In-app survey best practices: timing, frequency and follow-ups
The best in-app surveys ask one clear question, right after the action they are about, to the right people, and not too often. Trigger on an event, limit how often a person sees it, add follow-ups by score band, test before you publish, and read the answers on the Results tab.
The advice on timing and wording is general practice. The settings named below come from the surveys guide.
When should an in-app survey appear?
Ask right after the action the question is about. Someone who just finished onboarding can say how it went. Someone who is halfway through a task will find a survey annoying and may not answer honestly.
Use an event trigger for this. Set the survey trigger to event, enter an event name, and call track() when the moment happens:
import { track } from "@justonecx/sdk";
track("completed_onboarding");
The next track() call with that exact name shows the survey once. The other triggers are page load and scroll. They suit general questions, such as an NPS for established users. See in-app survey trigger events for more.
How often should you ask?
By default a person sees a survey once, or again after a throttle period. Set the repeat frequency in the builder (step 5 of the create flow) and keep it low. Asking the same person again and again lowers answer quality and wears out their patience.
There is one case where you ask more often on purpose: after every order, ticket or purchase. Set Show once per (event property) in the Delivery panel, for example order_id, and send the property:
track("purchase_completed", { order_id: "A-1042" });
The survey shows at most once for each different order_id, for each person. A repeat track() with the same order does nothing, whether the person answered or dismissed. Because every order is a new chance to ask, the Frequency setting and the throttle do not apply to such a survey.
How do you choose the right people?
Not every visitor should see every survey. Open the survey's Settings tab. Surveys use the same targeting editor as tours and announcements. You choose:
- Who sees it, using segments and conditions.
- Which pages, using "show on" and "hide on" rules.
The server applies the audience before content is sent. A person outside it never receives the survey. Read user segmentation for SaaS and the targeting guide.
A survey with page rules only opens when the visitor is on a matching page. If an event fires on another page, the survey waits and shows when the person reaches a matching page.
How do you pick the survey type?
Choose the type by the decision you want to make. NPS asks about the overall relationship, CSAT about one interaction, and CES about how easy a task was. The NPS vs CSAT vs CES article compares them.
Pick the type before you publish. A survey type cannot change after its first response.
Should you add follow-up questions?
Yes, when a number alone will not tell you what to fix. You can show different follow-up questions by score band. For example, ask a detractor what went wrong and ask a promoter what they value most.
Keep follow-ups short. One extra question is usually enough.
How do you test a survey before it goes live?
Use the Test survey mode in the builder to see the survey without saving a response. Check the wording, the placement and the page rules. A test that saves no response keeps your results clean.
Also check the trigger. If you use an event, call track() with the exact name and confirm the survey appears on the page you expect.
Where should the survey appear on screen?
You can show a survey as a slide-out, a modal or a banner. A modal asks for full attention. A slide-out or banner is easier to ignore. Choose by how important the question is. This is general design advice.
How do you read the answers?
Responses appear under the survey on the Results tab. For deeper work, choose Download responses (CSV). The file has one row per response with the answers, score, person and time.
Look at the follow-up text next to the score. A few written comments often show a pattern faster than the average does. When you find a pattern, tie it to something you can change, then ask again later with a new survey or a fresh trigger.
If you have not built a survey yet, follow how to add an NPS survey to your web app.
Frequently asked questions
What is the best time to show a survey?
Right after the action it asks about. Use an event trigger and call track() when that action finishes.
How do I keep from asking the same person too often?
By default a person sees a survey once, or again after a throttle period. Set the repeat frequency in the builder. For per-order surveys, Show once per (event property) limits it to once per property value.
Can I show a different follow-up to unhappy users?
Yes. You can show different follow-up questions by score band, for example one prompt for detractors and another for promoters.
How do I preview a survey without collecting answers?
Use the Test survey mode in the builder. It shows the survey without saving a response.
See how it works in the live demo.