# Setup

### Start a Journey

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F6zhm62t1kLRA9hUl4QPe%2Fimage.png?alt=media&#x26;token=105a9f33-3f6d-4cfb-9dbf-9a3a78a1c635" alt=""><figcaption></figcaption></figure>

#### Access the Journey Section

Navigate to the main menu and click **Journey**. This opens the Journey listing page, where you can:

* View existing journeys
* Access journey details
* Stop or manage active journeys

#### Create a New Journey

Click **Create New Journey** to begin. This action opens the journey creation wizard, which guides you through the setup process step by step.

{% @arcade/embed flowId="Dm7hXaPN7KTXaVrhXO4s" url="<https://app.arcade.software/share/Dm7hXaPN7KTXaVrhXO4s>" %}

### Enter Journey Information

#### Journey Name (Required)

Enter a clear and descriptive name for the journey (for example, *Customer Retention Campaign*).

* This field is mandatory
* You cannot proceed without entering a name
* If left empty, a warning message appears below the input field

#### Journey Description (Optional)

Add a description to provide context about the journey’s purpose.

**Example:**\
\&#xNAN;*A campaign designed to increase retention of new users through personalized offers based on browsing behavior and purchase history.*

Descriptions help teams quickly understand the intent and scope of the journey.

### What Is a Conversion?

A **conversion** represents the successful completion of a predefined user action that delivers business value.

A **conversion event** is the specific action used to determine when a **user** has successfully completed the journey’s objective. This event is defined by the business or marketing team and serves as the primary success indicator for the journey.

{% hint style="info" %}

### Conversion Tracking Logic

Conversion tracking is **user-based**, not event-based. A user can be counted as converted only once per journey, regardless of how many times the conversion event is triggered.
{% endhint %}

#### Common Conversion Event Examples

* Making a purchase
* Applying for a credit card
* Updating profile information

Conversions are key metrics for evaluating journey performance and overall campaign effectiveness.

### Select Conversion Event

Select the event that represents success for the journey.

* Use the dropdown menu to choose a conversion event
* The selected event determines how journey performance is measured **at the user level**

**Example:**\
Selecting **Purchase** means the journey is considered successful when a **user** completes a transaction. If the same user completes multiple purchases, the journey still records **one conversion for that user**.

* A conversion event must be defined **before** the journey is started
* Once the journey is live, the conversion event **cannot be added or modified**

<div data-with-frame="true"><figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FTto7BzmdfiUBakNfbOdP%2Fimage.png?alt=media&#x26;token=8a17de2b-3eac-475c-8e8a-cdcbdb124e33" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}

### Event Availability

To be selectable here, the conversion event must already be created under **Developers > Events**.

If the event does not exist, it will not appear in the dropdown. Refer to the Events documentation for instructions on creating new events.
{% endhint %}

### Select Conversion Event Property

Enable **Select Conversion Event Property** to apply additional conditions to the selected conversion event based on event properties.

This option helps narrow down which occurrences of the selected event should be considered valid conversions. Multiple conditions can be added and are evaluated using **AND** logic. As a result, only event occurrences that match all defined property conditions are counted.

Using event property conditions can improve measurement accuracy by excluding irrelevant or incomplete event occurrences.

**Example Configuration:**

Selected conversion event: **UpdateProfile**

Property conditions:

* **itemName** → **Exists**
* **itemNextData** → **Exists**
* **itemCurrentData** → **Exists**

A conversion is counted only when the **UpdateProfile** event includes all three properties.

<div data-with-frame="true"><figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FeBus5ZCSRHyqLDPazedE%2Fimage.png?alt=media&#x26;token=befcbbae-5f27-4858-b096-8014d02c77ad" alt=""><figcaption></figcaption></figure></div>

### Stop Counting Conversion After User Exits

After selecting a conversion event, define how long a **user** can be counted as converted **after exiting the journey**.

This setting defines a **post-exit time window** during which conversion events can still convert the user.

#### Configuration

* Duration can be set in **minutes, hours, or days**
* No duration is selected by default
* Selecting a duration is mandatory

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FKsvfvbrjtA7GOq6mdmKx%2Fimage.png?alt=media&#x26;token=cab8db1d-4f3f-407e-b06a-5d5297693cee" alt=""><figcaption></figcaption></figure>

| Scenario                                                                    | Is the Conversion Counted?      | Explanation                                                                                                                           |
| --------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Conversion triggered within the post-exit time window                       | ✅ Yes                           | If the user triggers the conversion event within the configured duration after exiting the journey, the user is counted as converted. |
| Conversion triggered outside the post-exit time window                      | ❌ No                            | Conversions occurring after the configured duration expires are not attributed to the journey.                                        |
| Multiple conversion events triggered within the same journey entry          | ✅ Yes (counted once)            | Conversion counting is user-based. Multiple event triggers by the same user result in only one conversion.                            |
| Conversion triggered after re-entry, when the user has not converted before | ✅ Yes                           | If the user has not been counted as converted previously, the conversion is counted after re-entry.                                   |
| Conversion triggered after re-entry, when the user has already converted    | ❌ No (no additional conversion) | A user can be counted as converted only once per journey. Re-entry does not create an additional conversion or reduce the user count. |

### Conversion Attribution Rules

* If a user triggers the conversion event **within** the configured duration after exit, the user is **counted as converted**
* If the event is triggered **after** the duration expires, the user is **not counted**
* Conversion tracking is **user-based**

This means:

* A user may trigger the conversion event multiple times
* **Only one conversion per user** is recorded for the journey
* Additional event triggers do not increase the conversion count