> 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/omnisend.md). # Omnisend #### Step #1: Create your integration 1. Get your API Key from Omnisend. You can access your Api key by following the steps here: . Be sure to select **I want to set up custom permissions for this API key** and make sure that both **Contacts** and **Events** are selected. 2. In Zigpoll: Click Settings -> Manage Integrations -> Enable the Omnisend Integration 3. Enter your API key into the input field and press save. {% hint style="info" %} **Already connected?** API keys created before survey events were added only carry the **Contacts** permission, so your contacts will keep syncing but no events will be sent. To start triggering automations, generate a new API key in Omnisend with **Events** enabled and save it in Zigpoll. {% endhint %} #### Step #2: Collect Your Data Once your integration has been completed, data will start flowing into your Omnisend account. If you use our Shopify integration, we will use the user data provided to associate it with the correct email address. If not, but you have an email input field, the results from that field will be used to identify any existing Omnisend profiles or it will create a new one. We will also pipe through your customer's average sentiment score and survey results. You can use this sentiment score to create mailing campaigns and trigger other events that will help grow your customer lifetime value. When a survey is completed, Zigpoll sends a custom event named `[Zigpoll] Completed Survey: ` to Omnisend, carrying the survey answers along with any campaign metadata. Use it as an automation trigger or in a segment rule to follow up on a response — the event appears in Omnisend automatically the first time it is sent, so there is nothing to set up on their side. Events require the **Events** permission on your API key (see Step #1). When a new contact is created, Zigpoll also adds the respondent's phone number as a separate `phone` identifier with its SMS channel set to a non-subscribed status, when one is available. The phone is captured from the survey response — a dedicated phone-number field or a phone number typed into a free-text/short-answer question (or the customer phone from your Shopify integration, which is preferred when connected) — and normalized to strict E.164 format (e.g. `+14155551234`); numbers that can't be validated are dropped. The phone is stored on the contact only; Zigpoll does not opt the contact into SMS marketing. --- # 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/omnisend.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.