# Mesure outcomes (Goal)

You’ll find the **Goal section** in the **Target & Publish** settings of any experience.\
It helps you measure how well your experience performs against the outcomes you care about—whether that’s **completion rate**, a **specific tracked event**, or, for tours, the results of an **A/B test**.

<figure><img src="/files/a7LPjlW77MPKXWL3M9DC" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**Why it’s useful:**

* Know if your experience actually drives user actions.
* Compare success across different user segments or variants.
* Get data to refine your onboarding, walkthroughs, or feature tours.
  {% endhint %}

The Goal section is structured in two parts:

1. **Define Success** – available for all experiences. Default completion stats plus optional event-based tracking.
2. **A/B Test (Tours only)** – allows you to create and manage test variants directly from the goal settings.

***

## Define Success (All Experiences)

This section is available for every type of experience (Tours, Surveys, Banners, Hints, Checklists…).\
It helps you track and compare **how many users complete the experience** or reach a specific outcome you define.

### Goal Options

You have two options to measure success:

* **Track Views & Completion Stats** (default, always enabled)
  * Monitors how many users start and complete the experience.
  * This generic tracker **cannot be removed**.
* **Track a Goal (Event-based tracking)**
  * Measure success by monitoring a specific in-app event.
  * Lets you compare users who achieved the goal **after going through the experience** vs. those who reached it **on their own**.

<figure><img src="/files/dsnEEDuv3gT1MsxNKZ8j" alt=""><figcaption></figcaption></figure>

***

### Setting Up a Goal Tracker

Select the "Track an event completion" option to proceed with event-based tracking, it allows you to measure the success of your experience based on specific user actions.&#x20;

<figure><img src="/files/BScKCsjCvaBm4LwkWMIq" alt=""><figcaption></figcaption></figure>

When selecting **Track a Goal**:

* **Create an Event on the Fly** → Quickly set up a new event to track.
* **Select an Existing Event** → Pick from events already created in your workspace.

{% hint style="info" %}
For more details on creating and managing events, see the [**Success Tracker**](/docs/analyze/success-tracker/overview.md) section.
{% endhint %}

***

### Goal Analytics View

This structured view helps you **measure the real impact** of your experience and refine engagement strategies by enriching your analytics with goal related data.&#x20;

You can easily monitor users **who reached a specific goal thanks to your experience** compared to the ones who reached that goal by themselves. This structured view helps you track the effectiveness of your experience in **guiding users to achieve set goals**, enabling data-driven decisions to enhance user engagement and success.

<figure><img src="/files/bEcrAWU4QlnVjtXhtMLq" alt=""><figcaption></figcaption></figure>

Once a goal is defined, the [Analytics dashboard](/docs/analyze/analytics.md) will include additional insights:

* **Reached Goal Summary (A)**\
  Shows the number and percentage of users who achieved the goal.\
  Clicking expands into detailed analytics.
* **Detailed Visualization (B)**\
  Displays a comparative graph of:
  * Goals reached **after interacting with the experience**, versus
  * Goals reached **independently**.

Clicking data points opens a breakdown of user interactions for that date.

***

## A/B Testing (Tours only)

For **Tours**, the Goal section includes an additional block dedicated to **A/B Testing**.

<figure><img src="/files/Kb7PD1Ze89RsNjYh9BOk" alt=""><figcaption></figcaption></figure>

A/B Testing allows you to:

* Create multiple variants of a tour (Original, Variant A, Variant B).
* Randomly split your targeted audience across variants.
* Analyze which version performs best on your chosen goal.

👉 See the [full A/B Test guide](/docs/analyze/a-b-test.md) for a complete walkthrough of test configuration, analytics, and best practices.

***

### Starting a Test

1. Go to your Tour → **Target & Publish → Goal**.
2. Click **Start A/B Test**.
   * Jimo creates the **Original variant** + **Variant A** (duplicate of the original).
3. Add another variant (max 3 total) if needed.
   * You can duplicate either the Original or Variant A as a base.
4. Adjust **audience distribution** using the slider.
   * Users are randomly dispatched **from the audience defined in the “Who” targeting rule**.
   * Each variant must get at least **10%** of traffic, none can exceed **90%**.

<figure><img src="/files/Qs3DAqRb16BNrR5VNHg0" alt=""><figcaption></figcaption></figure>

***

### Publishing & Managing

* **Cancel Test**: Available until you publish (removes variants & edits).
* **Publish**: Activates the test—users will be randomly assigned to variants.
* Variants can be previewed or edited directly from the Goal section.

Once published, results will appear under the **Analytics > Insights** tab for that Tour.

* You’ll see variant performance, a confidence tracker, and the option to **set a winning variant as default**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.usejimo.com/docs/publish/mesure-outcomes-goal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.