> 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/drip.md).

# Drip

How to get started with Drip

Connect your Drip account to Zigpoll and automatically add survey respondents as subscribers. When a respondent provides an email address, Zigpoll creates or updates their subscriber profile in Drip with survey responses as custom fields. You can optionally subscribe them to an email series campaign.

**Step #1: Get your Drip API Token and Account ID**

1. Log in to your Drip account.
2. Go to **Settings > User Settings** and copy your **API Token**.
3. Find your **Account ID** in your Drip URL or under **Settings > General Info**.

**Step #2: Connect Drip in Zigpoll**

1. In Zigpoll: Go to **Integrations** in the account sidebar and enable the Drip Integration.
2. Enter your **API Token**.
3. Enter your **Account ID**.
4. Click "Save Changes".

**Step #3: Configure Auto-Subscribe (Optional)**

If you want respondents to be automatically subscribed to a Drip email series campaign:

1. Toggle on **Auto Subscribe**.
2. **Select a Survey** — Choose which survey should trigger the subscription, or select "All Surveys".
3. **Select a Campaign** — Pick the Drip campaign to subscribe respondents to. Only active campaigns are shown.

You can add multiple configurations to route different surveys to different campaigns. Click "Click here to add another campaign subscription" to add additional entries.

**Step #4: Save Changes**

Click "Save Changes" to activate the integration.

**That's it.** Zigpoll will now create or update a subscriber in Drip each time a matching survey response includes an email address.

### Subscriber Details

Each subscriber created by Zigpoll includes:

* **Custom Fields** — All survey question-and-answer pairs are sent as custom fields on the subscriber profile.
* **Tags** — `zigpoll` and `survey-response` for easy segmentation in Drip.
* **Phone Number** — When a phone number 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), it is normalized to strict E.164 format (e.g. `+14155551234`) and stored on the subscriber's `sms_number` field. Numbers that can't be validated are dropped. SMS consent (`sms_consent`) is left unset — Zigpoll does not opt the subscriber into SMS marketing.

### Multiple Campaign Subscriptions

You can add multiple configurations to route different surveys to different Drip campaigns. Each configuration has its own survey filter and campaign destination.


---

# 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/drip.md?ask=<question>&goal=<user_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.