Product Surveys: ask, measure, and act

Product Surveys let you ask shoppers structured questions and get structured answers back — not another inbox of mixed emails. You build surveys once, place them where the moment is right (product page, after purchase, customer dashboard, or a shareable public link), and results aggregate automatically, including a real NPS calculation. ## How to build a survey 1. Go to **Surveys** and open the **builder**. 2. Add questions in any mix of seven types: **rating** (1-5), **NPS** (0-10), **single choice**, **multi choice**, **dropdown**, **short text** (up to 300 characters), and **long text** (up to 4,000). 3. Mark questions **required** where an answer truly matters; over-requiring is the top reason surveys die halfway. 4. Add **skip logic** where it helps: a single-choice option can carry a skip target, so answering "No" jumps the respondent past irrelevant follow-ups. The server enforces the same logic — required questions bypassed by a skip are relaxed, nothing else. 5. Set a **schedule** (start and end dates) if the survey is seasonal, and choose **frequency** — how many days before the same person can be asked again (the duplicate guard defaults to 7 days). 6. Under **access**, pick **customers** (only signed-in shoppers of your store may respond) or **public**. Public surveys are rate limited: identity-keyed duplicate protection per frequency window, plus a cookie-level guard for fully anonymous submissions. 7. Toggle **anonymity** if you want honest answers over attributable ones — anonymous mode strips customer identity from responses entirely. 8. Save, then set the status to **active**. ## Placements 1. **Product page** — attach the survey to specific products or all of them; it renders on those product pages. 2. **Post-purchase** — shows after checkout, while the experience is fresh. 3. **Customer dashboard** — signed-in shoppers see it inside their account area. 4. **Public link** — share a direct URL for anything from packaging QR codes to newsletter blasts. ## Reading results 1. Open the survey's **results** view. Per-question aggregation shows averages for ratings, full distributions for choice questions, and the latest text answers — enough context to quote customers verbatim in your next team meeting. 2. NPS surveys compute the official score: promoters (9-10) minus detractors (0-6) over all responses, with passives (7-8) counted in the base. The breakdown is shown alongside the score, so you know whether movement came from promoters or detractors. 3. Set a **detractor alert** in **Survey settings** (at /dashboard/surveys/settings) — the alert threshold defaults to 3 detractor responses within 24 hours, with an optional notification email. When a spike crosses the threshold, an alert is raised, so a bad week surfaces while you can still fix it. 4. Responses also fire the survey.submitted automation trigger, so you can hook surveys into your flows. ## AI survey generation Stuck on wording? Describe what you want to learn and let the AI draft the survey — title, description, and a full question set. The draft lands in the builder for your review; the AI never writes to the database directly, and generation counts against your plan's daily AI quota (15 requests per day on Free by default). ## FAQ **Who can answer a customers-only survey?** Only shoppers signed in to your store. Anonymous drive-by responses are rejected at submission, which is what keeps the sample meaningful. **Can the same person answer twice?** Not within the frequency window. Identity-keyed dedupe (customer reference or email) blocks repeats for known respondents, and a cookie guard covers anonymous ones. **Do I have to use AI to build a survey?** No — the builder is fully manual. The AI path is a draft generator for when you want a starting structure fast.