Use Pin analytics to see how many users are seeing and interacting with your Pins, identify issues with element anchoring, and track engagement trends over time.

View the analytics page

1. Open Appcues Studio and go to Experiences > Pins.
2. Click the Pin experience you want to analyze. The analytics page opens.

The page shows an overview chart, individual Pin stats, issue reporting, 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 Pin.

The chart

The chart shows Pin engagement over time, plotted by daily unique users. Hover over data points to see stats for a specific day.

Version markers appear on the chart when a change to the Pin is published and seen by a user. Use these to correlate engagement changes with specific edits.

Individual Pin stats

Each Pin within the experience has its own row of metrics:

• Opens (Icon w/ Tooltip Pins) — the number of times users expanded the tooltip to see the content.
• Clicks (Button Pins) — the number of times users clicked the button to trigger the associated action.
• Unique users — the number of distinct users who opened or clicked the Pin.
• Impressions — the total number of individual times the Pin was displayed on the page, regardless of interaction.
• Issues — the count of errors encountered while displaying the Pin. Since Pins are persistent, this count can only increase over time.

Two things to keep in mind when reading these stats:

• High impressions but low opens/clicks usually means the Pin is visible but users aren't engaging with it. Consider changing the icon, adjusting the position to be closer to the relevant element, or switching the behavior from "on click" to "on hover."
• Unique users is much lower than impressions is expected for persistent Pins — the same users see the Pin every time they visit the page.

Issues reporting

The Issues Report section shows the most recent errors your users encountered with the Pin. The table includes the issue description, the reason, the CSS selector involved, and when it was last seen.

Common reasons for Pin 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 user navigated away while the Pin was still loading
• The selector is dynamically generated and not stable

Click the link in the table to open the Chrome Extension Builder and fix the affected Pin. The table shows the 25 most recent events — export the full CSV for a complete list.

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 Pin, along with the date and time. Click any user to open their full user profile with all attributes.

View Pin events in Events Explorer

Events Explorer gives you a timeline view and lets you search for individual users.

1. Open Events Explorer in Studio.
2. In the Event Source dropdown, select Pin Events.
3. Select the Pin experience you want to explore. You'll see events broken down by type: Opens for Icon w/ Tooltip Pins, Clicks for Button Pins.
4. Click any event type to see a chart with total and unique event counts, and a searchable table of individual events.

Use the date range picker at the top of the page to adjust the time window.

Export Pin data

You can export data from two places, depending on what you need.

From the Pin analytics page

1. On the Pin's analytics page, click Export.
2. Choose Basic CSV or Full CSV. The Full CSV includes your custom user properties alongside the event data.
3. Set the date range and download.

The exported file includes a name column with the event type (e.g., step_seen, step_interacted) and columns for user ID, timestamp, and page URL.

Impression events (button_pin_seen or icon_seen) aren't surfaced in these exports. To access that data, use the Public API.

From Events Explorer

1. In Events Explorer, navigate to the specific event type you want to export.
2. Set the date range.
3. Click Export CSV.

This export includes only the selected event type, which is useful when you need a focused dataset — for example, exporting only step_error events to investigate anchoring issues.

Pin events reference

Use these event names when building reports outside Appcues, setting up integration triggers, or querying the Public API.

Pin events are also sent to any enabled client-side integrations, including experience_started, icon_seen, and step_seen.

Default properties (included with every event)

If the data doesn't look right

• Impressions are 0 but the Pin is published. Check that your audience targeting matches actual users and that the Pin is published to the correct domain. Verify the target element exists on the page. See Troubleshooting Pins.
• Issue count keeps climbing. This is expected for Pins — the count accumulates over time and doesn't reset. 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.
• 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 Pin was live. Also confirm that you're exporting from a published (not draft) Pin.
• step_error events appear for some users but not others. The target element likely exists for some users based on role, permissions, or app state, but not for others. This is common when Pins are anchored to admin-only UI elements. Adjust your audience targeting to exclude users who won't have the target element.

Still need help? Contact support with your Pin ID, the date range you're looking at, and a screenshot of the analytics page.