> 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/publish/mesure-outcomes-goal.md).

# Goal: measure outcomes

Define what success means for an experience, from completion stats to a tracked event, and know when to use Goal, the Success Tracker or an A/B test.

**Goal** defines what success means for an experience. Every experience tracks views and completion on its own; a goal adds the event you actually care about, and compares the users who reached it after the experience with those who reached it by themselves.

**You will have at the end:** one experience measured against the action it is meant to drive.

{% hint style="success" %}
**Why set a goal.** Know whether the experience actually drives the action, compare results across segments or variants, and get the data to refine your onboarding and your tours.
{% endhint %}

***

## What Goal measures

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FsSgwSy7mLeJFCXMovB89%2Fimage.png?alt=media&amp;token=af34d2dc-b029-44c6-a6cb-854ef36a3601" alt="The Goal section of Target and Publish"><figcaption></figcaption></figure>

Goal is available for every type of experience: tours, modals, surveys, banners, hints, checklists.

#### Views and completion

On by default for every experience, and it cannot be removed: how many users saw, started and completed it. A user has completed the experience when they reach its last step, or when they trigger the **Complete tour** action, an option of **Go to step**.

#### A tracked event

An event that marks success, such as a feature used or a form sent. You create the event on the fly, or pick one already in your project. Analytics then splits the users who reached it after going through the experience from those who reached it on their own.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FZd0RaPVcefjg02JJmD2A%2Fimage.png?alt=media&amp;token=59af616b-1012-4533-9237-6bdf99ad7e22" alt="The two goal options: views and completion stats, or a tracked event"><figcaption></figcaption></figure>

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FdhOF4bLyMC4vELnJf2qh%2FB-05-goal-attribution.png?alt=media" alt="Users who go through the experience before the goal event, compared with users who reach the goal event on their own"><figcaption></figcaption></figure>

## Set a goal

{% stepper %}
{% step %}

### Open Goal

In the experience, open **Target & Publish**, then the **Goal** section.
{% endstep %}

{% step %}

### Choose to track an event

Click **Track an event completion**. The default views and completion stats stay on.
{% endstep %}

{% step %}

### Pick or create the event

Select an existing event, or create one on the fly. Events are listed in **Success Tracker** > **Events**, see [Events](/docs/analyze/success-tracker/events.md).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FzBk5pXR5qv2UmaOYYcRg%2FB-s17-goal-event-tracker.png?alt=media&amp;token=cc3cf98d-dba6-4ab4-a377-e121d8a0a166" alt="Setup of your tracker: Create an event on the fly, a search field and the existing events grouped by source, with Test tracker and Save"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Publish, then read Analytics

The goal shows in the Analytics of the experience as soon as users reach the event, see [Read the goal in Analytics](#read-the-goal-in-analytics).
{% endstep %}
{% endstepper %}

## Read the goal in Analytics

Once a goal is set, the [Analytics](/docs/analyze/analytics.md) of the experience adds two blocks.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FqlL2decn4747bLkYecjK%2Fimage.png?alt=media&amp;token=acd52aa4-5f8e-4538-8d6e-e43669064e42" alt="Goal analytics: reached goal summary and comparison graph"><figcaption></figcaption></figure>

#### Reached goal summary

The number and the share of users who reached the goal. Click it to open the detailed view.

#### Goal graph

A graph of the goals reached after going through the experience, compared with the goals reached on their own. Click a point of the graph to see, for that date, the users behind it and how they interacted with the experience.

## Goal, Success Tracker or A/B test

| You want to know                                                             | Use                                                 | Scope                              |
| ---------------------------------------------------------------------------- | --------------------------------------------------- | ---------------------------------- |
| Did this experience lead users to the action?                                | **Goal**                                            | One experience                     |
| Do users adopt a feature, or go through activation, whatever the experience? | [Success Tracker](/docs/analyze/success-tracker.md) | Your product, across experiences   |
| Which version of a tour or a modal works better on the goal?                 | [A/B test](/docs/analyze/a-b-test.md)               | One tour or modal and its variants |

For tours and modals, the Goal section also holds **Start A/B Test**. The A/B test splits the Who audience between variants and compares them on the goal you set here. Variants, traffic split and results are in [A/B test](/docs/analyze/a-b-test.md).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FcM5oqB6u6n5saJu2Tplk%2Fimage.png?alt=media&amp;token=5b9a095d-0cf0-4b06-a98e-ed2a5c9b0065" alt="The A/B test block in the Goal section of a tour"><figcaption></figcaption></figure>

<details>

<summary>The A/B test in short</summary>

* **Start A/B Test** creates the **Original** and a **Variant A**, a copy of the original. Add one more variant if needed, up to three in all, copied from the Original or from Variant A.
* A slider splits the Who audience between the variants, at random. Each variant gets at least 10% of the traffic and at most 90%.
* Variants can be previewed and edited from the Goal section.
* **Cancel test** stays available until you publish, and removes the variants and their edits. **Publish** starts the test.
* Results show in the **Insights** tab of the Analytics of the experience: performance per variant, a confidence tracker, and the option to set the winning variant as the default.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FnxjBcFP2U0IaIppgHHRk%2Fimage.png?alt=media&amp;token=8c9576f5-2673-4153-bf94-668158705f6e" alt="A/B test in the Goal section: the Original and its variants, with the audience split slider"><figcaption></figcaption></figure>

The full guide is in [A/B test](/docs/analyze/a-b-test.md).

</details>

## From your assistant

Ask: *"How is the Profile Page Quick Guide doing? Where do users drop off?"* The assistant returns the completion rate and the step that loses the most users. That is completion, not the goal: read the goal in the Analytics of the experience. More in [What to ask?](/docs/integrations/mcp/what-to-ask.md)

## Verify

* The Analytics of the experience shows the goal summary once at least one user reached the event.
* The event exists: it is listed in [Events](/docs/analyze/success-tracker/events.md), in the Success Tracker, with its description and, for a no-code event, its conditions. The list does not keep a history of when the event was received: to follow it over time, create a tracker in the [Success Tracker](/docs/analyze/success-tracker.md).

## Go further

* [Analytics](/docs/analyze/analytics.md): read the stats of an experience.
* [Success Tracker](/docs/analyze/success-tracker.md): activation and feature usage trackers.
* [A/B test](/docs/analyze/a-b-test.md): test variants of a tour or a modal.

**Next page:** [Boost: promote a changelog post](/docs/publish/increase-visibility-boost.md)