Control where your NPS survey appears, how often users see it, and which users are eligible.

Open the survey's settings

1. Click Experiences and click the survey. Set the Type filter to NPS to find it faster.
2. Click Settings at the top. The Settings tab opens.

Settings save as you edit. Sections shared by every experience type are covered in Configure an experience's settings. This article covers what's specific to NPS.

Set page targeting

3. In Where this appears, choose where the survey can appear:

• Any page — the survey can show on any URL path where Appcues is installed.
• At a specific path — restrict the survey to specific URLs. Use this to keep the survey off checkout pages, login screens, or other areas where you don't want interruptions.

Set environment targeting

4. Under Environment in the same section, choose which domains the survey shows on:

• Everywhere my Appcues embed script is installed — the survey shows on all domains with the SDK.
• Only the domains I choose — select specific domains from the checkbox list. Use this to keep the survey in production only, or to test on staging first.

Read more about Page Targeting.

Set audience targeting

5. In Who sees this, choose who sees the survey:

• All users — every identified user is eligible.
• Users in a Segment — select a Segment. This is the recommended approach for most teams — it lets you reuse the same audience across multiple experiences and filter analytics by segment.
• Specific users — build conditions directly using user properties. For example, set User Property > Role > equals > Admin to target users with that specific property value. You can add multiple conditions with the Add condition button.

Set frequency and sampling

These settings are in How often this shows.

6. Set the survey frequency — "After someone completes the survey, when should it show up again?" Enter the number of days. Default: 10 days. This defines your rolling cadence. A user who completes the survey won't see it again until this many days have passed. In NPS 2.0, the "Ask me later" snooze behavior is configured in the survey's builder, not here. Select the Ask me later button in the builder to set the snooze Duration (e.g., 10 days) and, under Additional options, optionally enable Track event or Update user properties when someone snoozes. See Create an NPS survey for details.
7. Set the minimum page views — "How many pages should a user visit in a session before they see this experience?" Default: 0 (survey can show on first page view). Increase this to avoid interrupting users the moment they land in your app. For example, set it to 5 so users have time to settle in before seeing the survey.
8. Set the sampling percentage — "How many users should be sampled?" Use the slider or enter a value. Default: 100%. Sampling isn't a fixed cut of your audience — it's a per-user chance. At 15%, for example, each user who clears page and audience targeting has a 15% chance of seeing the survey, checked against that user's Session Randomizer property — not "15% of eligible users, guaranteed." This spreads responses across the days in each cycle instead of arriving in a single burst, which is useful for products with a large user base.

Set priority

9. In How this competes with other experiences, set the Weight. If a user qualifies for several experiences at the same moment, the one with the highest Weight shows first. Flows, legacy Flows, and NPS surveys compete with each other.
10. Check the Priority when published table. It shows where the survey will rank once you publish, next to the experiences it competes with.

Publish and un-publish

11. When your settings are ready, click Publish. If the survey is already live, click Push changes to send your edits to users. See Publish, schedule, and unpublish an experience to unpublish, schedule, or discard changes.

Confirm it worked

• After publishing, open your app in a browser where Appcues is installed. Navigate through enough pages to meet your minimum page views threshold.
• To check a specific user, open them in Audiences > Users and use the Eligibility tab. See Find and inspect users.
• Click Test URL targeting in Where this appears to confirm your page rules match the correct URLs.
• Open the survey's analytics. A test response should appear within minutes. See Analyze an experience's performance.

If your survey isn't showing

• Check the debugger. Open the Appcues debugger and confirm all rows show green checkmarks. Red errors indicate an installation issue. See Installation testing.
• Verify the domain. Expand "User Identified" in the debugger and check that _hostname matches a domain in your environment targeting.
• Check audience conditions. If targeting specific users or a segment, check the user's Eligibility tab. Property values are case-sensitive — admin does not match Admin.
• Check sampling. At low sampling rates, each eligible user only has a percentage-based chance of seeing the survey, so most won't see it on any given day. Set sampling to 100% temporarily for testing.
• Check priority weight. If other experiences have higher weights, the NPS survey may be queued behind them. Review the Priority when published table.

See Troubleshooting NPS for a full diagnostic walkthrough.