In-App Surveys Are Here: Ask Users the Right Question at the Right Moment

The best time to ask a user what they think is while they are still in your product, doing the thing you want to learn about. Not three days later in an email they will never open. That is the whole idea behind in-app surveys, and as of today they are a first-class part of SeggWat.

You already used SeggWat to collect feedback and ratings from a single embeddable widget. Now the same widget can run in-app surveys — NPS, CSAT, CES, and fully custom multi-question forms — triggered by what the user is actually doing. Paste one script tag, author the surveys from the dashboard, and ship.

What an In-App Survey Tool Should Actually Do

Most survey software was built for the email era. You write a survey, you blast a link, and you hope someone clicks. Response rates sit in the low single digits because the question arrives long after the moment that prompted it.

An in-app survey flips that. The question shows up inside the experience — after a user finishes onboarding, when they cancel a plan, the third time they visit a pricing page. Context is everything. A "How easy was this to set up?" prompt means something the minute setup finishes and almost nothing a week later.

So we built the survey widget around three jobs:

• Ask in context. Fire on a URL pattern, a custom event your app dispatches, time on page, scroll depth, or exit intent.
• Ask without engineering. Author and edit surveys from the dashboard. The widget pulls live definitions from the server, so your developers paste the snippet once and never touch it again.
• Ask the standard metrics, properly. NPS, CSAT, and CES come as built-in templates that flow into the same analytics SeggWat already aggregates.

One Script Tag, Every Survey

Installation is a single line, same as the rest of the SeggWat widgets:

<script src="https://seggwat.com/static/widgets/v1/seggwat-survey.js"
        data-project-key="your-project-key"></script>

That is the entire integration. Every survey you create in the dashboard is served to this one snippet. Add a new survey, change its questions, retarget it to a different page — none of it touches your codebase.

Surveys render in three display modes so they fit how your product looks:

• Banner — a dismissible bottom slide-in (the default, lowest friction)
• Modal — a centered overlay with a backdrop, for moments you want to interrupt
• Inline — mounted into a container you specify, so the survey lives inside your own layout

NPS, CSAT, and CES Without the Spreadsheet

You should not have to build a Net Promoter Score pipeline from scratch every time. SeggWat surveys ship with templates for the three metrics product teams actually track:

• NPS — the 0–10 "How likely are you to recommend us?" question, scored and banded into promoters, passives, and detractors automatically.
• CSAT — a satisfaction scale plus an optional open-text follow-up.
• CES — Customer Effort Score, for measuring how hard a task felt while it is fresh.

Pick a template, tweak the copy, and publish. NPS scores still aggregate through the same stats endpoint SeggWat has always exposed, so your existing dashboards and API calls keep working. Want something bespoke? Start from the blank template and assemble any mix of question types: open text, rating scales, NPS, single choice, multiple choice, and yes/no.

Triggers: Where and When

This is the part we are proudest of. A survey trigger in SeggWat is two groups working together — where the user is and when to ask.

• Where is a URL rule. /checkout, /settings/*, your pricing page — the survey is gated to the pages that matter.
• When is the behavioral moment: time on page, scroll depth, an exit-intent gesture, or a custom JavaScript event you dispatch from your own code.

You combine conditions with any or all matching, so "on the pricing page and after 20 seconds and on exit intent" is a single rule, not a tangle of if-statements. Each survey also respects a cooldown (90 days by default) so you never nag the same visitor twice, and a sample rate if you only want to ask a fraction of traffic.

Need to fire a survey from your own UI instead? Call it directly:

SeggwatSurvey.show("survey-id", { force: true });

Surveys Go Beyond the Widget

In-app is the headline, but a survey is not always something you embed. SeggWat surveys can also go out as magic-link invitations — a unique, no-password link delivered by email that drops the recipient straight into the survey. Same survey definition, same analytics, just a different front door. Useful for win-back campaigns, post-support follow-ups, or reaching users who are not currently logged in.

How It Fits the Feedback Loop

A survey response is only worth as much as what you do with it. Because surveys live in the same platform as your feedback and ratings, open-ended answers land in the same inbox your team already triages, and the quantitative scores feed the same analytics. There is no separate survey tool to log into, no CSV export to reconcile. The signal stays in one place.

Pricing and Availability

Surveys are live now. Any plan can build and preview surveys as drafts — design the questions, set the triggers, and test every display mode at the live survey demo before you commit. Publishing a survey so the widget serves it to real users requires the Pro plan.

FAQ

What is an in-app survey? An in-app survey is a short questionnaire shown to users inside your product or website, triggered by their behavior — finishing onboarding, visiting a page, or trying to leave. Because it appears in context, response rates are far higher than emailed surveys.

Which survey types does SeggWat support? NPS, CSAT, and CES come as ready-made templates. You can also build custom surveys with open text, rating scales, single choice, multiple choice, and yes/no questions.

Do I need a developer to create surveys? No. You paste one script tag once. After that, every survey is authored and edited from the SeggWat dashboard — the widget pulls live definitions from the server.

Can I control which page a survey appears on? Yes. Triggers combine a URL rule (where) with a behavioral condition (when) — time on page, scroll depth, exit intent, or a custom event — using any or all matching.

Can I send a survey by email instead of embedding it? Yes. Any survey can be sent as a magic-link invitation, delivering a no-password link straight into the survey.

Get Started

If SeggWat is already on your site, you are one script tag away from your first survey:

1. Add the survey widget snippet to your page.
2. Create a survey from a template in the dashboard.
3. Set a trigger, preview it, and publish.

Read the full survey widget docs for every trigger, display mode, and configuration option — or try the live demo first to see all three display modes in action.