> 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/email-zigpoll-surveys.md).

# Email Zigpoll Surveys

## **📩 How Email Surveys Work in Zigpoll**

Zigpoll allows you to send surveys directly via email, either manually or automatically through Shopify events. This guide explains how email survey sending works behind the scenes, how to set up sender and survey domains, and how Zigpoll identifies respondents.

If you want to deliver Zigpoll surveys via your own email platform (ex. Klaviyo), read our Integrations page to see if your platform is supported

{% content-ref url="/pages/-MkcAljZVNlkwKq4JoDM" %}
[Integrations](/integrations.md)
{% endcontent-ref %}

***

### **2. Ways to Send Email Surveys**

#### **2.1 Manual Email Sends**

Manual sends allow you to deliver a survey to a specific list of recipients.

**How it works:**

* You select recipients directly inside Zigpoll.
* Zigpoll sends the survey using either the default sender domain or your custom sender domain (if configured).
* The recipient’s email address is encoded in the survey link.
* When they submit the survey, Zigpoll automatically associates the response with that email.

**Use cases:**

* One-off feedback campaigns
* Follow-ups to segmented customer lists
* Pre-launch customer research

**How to send:**

* Go to "Campaigns" in the survey sidebar
* Go to "Emails"
* Choose to enter in emails manually or upload a csv with email addresses
* Hit "Send email"

<figure><img src="/files/vwPRQsCd3YjtoyETFaaS" alt=""><figcaption></figcaption></figure>

***

#### **2.2 Automated Sends via Shopify Webhooks**

Zigpoll can automatically trigger email surveys when certain Shopify events occur.

**Supported triggers:**

* **Abandoned checkout**
* **Order Paid**
* **Order Cancelled**
* **Order Fulfilled**
* **Order Delivered**
  * *Note:* “Order delivered” requires carriers recognized by Shopify (USPS, UPS, FedEx, DHL, etc.).\
    Third-party or unsupported carriers may not fire delivery events.

**How webhook sending works:**

1. You attach a survey to a trigger (e.g., *Order Delivered*) under "Settings -> Delivery" in Zigpoll. Ensure Delivery Format is "Email"
2. Shopify detects the event.
3. Zigpoll sends the matching survey email automatically.
4. Customer/order data is passed to Zigpoll, allowing auto-identification of the respondent.

This method is fully automated and ideal for post-purchase feedback loops.

<figure><img src="/files/Dthr6DyDPwS2xd0e9QC9" alt=""><figcaption></figcaption></figure>

***

### **3. Designing Your Survey Email**

You can customize the survey email template directly inside Zigpoll.

#### **3.1 Accessing the Email Editor**

1. Open your Zigpoll survey.
2. Go to **Design → Email**.
3. The editor displays your default template (based on the survey style you selected).

<figure><img src="/files/aYiP8sNi5Cte4aUkQ1ED" alt=""><figcaption></figcaption></figure>

#### **3.2 Customization Options**

You can customize:

* Subject line
* Body copy
* CTA button text
* Logo and branding
* Layout and color scheme

These changes apply immediately to both manual and automated sends.

***

### **4. Custom Sender Domains**

By default, Zigpoll sends survey emails from an address like `no-reply@zigpoll.com`. With a **custom sender domain**, those emails are sent from your own domain instead (e.g. `noreply@yourstore.com`) for a fully on-brand, white-labeled experience.

This feature is available on the **Standard plan and higher**.

#### **4.1 What a Custom Sender Domain Does**

A custom sender domain lets you send surveys from an address on your own domain, such as `noreply@yourstore.com`. This improves:

* Brand trust and recognition
* Email deliverability
* Open and engagement rates

#### **4.2 How to Set It Up**

1. Log into your Zigpoll dashboard and go to **Settings → Custom Domains**.
2. Enable the switch labelled **Custom Sender Domain**.
3. **Enter a sending subdomain.** Use a dedicated subdomain such as `mg.yourstore.com` — not your root domain — then click **Save Domain**.
4. **Add the DNS records.** Zigpoll generates the SPF and DKIM **TXT records** your domain needs. You can add them two ways:
   * **Auto-Connect DNS** — for supported DNS providers, Zigpoll writes the records for you in one click.
   * **Manually** — copy the **Name** and **Value** of each record into your DNS provider. Every record shows a live status (unverified / valid / invalid) so you can confirm it was added correctly.
5. Click **Verify Domain**. Once the records validate, your sender domain activates **automatically** — there is no manual approval step.
6. Send a test email survey. It will now arrive from your custom domain (e.g. `noreply@yourstore.com`).

{% hint style="info" %}
DNS changes can take up to 24–48 hours to propagate. If your records still show as unverified, wait a little and click **Verify Domain** again, or use [dnschecker.org](https://dnschecker.org) to confirm propagation.
{% endhint %}

<figure><img src="/files/NFMTjHF4To5MjDRY3Vgf" alt=""><figcaption></figcaption></figure>

For more detail and troubleshooting, see the [Custom Sender Domains FAQ](/faq/custom-sender-domains.md).

***

### **5. Custom Survey Domains**

A custom survey domain changes the URL where customers complete your survey — from `survey.zigpoll.com/your-survey` to something like `survey.yourstore.com/your-survey`. Paired with a custom sender domain, this gives you a fully white-labeled email survey experience.

Setup, SSL, and troubleshooting are covered on their own page:

{% content-ref url="/pages/Y4KWlFoXIXAwYXbQXf4z" %}
[Custom Survey Domains](/custom-survey-domains.md)
{% endcontent-ref %}

***

### **6. How Zigpoll Identifies Respondents**

Zigpoll automatically associates responses with the correct customer. Here’s how identification works in each sending mode.

#### **6.1 Webhook-Triggered Surveys**

When a survey is sent because of a Shopify event:

* Shopify includes customer/order data in the webhook.
* Zigpoll attaches that data to the respondent automatically.
* No email field or identification step is needed in the survey itself.

#### **6.2 Manual Sends**

For manual campaigns:

* Zigpoll encodes the recipient’s email in the survey link.
* When the respondent completes the survey, Zigpoll links it back to that email automatically.

No additional setup is required.

***

### **7. Email Volume & Plan Limits**

All Zigpoll plans include a monthly email send allowance.

* Every email actually delivered counts toward your quota.
* Webhook-triggered and manual sends are treated the same.
* You can view your current usage under **Billing** or **Account Settings**.

See our plans for more details:

{% content-ref url="/pages/-LZzntn1HSzaiXwIaBqe" %}
[Subscription Plans](/subscription-plans.md)
{% endcontent-ref %}


---

# 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/email-zigpoll-surveys.md?ask=<question>&goal=<endgoal>
```

`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.
