Analytics
How Jimo counts views, completions and drop-offs, which number answers which question, and what to do when users stop halfway through an experience.
Every experience comes with its own analytics: who saw it, who finished it, where people stopped, and whether it changed what they did next. This page explains how each number is counted, so you can read them without guessing and act on what they say.
Open any experience from its list: its analytics sit at the bottom of the experience page, in the Statistics and Issues tabs. Every number can be filtered by date range.

How Jimo counts
Most confusion on analytics comes from three words that sound alike: reached, started and completed. They are not the same population.

Users reached
Users who saw the first step of a tour, survey or banner, or at least one hint of a hint group
Yes
Started
Users who began the experience. For a survey, users who answered at least one question
Yes
Completed
Users who reached the end: the last step of a tour, or a Complete tour action on a button (a Go to step option); a submitted survey; all tasks of a checklist
Yes
Step views
Users who saw a given step
Yes
Views (graphs)
Every display, including repeat displays to the same user
No
What counts as a view
A view is a display of the experience to a user, not a click. For a tour or a survey, it is the first step appearing on screen. For a hint group, it is any one of its hints. For a checklist, it is the checklist being seen at least once. For a Resource Center, it is the user opening it.
Why the graph can be higher than the KPI
The KPI card counts each user once. The daily graph behind it counts every display. A user who sees a banner on three different days adds one to Users reached and three to the graph.

Completion rate
Completion rate is completed users divided by the users the experience counts from: users reached for a tour, users who started for a survey, users who viewed it for a checklist. A survey completion rate is often higher than you expect, because people who never answered the first question are left out.
Drop-off
Drop-off is the share of users who saw a step but not the next one. Step 1 is measured against the users who started. A step with a 50% drop-off lost half the people who reached it, whatever the size of the tour.
Clicks
The Total number of clicks card counts clicks on buttons that do something beyond moving the experience forward: Open Post, Navigate To, Launch Experience, Run JavaScript Code, Open Calendar. Buttons that only go to the next step or close the experience are not counted.
For the exact KPIs of each experience type, see Metrics by experience type.
Which number answers which question
Start from your question, then read the one number that answers it.
Did people see it?
Users reached (Unique viewers for hints)
Statistics tab
Did they finish it?
Went through all steps, Finished submissions, Completed checklist
Statistics tab
Where do they stop?
Step histogram, biggest drop-off
Statistics tab, tours with 2 steps or more
Did they click what matters?
Total number of clicks
Statistics tab
Is it working for one audience?
Reached and completed per segment
Your assistant, see below
Is something broken?
Steps whose element was not found, hidden, or matched twice
Issues tab
Read a funnel
For a tour with two steps or more, the step histogram shows how many users saw each step. The first bar is always 100%: it equals the users who started. Each next bar shows how many are left.

Read it in three passes.
The shape
A funnel that declines a little at every step is normal: some users always leave. A funnel with one cliff, where most users leave at the same step, points at that step.
The biggest drop-off
The biggest drop-off is the step that loses the most users in number, not the highest rate. A 60% drop on a step seen by 5 people matters less than a 30% drop on a step seen by 400.
For example, in the four-step tour of the figure above, seen by 100 users, 38 reached step 2: 62 users, 62%, left at the first transition. Steps 3 and 4 kept most of those who got there, 32 then 29. The problem is step 1 or the move to step 2, not the end of the tour.
Small numbers
Below a few dozen users per step, one user changes the percentages a lot. Wait for more data before you rewrite a step.
What to do with a drop-off
Work through the likely causes in this order, from the cheapest to check to the most expensive to fix.

The step could not show
Open the Issues tab first. If the step's target element was not found, was hidden, or matched several elements, users never saw that step, and the funnel stops there for a technical reason. Fix the element, see Targeting on dynamic apps.

The Issues tab shows an Issue reporting table with the columns User, Step, Issue (for example "Could not find element with selector ..."), URL and Date, and a Troubleshoot button above it. Each row is one occurrence: one user, on one step, on one page.
The step asks for something the user cannot do yet
A step that waits for a click on an element on another page, or for a form to be filled, loses everyone who is not there. Check what moves the user to the next step in the Steps Triggers.
The experience shows at the wrong moment
A tour that opens while users are in the middle of a task gets closed. Review its trigger in Show on, its timing in When and its pages in Where. An experience launched by a button action (Launch Experience) checks only its Who: its Where and When do not apply, so look at the step that launches it. If the launched experience uses No automatic trigger, only its Goal remains: the experience that launches it decides who sees it.
The step says too much
Long copy and several buttons on the same step slow people down. Shorten it, keep one clear action, and compare the next weeks of data. To compare two versions at the same time, run an A/B Test.
The audience is too broad
If users who already know the feature are in the audience, they leave early because they do not need the tour. Narrow it in Who.
From your assistant
With the Jimo MCP connected, your AI assistant reads the same analytics and does the comparison for you.
"Where do people drop off in the onboarding tour, and is anything broken on that step?"
It returns the step-by-step funnel with the biggest drop-off, then checks the issues reported for the same experience. Other questions that work: "How are we doing this month?", "Compare how Trial Users and Paying Users adopt the new tour", "Is anything broken since our deploy on Monday?". The weekly_digest prompt chains them into one weekly summary. See What to ask?.
Verify
Users reached on the KPI card is lower than or equal to the total of its daily graph.
The Issues tab is empty for the experience you are analyzing, or you know why it is not.
In this section
Go further
Next page: A/B Test
Last updated





