Once a campaign is live, you want to know how many of the users it reached went on to complete its Key Moment.

Every campaign and tactic has a Dashboard tab that shows you that. The top row runs from reach to objective: a reach-to-objective funnel, completions, drop-off and conversion rate, all counting only users who saw your content. Below that you get the objective's trend against its target, exposed versus unexposed users over time, and, on a campaign, objective completion split by tactic.

To have a card's numbers explained, open its ⋮ menu and click .

Read the docs · Ask support

Surveys were one of the last reasons to keep building in classic Flows. Survey blocks add Text input, Single Select, Multi Select and Rating questions to Flows 2.0 and Embeds. Build it by hand or ask AI to create your survey.

Sending different users different content meant building a separate Flow for each audience. With conditional actions, one button or image sends each user down their own path, based on a survey answer or a user profile property:

Survey blocks are in beta. Conditional actions need web SDK 7.32.0 or later.

Read the docs: Surveys · Conditional actions · Ask support

Building an experience used to mean leaving your AI chat for the Appcues builder, even when the brief, the copy and the context were already sitting in the chat.

The Appcues MCP Server can build experiences. Describe one in Claude, ChatGPT, Cursor or any client that accepts a custom MCP server, and it creates a draft in your account. You can also ask it to clone an existing experience and swap the copy, or to return a screenshot of a step so you can check the result without leaving the chat.

Everything it builds starts as a draft. Nothing goes live until you publish it or tell your agent to.

For the best results, add our context file to your AI client. Experience building is in beta. An admin turns the MCP Server on under .

Read the docs · Ask support

If the design already lives in a mockup, a landing page or a PRD, retyping it as a prompt wastes the work you've done.

Open Appcues AI from the Home page of the Appcues App at app.appcues.com.

Read the docs · Ask support

A funnel tells you how many people dropped out of the path you designed. It can't tell you where they went instead.

User Journeys charts the paths people take through your product, built from the pages they viewed in each session. Pick a page and see sessions that start on it, end on it, or pass through it. Switch to page groups to trace whole areas of your product instead of single URLs.

No additional setup needed. Appcues builds your pages and page groups from your traffic.

Save a journey as a view your team can reopen, or ask Appcues AI to build one.

User Journeys is under Dashboards in the Appcues App.

Read the docs · Ask support

To find out a teammate had published a Flow, or that Appcues had raised a new recommendation, you had to open Appcues and look.

Notifications bring those events to you. Pick the ones you want to hear about: an experience published or unpublished, or a new issue or opportunity on the Recommendations page. For each one, choose to hear about it immediately or in a daily, weekly or monthly digest.

Personal notifications go to your own email. Admins can also send account notifications to a shared inbox, a Slack channel, or both.

Account notifications take one email address per event. To reach several people, use a team alias or Slack.

Set them up in in the Appcues App, which is rolling out gradually. If you can't see it yet, ask your Appcues contact or support for access.

Read the docs · Ask support

You publish an experience, confirm it works, and move on. A change to your site breaks the selectors it depends on, and the experience quietly stops reaching users. It can sit like that for weeks until someone opens the Flow's analytics.

Appcues now watches your live experiences and raises a recommendation when one starts failing for users — a sudden spike, or a slower climb over several days. Open it to see what's going wrong and what to do, and apply an AI action if one's available to fix it in place.

Set up email notifications so you hear about a spike without having to check the Recommendations page.

Available in the Appcues App, which is rolling out gradually. If you can't see it yet, ask your Appcues contact or support for access.

Read the docs · Ask support

Working out whether users came back to a feature meant exporting events to a spreadsheet or rebuilding the question in a separate analytics tool.

A card groups users into cohorts by the event that started them, then shows how many of each cohort came back and did a second event in the periods after. Put the same event in both the and slots and you get "of the users who tried this, how many used it again?" Read it as a cohort grid, one row per cohort, or as a trend over time showing how fast retention falls off.

Cohort by start date, or by up to 10 segments or accounts, at daily, weekly or monthly granularity.

Retention cards are part of the Appcues App, which is rolling out gradually. If you can't see them yet, ask your Appcues contact or support for access.

Read the docs · Ask support

Every experience used to stand on its own. Now group them around the outcome they're actually chasing.

A is a top-level container built around one measurable objective — usually a Key Moment like "completed setup" or "activated a paid seat." Inside it, are distinct approaches that each attack the same goal from a different angle: awareness, blocker removal, follow-up, whatever the moment needs.

Structure:

Grouping an experience into a Campaign doesn't change its targeting, frequency, or runtime behavior — Campaigns are for planning and measurement.

Read the docs · Ask support