> 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/rudderstack.md). # RudderStack Send survey responses and customer profiles into RudderStack Integrating Zigpoll with RudderStack lets you automatically send survey responses into your RudderStack data plane as identify and track events. From there, you can route them to any downstream destination — analytics tools, data warehouses, marketing platforms, and more. *** ### Step 1: Get Your RudderStack Source Write Key 1. Log into your RudderStack Dashboard. 2. Navigate to **Sources** and select (or create) an HTTP source. 3. Copy the **Source Write Key** and **Data Plane URL** from the source settings. *** ### Step 2: Enable the RudderStack Integration in Zigpoll 1. Log in to your Zigpoll Dashboard. 2. Navigate to **Integrations** from the left-hand menu. 3. Find **RudderStack** and toggle it on. 4. Enter your **Source Write Key** and **Data Plane URL**. 5. Press **Save**. *** ### Step 3: Configure Options * **Send Identify Event** (on by default): Sends an identify call with user traits (email, survey responses, metadata) each time a survey is submitted. Turn this off if you only want track events. *** ### What Data Gets Sent Once enabled, every survey submission sends the following to your RudderStack data plane: **Identify Call** (if enabled): * `anonymousId`: The participant's ID * `traits`: Email, participant handle, metadata, and a link to the participant's Zigpoll profile. When a respondent provides a phone number, it is normalized to E.164 format and included as a `phone` trait. **Track Call:** * Event name: `Survey Completed` * Properties include the survey title, all question responses, and any survey metadata All response keys are converted to snake\_case for consistency with downstream tools. *** ### Example Use Cases * **Route survey data to your data warehouse** for long-term analysis alongside other customer data. * **Trigger downstream actions** in any RudderStack destination (email tools, CRMs, analytics) based on survey responses. * **Enrich customer profiles** across your entire stack with qualitative survey insights. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zigpoll.com/integrations/rudderstack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.