> 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/trackers.md). # Trackers Create an activation tracker for a journey or a feature usage tracker for one feature, limit it to an audience, and test it in your app before saving. A tracker turns events into a number you can follow. An activation tracker chains several events into steps; a feature usage tracker follows a single event. Click **New Tracker** on the [Success Tracker dashboard](/docs/analyze/success-tracker/overview.md) and pick the kind you need. ## Choose the kind of tracker | You want to know | Pick | | ------------------------------------------------------------------ | ---------------------- | | How many users go from sign-up to first value, and where they stop | **Activation tracker** | | Whether users adopt one feature, and how often | **Feature usage** |
New tracker chooser: A Activation tracker, to track success across several steps, B Feature usage, to track the usage of one feature
## Create an activation tracker
Activation tracker setup with steps and audience
{% stepper %} {% step %} ### Name the tracker Give it a name and a description your team will understand, such as "Activation: first project created". {% endstep %} {% step %} ### Add the steps Each step is one event. Click **Select event** to pick an existing event, or create one on the fly. **Add step** adds the next one, and the trash icon removes a step. Keep it short: three to five steps read better than ten.
Event picker with Create an event on the fly and existing events
{% endstep %} {% step %} ### Limit the audience, if needed Under **Tracker audience**, pick an existing segment or create one on the fly. The panel shows how many users are selected. Without an audience, the tracker counts everyone. {% endstep %} {% step %} ### Test it Click **Test Tracker**. Your app opens with an overlay at the bottom of the screen that marks each step done or pending as you perform it.
Testing overlay of an activation tracker
{% endstep %} {% step %} ### Create it Click **Create Tracker**. The tracker appears on the dashboard and starts counting. {% endstep %} {% endstepper %} ## Create a feature usage tracker Pick **Feature usage** in the chooser.
Feature usage tracker setup
{% stepper %} {% step %} ### Name the tracker For example, "Feature usage: CSV export". {% endstep %} {% step %} ### Pick the event Select an existing event, or create one on the fly. {% endstep %} {% step %} ### Limit the audience, if needed Same as for an activation tracker: an existing segment, or one created on the fly. {% endstep %} {% step %} ### Test it **Test Tracker** opens your app with an overlay that shows the event and how many times it fired, live. {% endstep %} {% step %} ### Create it Click **Create Tracker**. {% endstep %} {% endstepper %} ## Events created on the fly An event created on the fly lives inside this tracker. It uses the same conditions as a saved event: element, input and page. See [Events](/docs/analyze/success-tracker/events.md#add-conditions).
On the fly event conditions
{% hint style="info" %} **Save the events you will reuse.** If the same action matters in a tracker, a Goal and a trigger, create it once in **Events** and select it everywhere. Rebuilding it on the fly each time gives you several definitions of the same action. {% endhint %} ## Related * [Overview](/docs/analyze/success-tracker/overview.md): read the dashboard of a tracker * [Events](/docs/analyze/success-tracker/events.md): create and test events * [Segments](/docs/analyze/users-and-segments/audience/segments.md): the audiences a tracker can be limited to * [Success Tracker](/docs/analyze/success-tracker.md): Goal, A/B test or Success Tracker