> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/funnelish.md).

# Funnelish

Running sales funnels on **Funnelish**? Adding **Zigpoll** lets you collect feedback at every step of the funnel—from opt-in and sales pages to the order form and the post-purchase thank-you page. Ask shoppers how they found you, why they did (or didn't) buy, and how the checkout experience felt, all without touching your funnel's design.

Funnelish lets you add custom code either **funnel-wide** (across every step) or to a **single page**, so you can choose exactly where Zigpoll runs.

***

#### 🔧 Step 1: Get Your Zigpoll Embed Script

1. Go to your Zigpoll dashboard.
2. Select your survey and click **“Installation”**.
3. Copy the JavaScript embed code. It looks like this:

```html
<script type='application/javascript'>
  ;(function () {
    window.Zigpoll = {
      accountId: 'YOUR_ACCOUNT_ID'
    };

    var script = document.createElement("script");
    script.type = "text/javascript";
    script.charset = "utf-8";
    script.src = "//cdn.zigpoll.com/static/js/main.js";
    script.async = true;

    document.head.appendChild(script);
  }());
</script>
```

> Replace `YOUR_ACCOUNT_ID` with your actual account ID.

***

#### 🌐 Step 2: Choose Where Zigpoll Should Run

Funnelish gives you two ways to add the script. Pick the one that matches where you want your survey to appear:

* **Funnel-wide** — Zigpoll loads on **every step** of the funnel. Best for site-wide feedback, exit-intent surveys, or attribution questions you want available throughout.
* **Single page** — Zigpoll loads on **one specific step**. Best for a post-purchase survey on your thank-you page, or an exit-intent survey on a single sales page.

***

#### ✅ Option 1: Add Zigpoll Funnel-Wide

**Use this if you want your survey available across the entire funnel.**

1. Open your funnel in Funnelish and go to **Settings**.
2. Open the **Custom Codes** (Tracking Codes) section.
3. Click **Create a New Code**.
4. Give it a name like `Zigpoll`.
5. Paste your Zigpoll embed script into the code field.
6. Under **Code placement**, select **Append to page head**.
7. Turn the **Lazy Load** toggle **off** so the survey is ready as soon as the page loads and your display rules fire correctly.
8. Save the code, then click **Save Changes** in the funnel settings.

> 📌 The script is now injected into every step of your funnel.

***

#### ✅ Option 2: Add Zigpoll to a Single Page

**Use this if you only want the survey on one step—like the thank-you page.**

1. Open the step you want in the Funnelish **page editor**.
2. Click the **three-dots (More actions)** menu at the top of the editor.
3. Choose **Custom Code**.
4. Select the **Head HTML** tab and paste your Zigpoll embed script.
5. Save the page, then publish your funnel.

> 🛠 This loads Zigpoll only on that single step, giving you precise control over where the survey appears.

***

#### ✅ You're Done!

Zigpoll will now load on your Funnelish funnel—either across every step or just where you added it. You can control **when** and **how** the survey appears (time delay, scroll depth, exit intent, targeting, and more) directly from the **Zigpoll dashboard**, without editing your funnel again.

***

#### 🛒 Recommended: A Post-Purchase Survey on Your Thank-You Page

The thank-you / order confirmation step is the perfect place to learn from customers right after they buy:

* **Attribution** — “How did you hear about us?” to understand which channels drive sales. See the [Attribution Surveys](/tutorials/attribution-surveys.md) tutorial.
* **Checkout friction** — “How easy was it to complete your order?” to spot drop-off causes.
* **Upsell insight** — ask why shoppers did or didn't take the one-click offer.

Add the embed code to your thank-you step using **Option 2** above, then build the survey in Zigpoll.

***

#### 🙋 Optional: Pass Customer & Order Data

If you want to attach the buyer's details to their response—handy for post-purchase surveys—add a second script **below** the embed code with whatever data your page exposes:

```html
<script type="text/javascript">
  window.Zigpoll.user = {
    handle: "Jane Doe",
    id: "CUSTOMER_ID",
    metadata: {
      email: "jane@example.com",
      order_id: "ORDER_ID"
    }
  };
</script>
```

This lets you segment and filter responses by customer in your Zigpoll analytics. See [Participant Metadata](/embed/participant-metadata.md) for the full list of fields.

***

#### 💡 Pro Tips

* Use Zigpoll's **Preview Mode** to test display settings (delay, scroll, exit intent) before going live.
* Keep **Lazy Load** off on the Funnelish code so Zigpoll's own display rules control timing.
* Target surveys to specific audiences—returning visitors, mobile users, or particular regions—right from the Zigpoll dashboard.
* Need help? [Contact us](mailto:support@zigpoll.com)—paid plans include end-to-end installation support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zigpoll.com/integrations/funnelish.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.