Analyze Embed performance
Use Embed analytics to see how many users are viewing and interacting with your Embeds, identify issues with element targeting, and track engagement trends over time.
Table of Contents
View the analytics page
- Open Appcues Studio and go to Experiences > Embeds.
- Click the Embed experience you want to analyze. The analytics page opens.
The page shows a scoreboard of key metrics, an activity chart, a step breakdown, and a list of recent users. You can change the date range at the top of the page — this applies to everything on the page. You can also apply a segment to filter the data and view the publish history of your Embed.

Scoreboard
The scoreboard at the top shows four metrics for the selected date range:
- Unique users — The number of distinct users who saw the Embed during the date range.
- Total views — The total number of times the Embed was shown. This counts every occurrence, not just unique users. If one user sees the Embed on two separate occasions, that counts as 2 total views.
- Total interactions — The total number of times users interacted with the Embed (clicked a button, clicked an image).
- Total issues — The total number of errors encountered while displaying the Embed, such as when the target element isn't found on the page.
Two things to keep in mind when reading these metrics:
- Total views equals unique users when each user only sees the Embed once. If total views is significantly higher than unique users, users are seeing the Embed multiple times (expected when 'show every time is selected).
- High views but low interactions usually means the Embed is rendering but users aren't engaging with its content. Consider adjusting the content, placement, or call-to-action.
Embed activity chart
The chart shows Embed views over time, plotted by day. Hover over data points to see the exact count for a specific date.
Use this chart to spot trends — for example, a sudden drop may indicate a deployment changed the target element, or a spike may follow a new audience being targeted.

Step breakdown
The step breakdown table shows per-step metrics for the Embed:
- Views — The number of times users saw the step.
- Interactions — The number of times users interacted with the step (clicked a button, submitted a form, etc.).
- Unique users — The number of distinct users who saw the step.
Click the step thumbnail or the external link icon to open the step in the Builder.
If a step shows 0 views, verify that the target element exists on the page and that the CSS selector is valid. See Troubleshoot element targeting.

Issues reporting
The Issues Report section shows the most recent errors your users encountered with the Embed. The table includes the user ID, the URL, the CSS selector involved, and when it was last seen. These are step_error events — errors Appcues encountered while trying to display the Embed.
Common reasons for Embed issues:
- The target element doesn't exist for some users (e.g., role-based UI differences).
- Your app was updated and the CSS selector changed.
- The target element loads after the Appcues SDK evaluates the page.
- The selector is dynamically generated and not stable across page loads.
See Issues Reporting for more details on interpreting and resolving issues.
Recent users
The Recent Users section lists the most recent users who saw the Embed, along with the date and time. Click any user to open their full user profile with all attributes.
Export Embed data
- On the Embed's analytics page, click Export.
- Choose Basic CSV or Full CSV. The Full CSV includes your custom user properties alongside the event data.
- Set the date range and download.
- The exported file includes a
namecolumn with the event type (e.g.,experience_started,step_interaction) and columns for user ID, timestamp, and page URL.
Embed events reference
Use these event names when building reports outside Appcues, setting up integration triggers, or querying the Public API.
| Event | When it fires |
|---|---|
experience_started |
The Embed is rendered on the page for a user. This is the event that powers the "Total views" metric. |
step_seen |
A step within the Embed is displayed to the user. |
step_interaction |
A user interacted with the Embed (clicked a button, clicked an image). This powers the "Total interactions" metric. |
step_error |
An error occurred displaying the Embed (e.g., target element not found). This powers the "Total issues" metric. |
step_recovered |
An Embed that previously errored recovers after Appcues finds the target element on the page. |
|
A user completed a step within the Embed (e.g., clicked a button that advances to the next step or finishes the Embed). |
|
The user clicked a button configured with the Snooze action, postponing the Embed for later. |
|
A user completed the final step within the Embed (e.g., clicked a button configured with the Next action). |
experience_dismissed |
The user explicitly closed or dismissed the Embed. |
If the data doesn't look right
- Total views is 0 but the Embed is published. Check that your audience targeting matches actual users and that the Embed is published to the correct domain. Verify the target element exists on the page using the Appcues Debugger. See Troubleshoot Embeds.
- Issue count keeps climbing. The count accumulates over the selected date range. Focus on whether the rate of new issues is increasing, not the total. If the same selector keeps erroring, update the CSS selector to a more stable one. See Troubleshoot element targeting.
- Data appears delayed. Events can take a few minutes to appear in analytics. If data is missing after 15 minutes, check that Appcues is installed correctly on the relevant pages using the Appcues Debugger.
- CSV export is empty. Verify the date range covers the period when the Embed was live. Also confirm that you're exporting from a published (not draft) Embed.
-
Step breakdown shows 0 views but Total views is not 0. The scoreboard counts
experience_startedevents while the step breakdown countsstep_seenevents. If the target element fails to render after the experience starts, you'll see this discrepancy — check the Total issues count for errors.
Still need help? Contact support with your Embed ID, the date range you're looking at, and a screenshot of the analytics page.