​
Overview

This article explains how the Userpilot SDK tracks and logs events related to flows within the Analytics tab. It covers the logic behind each event type, what they represent, and how this data helps you evaluate user engagement, identify drop-offs, and measure the overall effectiveness of your flows. The SDK records key events at both the flow and step levels, offering detailed insights into how users interact with your in-app experiences.

​
The goal of tracking these events

  1. Identifying how users interact with multi-step experiences
  2. Measuring completion rates and friction points
  3. Enabling targeted improvements to onboarding, adoption, and engagement flows

​
Key Metrics and completion overview

​
Key metrics for the flow

  • Total Shown: the number of unique users who received and saw the flow on their device.
  • Completed: the number of users who completed all the flow steps.
  • Dismissed: the number of users who dismissed the flow.
  • Average Time to Complete: the average time it took users to complete all the flow steps.
Screenshot2025 07 27at12 30 51 Pn
Each metric includes a visual indicator (green or red arrow) showing the percentage change compared to the previous period (e.g., +3% from the last 7 days).

​
SDK rules

This section breaks down the logic the SDK follows to track each flow event shown in the Analytics tab:

​
Total shown

Trigger conditions
  1. User views at least one step of the flow (even without interaction)
  2. User reaches the final step (counted as complete even without interaction)

​
Completed

Trigger conditions
  1. User completes all the flow steps
  2. User interacts with a button that executes a dismiss - Mark flow as completed action
Screenshot2025 07 27at12 34 51 Pn
  1. User clicks on the button that contains any action except dismiss
Screenshot2025 07 20at15 28 10 Pn
  1. User clicks on the image that contains any action, as shown in the screenshot below
Screenshot 2025-07-20 at 15.39.48.png
  1. If the flow step contains logic that references a step that doesn’t exist, the SDK should skip that step and mark the flow/step as completed.
Screenshot2025 07 27at12 40 41 Pn

​
Dismissed

  1. Clicks a CTA with a dismiss action (e.g. Dismiss and never show again)
  2. Press the ESC key
  3. Refreshes the page
  4. Navigates away mid-flow
  5. Flow exits due to frequency limit (e.g. shown once only)
NoteYou might notice that Dismiss and Complete events sometimes add up to more than the total Show count. This usually happens based on how users interact with the last step of the flow.For example, if a user reaches the final step and clicks the dismiss icon, Userpilot will log both a Complete and Dismiss event for that user.Screenshot2025 07 27at13 58 07 PnTo avoid this and track only one event (like Complete), you can:
  • Set the button action to “Dismiss and mark flow as completed”, or any other action
  • Set the dismiss icon action to “Go to next step”
This ensures only the Complete event is tracked.Screenshot2025 07 27at13 06 00 PnScreenshot2025 07 27at13 04 57 Pn

​
Filters and segmentation

You can filter the data by:
  • Segment - based on the defined user segments you created.
  • Company - filter by specific company segments you created.
Time Period - choose from preset ranges (e.g., Last 7 days) to view recent or historical trends Screenshot2025 07 27at13 26 08 Pn The Performance graph helps you visualize user interactions over time. It displays daily counts for:
  • Started
  • Completed
  • Dismissed
Each line on the chart represents a different metric. Hover over any point to see the exact data value for that date. You can switch between daily, weekly, and monthly views, compare results with the previous period to track performance trends, and change the chart type to a column view if you prefer. Screen+Recording+2025-07-27+at+13.31.03.gif

​
Steps Breakdown

This section shows how users interact with each step of your flow, especially helpful for multi-step flows. It helps you identify where users are most likely to drop off, so you can pinpoint steps that may need improvement or optimization. Screenshot 2025-07-27 at 13.35.39.png
You can click on the Shown, Drop-off, or Completed count to view the list of users who performed that action.

​
User-level activity table

Below the graph, the User Activity section provides detailed breakdowns at the individual user level, including:
  • Name and ID: displays the user’s name or identifier. Useful for recognizing individual users in the activity list.
  • Shown: the number of times the flow was delivered and displayed to the user.
  • Seen: the timestamp or time period indicating when the user last received or saw the flow.
  • Completed: indicates whether the user completed all flow steps.
  • Dismissed: shows if the user dismissed any step in the flow.
  • Goal Completed at: the date and time when the user completed a defined goal after seeing the flow.
Screenshot2025 07 09at22 53 35 Pn

​
Goal tracking

If your flow includes a goal (e.g., “Perform an Action”), Userpilot also displays:
  • Unique Users Seen - the number of unique recipients the goal applied to.
  • Goal Completion - the number of recipients who achieved the defined goal.
Screenshot 2025-07-27 at 13.40.48.png
For any questions or concerns, please reach out to support@userpilot.com