After building your Flow in the Builder, click Target & Publish to open the settings page. This is where you control every aspect of how the Flow reaches your users. Each section below corresponds to a panel on that page.

Schedule your Flow

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

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

For details, see Schedule experiences.

Set the trigger type

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

Manually triggered Flows ignore all other targeting rules — frequency, page targeting, and audience conditions are bypassed. The Flow 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.

Set page targeting

Page targeting defines where the Flow appears — which URLs and which domains.

In the Page Targeting panel, add one or more URL conditions (exact match, contains, starts with, matches regex).

Select which domains the Flow should display on. Use this to limit a Flow to production, staging, or a specific environment.

For setup instructions, see Page targeting. For dynamic URLs, see Targeting dynamic URLs. To verify your conditions, use the Test Page Targeting tool.

Set audience targeting

The audience panel defines who sees the Flow.

• All users — every user on a matching page sees the Flow.
• Users in a segment — target a saved segment. Segments let you reuse audience definitions across multiple Flows and track which messages reach which groups.
• Specific users — build conditions using user properties, group properties, language, Flow/Checklist/Pin/Banner completion, events, segments, or email and push notification status.

For setup instructions, see Audience targeting. To target by properties, see Targeting by user and group property.

Set frequency

Frequency controls how often a qualifying user sees the Flow.

• Show once — the Flow shows one time per user and never again.
• Show every time — the Flow shows every time the user qualifies. Combine with audience conditions to control repetition (for example, "show every time the user has not completed X").

For detailed configuration including recurring schedules and interval-based frequencies, see Set Flow frequency.

Frequency limit

Below the frequency setting, you can enable a global frequency limit that caps how often a user sees any Flow or NPS across your entire account. For example, "no more than 1 per hour."

This is an account-wide setting, not Flow-specific. See Experiences frequency limit.

Set priority

When multiple Flows qualify for the same user on the same page, Appcues shows one per page view. Priority controls which one goes first.

By default, the most recently published Flow takes priority. Click View Flow Priority to see all Flows ranked in order and adjust weights.

For details on how priority is evaluated and how to set weights, see Set Flow priorities.

Set a goal

Goals measure whether users take a specific action after seeing the Flow — for example, completing a setup wizard or visiting a pricing page.

• No goal — only tracks Flow views and completion.
• Choose an existing goal — select from saved goals in the dropdown.
• Create a new goal — define a new goal and automatically link it to this Flow. Results appear on the Flow's analytics page.

For details on creating and managing goals, see Goals overview.

Set completion actions

Define what happens when a user completes the Flow.

• Redirect to a different page — sends the user to a URL after the final step.
  • For a page within your app, enter the path only (for example, /profile).
  • For an external URL, enter the full address including https://.
• Trigger Appcues content — launch another Flow when this one completes. Both Flows must be published. If the triggered Flow is on a different page, combine this with "Redirect to a different page."

For more on chaining Flows, see Link Flows together.

Confirm it worked

After configuring settings and publishing:

• Visit the targeted page as a user who matches the audience rules. The Flow should appear.
• Check the Eligibility tab on the user's profile in Studio to verify they qualify.
• If using a goal, complete the goal action and confirm it registers on the Flow's analytics page.

If settings aren't working as expected

• Flow doesn't appear — check trigger type, page targeting, audience, and frequency in that order. See Troubleshoot Flows for a full diagnostic.
• Flow appears on the wrong page — review page targeting URL conditions. Use the Test Page Targeting tool to verify.
• Wrong users see the Flow — check audience conditions and confirm user properties are being sent with the expected values.
• Flow doesn't repeat — frequency may be set to Show once, or the user already qualifies as "seen." See Set Flow frequency.
• Multiple Flows competing — check the priority table and adjust weights. See Set Flow priorities.