> 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/custom-survey-domains.md).

# Custom Survey Domains

Host your Zigpoll surveys on your own branded URL, with an SSL certificate provisioned automatically.

A **custom survey domain** changes the URL where customers complete your survey. Instead of the default Zigpoll address, your surveys load from a subdomain on your own domain — fully on brand, served over HTTPS, with the SSL certificate provisioned automatically.

* **Default:** `survey.zigpoll.com/your-survey`
* **Custom:** `survey.yourstore.com/your-survey`

{% hint style="info" %}
A custom **survey** domain controls the URL customers *visit* to take the survey. A custom **sender** domain controls the address survey emails are *sent from*. They are separate features — set up both for a fully white-labeled experience. See [Custom Sender Domains](/faq/custom-sender-domains.md).
{% endhint %}

***

### What it affects

Once your custom survey domain is active, it is used everywhere Zigpoll links to a survey, including:

* The survey URL shown in and linked from your email surveys
* Generated [survey links](/survey-links.md) and [public links](/public-link.md)
* The link customers click to open and complete the survey

Switching domains does not affect existing responses or your survey configuration — only the URL the survey is served on.

***

### Requirements

* A subdomain you control (e.g. `survey.yourstore.com`). We recommend a dedicated subdomain rather than your root domain.
* Access to your DNS provider so you can add a CNAME record (or connect it automatically — see below).
* The **Standard plan or higher**. On other plans, saving a domain shows *"Please upgrade to the Standard plan or higher to use this feature."*

***

### How to set it up

1. In your Zigpoll dashboard, go to **Settings → Custom Domains** and turn on the switch in the **Custom Survey Domain** card.
2. **Enter your preferred survey subdomain**, for example `survey.yourstore.com`, then click **Save Domain**.
3. **Add the DNS record.** Zigpoll asks you to point your subdomain at our servers with a single **CNAME** record. There are two ways to do this:
   * **Auto-Connect DNS** — for supported DNS providers, Zigpoll adds the record for you in one click.
   * **Manually** — in your DNS provider, create a CNAME record:

     | Type  | Name (host)                       | Value               |
     | ----- | --------------------------------- | ------------------- |
     | CNAME | `survey` *(your subdomain label)* | `proxy.zigpoll.com` |
4. Click **Check Status** to verify. While DNS is propagating, the domain shows as **pending** and Zigpoll keeps checking automatically — you don't need to keep clicking.
5. When the record is detected, the domain flips to **active** and an SSL certificate is provisioned automatically. Your surveys are now served over HTTPS at your custom domain.

{% hint style="info" %}
DNS changes can take up to 24–48 hours to propagate, though they're often much faster. You can confirm propagation with a tool like [dnschecker.org](https://dnschecker.org).
{% endhint %}

***

### Troubleshooting

* **Stuck on "pending."** The CNAME hasn't fully propagated yet. Give it some time — Zigpoll re-checks automatically and activates the domain once the record resolves.
* **Verification error.** Double-check that the CNAME's **Name** matches your chosen subdomain label and its **Value** is exactly `proxy.zigpoll.com`. Correct the record and click **Check Status** again.
* **Use a subdomain, not your root domain.** Root-domain CNAME records can conflict with other DNS settings. A subdomain (e.g. `survey.yourstore.com`) keeps things clean and avoids disrupting your main website.
* **No manual SSL setup needed.** Zigpoll provisions and manages the certificate for you once DNS is configured.

#### My survey links show "not found" after I changed my custom domain

Zigpoll only serves your surveys on `survey.zigpoll.com` and on the custom domain currently saved for your account. When you change or remove the custom domain, links that use the **old** domain stop loading and show a not-found page.

* **Update the links you have already shared** (email templates, Klaviyo flows, QR codes, Linktree) to use the new domain. Links in the form `https://survey.zigpoll.com/SURVEY_ID` keep working whatever custom domain you use, so they are a safe choice for places that are hard to update.
* **Keep the CNAME for the new domain in place.** Removing the DNS record takes the domain offline again.

#### My new custom domain won't load even though DNS is set up

Reconnect the domain so Zigpoll registers it again:

1. Go to **Settings → Custom Domains**.
2. Turn off the switch in the **Custom Survey Domain** card and click **Remove Domain** to confirm.
3. Turn the switch back on, enter the same subdomain, and click **Save Domain**.
4. Leave your CNAME record pointing at `proxy.zigpoll.com` and click **Check Status** until the domain shows as verified and active.

Removing and saving the domain again restarts its SSL certificate setup from scratch. If it still shows an error after that, send the error message and your subdomain to <support@zigpoll.com>.

{% hint style="info" %}
Need a hand? Send your domain details to <support@zigpoll.com> and we'll help you get set up.
{% endhint %}


---

# 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/custom-survey-domains.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.