An experience's Settings tab controls who sees it, which pages it appears on, what triggers it, how often it shows, and which experience wins when several qualify at once. Every web experience type uses the same tab, and each type shows only the sections that apply to it. Some teams call this targeting, audience rules, or triggering.

This article covers Flows, legacy Flows, Embeds, Banners, Pins, Launchpads, and NPS surveys. Checklists have their own settings page; see Create a Checklist.

Prerequisites

• Admins, Publishers, and Editors can change settings.
• Publishing or pushing changes needs the Admin or Publisher role.

Open an experience's settings

1. Click Experiences in the left sidebar.
2. Click the experience. The experience opens.
3. Click Settings at the top. The Settings tab opens, with a summary of every section on the left.

Each item in the summary shows the section's current value, such as Audience: Users in a Segment or Frequency: Once. Click an item to jump to its section.

Banners and Pins open straight to their settings. Legacy Flows show only Settings and Analytics, because you build them in the Appcues Builder Chrome extension.

Name and describe the experience

The Details section holds:

• Name: what your team sees in Appcues.
• Display name: the name your users see, for example in a Launchpad. Flows and legacy Flows only.
• Description: what the experience is for, who owns it, and anything a teammate should know.
• Tactic: the campaign tactic the experience belongs to. Choose None to leave it standalone.
• Build URL: the page the builder opens on when you edit the experience.

Choose who sees it

In Who sees this, choose one:

• All users
• Users in a Segment: pick a Segment. Click Add criteria to narrow it with extra rules for this experience only.
• Specific users: build rules from user properties, events, and other conditions.

Click Calculate audience size to count the users who match right now. Click Summarize targeting for a plain-language summary of the rules.

For rule types and examples, see Configure Audience Targeting and Target by User & Group Property.

Choose which pages it appears on

Where this appears has two parts.

Pages. Choose Any page or At a specific path. With a specific path, click Add page rule to add a URL rule. Rules match the path after the domain, for example /settings in www.example.com/settings.

Environment. Choose Everywhere my Appcues embed script is installed or Only the domains I choose. With your own selection, tick the domains in the table. Each domain shows Installed or Not installed, so you can see where the Appcues SDK is running. Leave at least one domain selected.

Click Test URL targeting to check whether a URL matches your page and domain rules. See Configure Page Targeting for rule operators and regex.

Choose when it shows

When this shows sets the trigger and the frequency. Banners, Pins, and Launchpads have no trigger: they show whenever a user qualifies.

The trigger type controls what starts the Flow for a qualifying user.

Manually triggered experiences ignore all other targeting rules — frequency, page targeting, and audience conditions are bypassed. The experience shows each time the trigger fires.

A Flow can be triggered automatically (page load or event) and manually at the same time. For example, a Flow set to trigger on page load can also be launched from a Checklist item.

Frequency. Choose one:

• Show once
• Show every time
• Show multiple times: enter how many times. Flows and Embeds only.

Tick Stop showing when experience is completed to stop showing it once a user completes it. Flows and Embeds only. For details, see Set Flow Frequency.

NPS surveys

NPS surveys have How often this shows instead of a trigger. Set how many pages a user visits in a session before the survey appears, when to show it again after someone responds, and what share of users to sample.

Choose what happens when someone finishes

Legacy Flows have a What happens next section. Tick either or both:

• Send them to another page: enter a Redirect URL. Start with https:// for another site, or / for a page on the same site.
• Start another flow: pick the next legacy Flow.

These actions don't run in preview. They run in the live experience.

Make it available in a Launchpad

For Flows and legacy Flows, tick Allow this flow to be recalled from any Launchpad in the Launchpad section. The Flow then appears on any Launchpad that has a Flow List block, for users who meet its conditions.

After you tick it:

• Only show if the page matches (default): The Flow appears in the Launchpad only when the user is on a page that satisfies the Flow's own page targeting. Use this for Flows that are relevant to a specific page — for example, a Flow published to /analytics only appears in the Launchpad when the user is on that page.
• Uncheck "Only show if the page matches": The Flow appears in the Launchpad on all pages where the Launchpad is installed. Use this for Flows that work as general announcements or notifications.

A Flow triggered by an event can't be recalled from a Launchpad. Change the trigger to When the user reaches the page to turn this on.

Set priority

How this competes with other experiences decides which experience shows first when several qualify for the same user at the same moment. The experience with the highest Weight wins.

The Priority when published table shows where this experience will rank once you publish, next to the experiences it competes with:

• Flows, legacy Flows, and NPS surveys compete with each other.
• Embeds compete only with other Embeds.
• Banners, Pins, and Launchpads don't compete, so they have no priority section.

See Set Flow Priorities.

Override the account frequency limit

Flows and legacy Flows show the Account frequency limit section. The limit is an account-wide setting: it caps how many Flows and NPS surveys a user can see in a set time, such as 2 per hour. When it's on, the section shows the current limit.

• Tick Override account frequency limit on this Flow to exempt this Flow from the limit.
• Click Edit account frequency limit to change the limit for the whole account.

See Set Experiences Frequency Limit.

Measure success with a goal

If the experience has a goal, How success is measured appears and Goal is added to the summary. Choose No goal — just track views and completions, or keep A Goal is achieved and pick the goal from the list.

Conversion timeframe is how many days after seeing the experience a user can reach the goal and still count as a conversion. Enter 1 to 90.

See Set up Goals.

Localize a legacy Flow

Legacy Flows have a Localization section.

1. Click Configure languages and add the languages you support.
2. Click Download all translations. A file with the Flow's content downloads.
3. Click Upload next to a language and choose its translated file.
4. Enter a Display name for each language, if your users see the Flow's name.

The Flow must be unpublished to download content, upload translations, or remove them. See Localize Flows.

Add tags

In Tags, click Add tag to label the experience. Tags let you filter the Experiences list and save views.

Schedule your experience

Set a start and end date to automatically publish and unpublish your experience.

This is optional — if you don't set a schedule, the experience goes live as soon as you click Publish and stays live until you manually unpublish it.

For details, see Publish, schedule, and unpublish an experience.

Publish your changes

Settings save as you edit, but users don't see the changes until you publish them.

• A draft experience: click Publish.
• A live experience: the header shows Unpublished changes. Click Push changes to send them to users.

See Manage experiences for scheduling, unpublishing, and discarding changes.

Who changed this, at the bottom of the tab, shows who created the experience and who last edited it, with a link to its publish history. Click the copy icon next to Experience ID to copy the ID.

If a section is missing

• The section isn't in your plan. Event triggering, priority, Launchpads, and the account frequency limit can each be plan-dependent. The section shows a message saying it isn't included.
• The experience type doesn't have it. 
• You see "This flow is part of a workflow." A Workflow controls when this Flow shows. Click Open workflow in Studio to change it there.
• There's no goal section. It appears only when the experience already has a goal.
• You're looking at a legacy NPS survey. Its settings are still in Appcues Studio.

Still stuck?

Collect the following and contact support:

• The experience URL from your browser's address bar.
• The Experience ID from Who changed this.
• The section you're trying to change.
• A screenshot of the Settings tab.