> 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/segment.md). # Segment Integrating Zigpoll with Segment gives you powerful new ways to collect, analyze, and act on customer feedback. By connecting a source, you can automatically enrich survey responses with data from your existing tools, send survey results downstream, or trigger workflows in your favorite platforms. In this guide, we’ll walk you through how to connect a source to Zigpoll and start using it right away. *** ### Step 1: Create A Zigpoll Source In segment 1. Log into your Segment Dashboard 2. Create a source, select Zigpoll from the list of source options. *** ### Step 2: Enable the Segment integration in Zigpoll and enter your write key 1. Log in to your Zigpoll Dashboard. 2. Navigate to **Integrations** from the left-hand menu. 3. Select **Segment** and enter the write key for your source. *** ### Step 3: Put It Into Action Once your source is connected, you can: * **Send survey results** directly into the source. * **Attach metadata** (like customer ID, order details, or session data) to enrich responses. * **Trigger workflows** in tools like Segment, Klaviyo, or Slack. *** ### Example: Using Zigpoll with Segment By connecting Segment as a source, every Zigpoll survey response becomes an event inside Segment. When a respondent provides a phone number, it is normalized to E.164 format and included as a `phone` trait on the Identify call (Segment's reserved trait, which maps to the SMS channel by default). From there, you can: * Send feedback into analytics dashboards. * Sync responses with email automation flows. * Enrich customer profiles with qualitative 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 dynamically 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/segment.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 `build a script that syncs our docs to a CMS` 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.