> 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/tutorials/launching-an-nps-survey.md).

# Launching an NPS Survey

Launch an NPS survey for your store and track your score over time

{% embed url="<https://www.youtube.com/watch?v=3xHruX0bnPU>" %}

1. Go to **Surveys** in your Zigpoll dashboard.
2. Click **New Survey**.
3. Select the **NPS** template from the list.
4. Give your survey a **name** (for internal use).
5. Click **Create Survey**.

You’ll land on the survey editor, where you can see all of your questions and start customizing them.

***

#### Choosing where your NPS survey appears

When you create or edit a survey, you can choose how and where customers see it. Common options include:

* **Link only**
  * Zigpoll gives you a URL you can share via **email**, **SMS**, or anywhere else.
* **On-site (every page or specific pages)**
  * Show the survey across your site, or only on certain URLs (e.g., after signup or on the account page).
* **Post-purchase**
  * Show the survey after checkout to capture feedback while the experience is fresh.
* **API only (advanced)**
  * Trigger an NPS survey at a specific **onboarding step** or **product milestone** by calling the Zigpoll API.

Choose the option that best matches your customer journey, then proceed to configure the questions.

***

#### Editing questions and changing question types

Every question in your survey can be fully edited.

1. In the survey editor, find the question you want to change.
2. Click **Edit Question** on that question.
3. In the **question editor**, you can:
   * Edit the **question text** directly by typing.
   * Click **Update Question** at the top to save your changes.

#### **Changing the question type**

If you want to change how a question is answered (for example, from a 0–10 NPS scale to a star rating):

1. In the question editor, open the **question type dropdown**.
2. Under **Rating & Ranking**, choose from:
   * **Star Rating**
   * **Satisfaction**
   * **Ranked Choice**
   * Other available formats
3. Click **Update Question** to apply the new type.

This flexibility lets you adapt the survey format to the feedback you need from your customers.

#### Taking your survey live

Toggle the visibility of your survey to "Live" and that will mean the public will be able to see your surveys and start submitting answers!

<figure><img src="https://1643988190-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LZpanNFqg3aCUZgXh3X%2Fuploads%2Fgit-blob-722ea033e93b4160e1aa9470898399193db2ce3a%2Fsurvey-live-switch.png?alt=media" alt="The Live switch in the survey header" width="580"><figcaption></figcaption></figure>

See our main "survey" page for additional insturctions on adding followup logic, targeting, customizing design, and more:

{% content-ref url="/pages/-LZuaccvpi\_yui07Qufh" %}
[Surveys](/polls.md)
{% endcontent-ref %}

#### Reading your NPS score

You do not need to calculate anything. The question's chart on the survey dashboard groups answers into Detractors (0–6), Passives (7–8) and Promoters (9–10) and shows the NPS score, which is the percentage of promoters minus the percentage of detractors, from −100 to 100. The chart updates as responses arrive, and the date filter at the top of the dashboard lets you compare periods, so you can watch the score move month by month. See [Analytics, AI, and Reporting](/analytics-ai-and-reporting.md).


---

# 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/tutorials/launching-an-nps-survey.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.
