> 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/playbooks-for-agencies.md). # Zigpoll for Agencies Zigpoll gives you first-party answers to the questions every client asks: *Where did this customer come from? Why aren't visitors buying? What should we fix next?* Agencies use it to win pitches with data, prove the impact of their work, and turn surveys into a billable, recurring service. Everything below is a two-minute read. Each item links somewhere deeper when you're ready. ### What you can deliver, by practice * **CRO & experimentation** — Run pre- and post-purchase surveys alongside your tests so the "why" sits right next to whatever moved. Start with our [CRO audit playbook](/playbooks-for-agencies/cro-audit.md) and the [exit intent survey](/tutorials/exit-intent-survey.md) for objection mining. One CRO agency drove a [2% absolute lift in conversion](https://www.zigpoll.com/blog/blikket-case-study) with on-site surveys. * **Paid media & attribution** — The post-purchase "How did you hear about us?" survey is the independent referee for every channel — including the ones pixels can't see (TV, podcasts, TikTok, Reddit). See [attribution surveys](/tutorials/attribution-surveys.md) and how [NextPercent uses it to referee every channel](https://www.zigpoll.com/blog/nextpercent-case-study). * **Retention & lifecycle** — Post-purchase and email surveys feed straight into Klaviyo and your client's CRM, so every answer becomes a segment you can trigger on. See [Klaviyo segmentation](/tutorials/klaviyo-segmentation.md) and how [GrowthTrigger builds Klaviyo segments from survey answers](https://www.zigpoll.com/blog/growth-trigger-case-study). * **SEO & content** — Ask visitors what they came to find and didn't. Survey answers are a keyword and content-gap source your competitors don't have. * **Creative & brand** — Test names, packaging, and ad creative with real customers before the spend. See [How to test product names, packaging, and ad creative](/guides/how-to-test-product-names-and-creative.md), or pressure-test concepts instantly with [synthetic research](/synthetic-research.md). * **Dev & Shopify builds** — Surveys ship as native checkout, Thank You, Order Status, and customer account [app blocks](/installation/activating-zigpoll-on-shopify-checkout-extensions.md) — no theme surgery. Bake feedback collection into every build you hand off. * **Full-service** — All of the above from one dashboard per client. [Daily Grind Digital uses Zigpoll across attribution, CRO, and first-party data](https://www.zigpoll.com/blog/daily-grind-digital-case-study). ### Built for running client accounts * **One login, every client** — manage [multiple accounts](/accounts/multiple-accounts.md) and switch between them instantly. * **Roles for your team and theirs** — Admin, Editor, Read only, and Billing Admin via [team invites](/tutorials/adding-team-members.md). * **Fully white-labeled** — [no Zigpoll branding on any plan](/faq/branding-and-white-labeling.md), plus [custom survey domains](/custom-survey-domains.md) and sender domains. * **Reuse what works** — [migrate a proven survey](/polls/migrate-survey.md) from one client account to the next instead of rebuilding it. * **Reporting that scales** — [automated reports](/playbooks-for-agencies/building-automated-reporting-with-zigpoll.md), [Looker Studio](/integrations/data-studio.md) dashboards, the [API](/web-api.md), and [MCP](/integrations/mcp.md) so your AI tools can query client survey data directly. ### Playbooks Step-by-step plays for packaging Zigpoll into your services: * [Win more clients with Zigpoll](/playbooks-for-agencies/win-more-clients-with-zigpoll.md) — use surveys in pitches and audits to close deals. ([TabooGrow closes new clients this way](https://www.zigpoll.com/blog/taboogrow-case-study).) * [CRO audit](/playbooks-for-agencies/cro-audit.md) — a productized audit powered by voice-of-customer data. * [Building automated reporting](/playbooks-for-agencies/building-automated-reporting-with-zigpoll.md) — recurring client reports without recurring work. * [AI implementation guide](/playbooks-for-agencies/ai-implementation-guide.md) — offer AI-powered insights as a service. * [Website launch optimization](/playbooks-for-agencies/website-launch-optimization.md) — bake surveys into every launch. ### Partner with us **Partner program** — recurring commissions, co-marketing support, and a listing in our partner directory alongside agencies like Barrel, Swanky, and Eastside Co. Details and sign-up: [zigpoll.com/partners](https://www.zigpoll.com/partners). **Affiliate program** — prefer a simple referral link? Earn a **50% recurring revenue share** on every referral, tracked for 30 days, paid monthly. [How it works](/affiliate-program.md). **Get featured in a case study** — if you've gotten results for a client with Zigpoll, we'd love to tell the story (and send our traffic to your site). Email with the client, what you ran, and the numbers — we do the writing. {% hint style="info" %} Setting Zigpoll up for a client and want a second pair of eyes? Reply to any of our emails or write — we'll help you get it right from the start. {% endhint %} --- # 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/playbooks-for-agencies.md?ask=&goal= ``` `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.