An NPS survey only produces useful data if it reaches the right users at the right time. These guidelines help you configure survey timing, frequency, and follow-up actions so your scores reflect real sentiment and lead to action.

Survey activated users, not new ones

Don't ask users for an NPS score while they're still learning your product. New users haven't formed a meaningful opinion yet, so their responses skew your data and create a frustrating experience.

Target your NPS survey to users who have passed your activation milestone. Use a user property like account creation date or subscription start date to filter out users who signed up recently — for example, exclude users whose account is less than 30 days old. 

Restrict page targeting

Avoid targeting your NPS survey to all pages. A survey that pops up while a user is in the middle of a task feels intrusive and leads to lower response quality.

Instead, select a few low-friction pages where users are likely to have a moment to respond — dashboards, home pages, or settings pages work well. You can also exclude specific pages where the survey would interfere with critical workflows. Configure this in the NPS targeting settings.

Match frequency to usage patterns

Set your survey frequency based on how often users interact with your product. Asking too frequently annoys users and doesn't produce meaningfully different data between cycles.

As a starting point: for daily-use products, survey every 90 days. For weekly-use products, every 4–6 months. Adjust based on your response rates and how fast your product is changing.

Set a generous snooze window

When a user clicks "Ask me later," suppress the survey for at least 7 days — ideally longer. A short snooze window (e.g., 1 day) leads to repeat dismissals and frustration, especially if the user snoozes because they're busy, not because they're undecided.

Configure the snooze duration in the NPS survey's Ask me later settings.

Follow up on scores with targeted Flows

When a user submits an NPS response, Appcues automatically captures the score into a user property called _npsScore (Most Recent NPS Score). Use this property to create Segments for each NPS group and then target follow-up Flows to each one:

• Promoters (9–10): Ask for a review, referral, or case study participation.
• Passives (7–8): Highlight recently shipped features or underused functionality.
• Detractors (0–6): Offer a direct channel to share feedback or connect with your team.

See Target Flows based on NPS scores for setup instructions.

Segment your results

Your overall NPS score is a useful headline number, but the real insights come from comparing scores across user segments. In the NPS dashboard, use the Segment filter to break down scores by plan type, role, account age, or any other property you track. This helps you identify which user groups are happiest and which need attention.

Share responses with your team

NPS data is most valuable when the whole team sees it — not just the product team. Route responses to a shared channel so customer-facing teams can act on feedback quickly.

• Slack: Use the Appcues Slack integration to post NPS responses to a channel in real time.
• HubSpot: Add NPS scores to contact records using a HubSpot workflow. See Add NPS responses to a HubSpot contact record.
• Other tools: Use Zapier to send NPS events to any destination.