> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/analyze/success-tracker.md). # Success Tracker Track what users do in your product, not only what they do in your experiences: activation journeys, feature usage, and the events behind them. The Success Tracker measures what users do in your product, whether or not they saw an experience. It answers questions like "how many new users reach their first project?" or "is anyone using the new export?". It is built from **events**, the actions you want to count, and **trackers**, which turn those events into a funnel or a usage curve. ## What it tracks {% columns %} {% column width="50%" %} ### Activation tracker A sequence of steps, each tied to an event. It shows how many users enter, how many complete every step, and where they stop. Use it for the path to value: sign up, create a first project, invite a teammate. {% endcolumn %} {% column width="50%" %} ### Feature usage tracker One event, followed over time. It shows how often the feature is used, and by how many distinct users. Use it for adoption: is the new feature used, and is usage growing? {% endcolumn %} {% endcolumns %} Both can be limited to an audience, such as a [segment](/docs/analyze/users-and-segments/audience/segments.md) of new users, so the numbers describe the people you care about. #### Events An event is a user action Jimo can detect without code: an element clicked, hovered or present, an input filled, a page visited. You define it once in **Success Tracker > Events**, and reuse it everywhere. See [Events](/docs/analyze/success-tracker/events.md). ## Goal, Success Tracker or A/B test Three features measure success, at three different levels. Pick the one that matches your question.

Goal measures one experience, an A/B test compares versions of one tour, the Success Tracker measures the whole product, all three built on the same events

| | Goal | A/B test | Success Tracker | | -------------- | ----------------------------------------------- | ---------------------------------------- | -------------------------------- | | **Question** | Did users who saw this experience do the thing? | Which version of this tour works better? | Do users do the thing at all? | | **Scope** | One experience | One tour, two or three versions | Your product, across experiences | | **Built from** | Completion, or one event | The tour's Goal | Events, in steps or alone | | **Set up in** | Target & Publish > Goal | Target & Publish > Goal | Success Tracker | | **Read in** | The experience's **Reached goal** | The tour's **A/B Test** block | The tracker's dashboard | The three share the same events. A typical setup: an activation tracker shows that users stall at "invite a teammate", a tour aims at that step with the invite event as its [Goal](/docs/publish/mesure-outcomes-goal.md), and an [A/B test](/docs/analyze/a-b-test.md) compares two versions of that tour. {% hint style="info" %} **A reached goal is not always thanks to the experience.** Users can reach a goal without seeing your tour. The Goal graph separates goal events during the experience from all goal events, so you can see the difference. See [Metrics by experience type](/docs/analyze/analytics/metrics-by-experience-type.md#reached-goal). {% endhint %} ## How the activation funnel counts The activation funnel is read over a period, set with the dashboard's time filter. * **Entered** is the number of users who entered the tracker in the period, and **Completed** the number who performed every step. * Each step counts users who performed its event **at least once in the period, in any order**. Because order is not enforced, a later step can count more users than an earlier one, when people skip ahead. That is not an error: it tells you that the step you thought came first is not the natural entry point.

Activation funnel of four steps where step 3 counts more users than step 2, because steps are counted in any order and users skipped ahead

## Get started {% stepper %} {% step %} ### Create the events you need List the few actions that mean success, and create one event per action. See [Events](/docs/analyze/success-tracker/events.md). {% endstep %} {% step %} ### Create a tracker An activation tracker for a journey, a feature usage tracker for one feature. See [Trackers](/docs/analyze/success-tracker/trackers.md). {% endstep %} {% step %} ### Read the dashboard Watch where users stop, then aim an experience at that step. See [Overview](/docs/analyze/success-tracker/overview.md). {% endstep %} {% endstepper %} ## From your assistant With the [Jimo MCP](/docs/integrations/mcp/what-to-ask.md), your assistant reads any activation tracker by name, for everyone or for one segment, over the last 30 days unless you give another period. > "Where do new users stall before activating? Compare Trial Users with Paying Users." It returns the users entered and completed, the step where they fall out, and the same funnel scoped to a segment. When a project has several activation trackers, name the one you mean. See [What to ask?](/docs/integrations/mcp/what-to-ask.md). ## Verify * Your events show in **Success Tracker > Events**, and each one fires when you test it. * Your tracker's dashboard shows users entering the first step. * Each step of the funnel has users, or you know why it does not. ## In this section The pages follow the Success Tracker screen: the **Trackers** tab, the **New Tracker** button, then the **Events** tab.


Overview	The Trackers tab: read the cards, the funnel and the usage curves	Overview	D2-c06-overview.png
Trackers	New Tracker: create and test an activation or feature usage tracker	Trackers	D2-c07-trackers.png
Events	The Events tab: the events everything else uses	Events	D2-c08-events.png

## Go further


Goal	Measure one experience against an event	Goal: measure outcomes	B-c05-goal.png
Users & Segments	The segments a tracker can be limited to	Users & Segments	D2-c09-users-and-segments.png

**Next page:** [Admin and settings](/docs/settings/admin-and-settings.md)