Changelog
Follow up on the latest improvements and updates.
RSS
new
Integrations
AI
Build an Appcues experience from Claude, ChatGPT or Cursor
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
Settings > Appcues AI
.new
Builder / Experiences
AI
Hand Appcues AI a mockup, a page or an old Flow, and it builds from that
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.
- Build from what you have.Upload a mockup or screenshot, or paste a public URL, and Appcues AI drafts the experience from its layout, copy and styling.
- Start from an old Flow.Ask Appcues AI to convert a legacy Flow into Flows 2.0. You get a starting point to finish in the builder, so check the styling and every step.
- Give it your source material.Attach a brief, a CSV or your event names, and @-mention a campaign, segment or Key Moment.
- Set rules once.Admins add context rules, such as audience and tone, inSettings > Appcues AI. They apply to every conversation.
Open Appcues AI from the Home page of the Appcues App at app.appcues.com.
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.
new
Integrations
AI
Get notified by email or Slack when experiences go live
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
Settings > Notifications
in the Appcues App, which is rolling out gradually. If you can't see it yet, ask your Appcues contact or support for access.new
Builder / Experiences
AI
Know when a live experience breaks
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.
new
Analytics
AI
Add a Retention card and see who comes back
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
Retention
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 Start
and Return
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.
Every experience used to stand on its own. Now group them around the outcome they're actually chasing.
A
Campaign
is a top-level container built around one measurable objective — usually a Key Moment like "completed setup" or "activated a paid seat." Inside it, Tactics
are distinct approaches that each attack the same goal from a different angle: awareness, blocker removal, follow-up, whatever the moment needs.Structure:
Campaign → Tactics → the Flows, Pins, Checklists, Embeds, and Banners your users see.
What you can do
- Give each Tactic its own audience and messaging without losing the shared objective
- Track reach, objective progress, and per-segment performance on the Campaign Dashboard
- Let Appcues build one for you — describe the goal and it proposes a name, objective, and starting Tactics
- Include a single experience in multiple Campaigns when it serves more than one goal
Grouping an experience into a Campaign doesn't change its targeting, frequency, or runtime behavior — Campaigns are for planning and measurement.
new
Analytics
Segmentation
AI
Key Moments: the milestones that matter, defined once
Raw events don't tell you when a user actually converts, adopts, or hits behavior worth acting on.
Key Moments
do.A Key Moment is a named, reusable milestone in the customer lifecycle — a trial conversion, an expansion purchase, a feature milestone, a first "aha." Build it from events, user conditions, or both. Define it once; reference it everywhere targeting and measurement live.
What you can do with them
- Combine multiple events with OR logic, or skip events entirely and define the moment purely by user conditions
- Layer on filters — user properties, segment membership, prior events, event-level attributes (order amount, plan tier, anything you send us)
- Fire once per user for true one-time milestones, or on every qualifying event for recurring behavior
- Reuse across Campaign objectives, Tactic targeting, and Dashboard metrics, so the numbers on your dashboard match the users your Campaigns are reaching
Two ways to build one
- Describe the moment in plain language and Appcues builds it for you
- Or open Settings > Key Momentsand configure it by hand
Key Moments 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.
Measuring anything beyond one flow's numbers meant exporting to a spreadsheet or rebuilding the question in a separate analytics tool.
Dashboards are your own views of product analytics. Each holds cards and each card answers one question.
Three card types available today:
- Metrics.Users, accounts, sessions, or events, as a trend over time, a breakdown across groups, or one headline number. Set a target, or compare across segments, accounts, campaigns, or the previous period.
- Funnel.Where users drop off across a sequence of steps, within a conversion window you set.
- Retention.Whether users come back and do it again, grouped into cohorts.
You can also describe what you want to measure to Appcues AI and let it build the cards, or the whole dashboard.
Dashboards 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.
new
Builder / Experiences
Developer / Installation
Run your own JavaScript inside a Flow or Embed
Content blocks couldn't fetch live data at render time. Click actions on buttons and images could only open a URL or track an event.
JavaScript snippets are custom code you write once, publish, and reuse. Two kinds:
- Content block.Add a Javascript block to a cell and it renders whatever your code returns at runtime — a live pull from your API, a value computed on the spot, anything you can build.
- Click action.On a Button, Image, or text link, run a snippet on click to trigger an action in your app — flip on dark mode from a Flow's button, open your support chat, or force a click in the app to change the state of the page and get ready for the next tooltip, a common problem on SPAs.
Available in Flows 2.0 and Embeds.
Load More
→