Skip to content

Appcues

Appcues adds guides, checklists and announcements to an app and can use the app’s own events to decide who sees them.

Visit Appcues

What should your app send before Appcues can guide a customer?

Install the web integration and identify the visitor with a stable ID that does not reveal their email address. Decide which app actions matter. Send the event for a completed action, such as a saved billing address, after your app confirms the save.

A flow may start for people who have not saved their address. Your app still owns permission to change it and displays the result.

What sets Appcues pricing and how many guides can run?

Appcues counts unique users identified in a rolling 30-day window, including people who never see a guide. The current Grow offer starts at US$9,000 a year and lists 25 published experiences and pricing that scales with usage up to 50,000 monthly active users.

Enterprise is custom and lists 100 published experiences. Check the quote for actual volume and add-ons. Count identified people and published experiences separately.

How can a translated flow stay usable with a keyboard?

For web Flows 2.0, enable localization in Experience Settings. Appcues supports translation files and can switch the layout automatically for a right-to-left device language. The vendor says modals and slideouts hold keyboard focus until progression or dismissal. A tooltip can move focus into the guide while still allowing the person to reach other parts of the page.

Flows 1.0 use a separate workflow. Set up localization while that flow is unpublished. If it is live, Appcues suggests translating a copy before replacing it. An unmatched language shows the original copy, and right-to-left layouts need custom theme styling. Checklists are outside the documented Flows 2.0 translation workflow.

Preview each needed translation and check how focus returns after closing. Keep the app control available if the guide never appears.

How can you plan a billing-address hint without touching a customer record?

Draw a settings screen and two fictional accounts. Keep the exercise on paper with no integration, real addresses or saves.

  1. Choose who needs help
    Show the hint to a person allowed to edit their address who has not saved one. Leave it off for a person who cannot edit.
  2. Plan what success means
    Record the app’s saved result separately from the guide’s completion. Mark how someone can dismiss the hint and find the setting later.
  3. Keep what you would need to switch
    Appcues documents CSV exports for experience performance, steps and responses. Keep the copy and display rules independently. Remove the script or tag after you have checked the settings page without it.