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

Open targeting settings

1. Click Target & Publish when you're done building your NPS. The settings page opens.
2. At the top you'll see the Details section with the survey name and Build URL. The Build URL is the page where the Appcues Builder opens when you preview this survey — it doesn't affect where the survey shows to end users.

Set page targeting

3. Under URL Targeting > Page targeting, 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 targeting, 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. Under Audience targeting, choose who sees the survey:

• All users — every identified user is eligible.
• Users in a Segment — select a Segment you've created in Studio. 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

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 Builder, not here. Select the Ask me later button in the survey 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 spreads your survey across the days within each cycle. A lower percentage means responses arrive gradually rather than in a single burst — this is useful for products with a large user base.

Set priority

9. Under Flow priority, set the Weight for this NPS survey. If a user qualifies for multiple experiences (Flows, NPS surveys, etc.) at the same time and the same pages, the experience with the highest weight shows first. Leave the weight at 0 to use the default priority order. Increase it if this survey should take precedence over other experiences. Click View Flow priority to see all your live experiences ranked by weight.
10. Review the Priority when published setting. This controls where the survey sits in the priority queue relative to other experiences published to the same URLs.

Publish and un-publish

11. When your targeting settings are ready, click Publish in the top-right corner. The survey goes live immediately. If you've made changes you want to discard, click the dropdown arrow next to Push changes and select Discard changes.
12. To take a survey offline, click the three-dot menu (···) in the top-right and select Un-publish. The survey stops showing immediately. You can also schedule publishing using the Schedule button next to Push 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.
• Click Check eligibility in the audience targeting section to verify a specific user qualifies.
• Click Test URL targeting to confirm your page rules match the correct URLs.
• Check the NPS analytics page — a response should appear within minutes of submitting a test score.

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, click Check eligibility to test your user. Property values are case-sensitive — admin does not match Admin.
• Check sampling. At low sampling rates, most eligible users won't see the survey 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 order with View Flow priority.

See Troubleshooting NPS for a full diagnostic walkthrough.