# Using Journey Tracker

**Journey Tracker** aids system users or visitors by providing an easy visualization of the steps they have completed. Users can get easily puzzled and frustrated when they do not know how far away the end of the task is, so the Journey Tracker provides encouragement as users can see their progress during a dynamic process.

The Journey Tracker indicates progress along a user’s application journey, and encourages them to continue by providing a visual indication of the progress made and the number of tasks yet to be completed. This feature itself improves user engagement, reduces anxiety, and increases your application’s conversion rate.

## Enabling Journey Tracker

1. Sign in to the Management Console with your credentials
2. Click on the name of the Space you want to work on&#x20;
3. Click **Guides** from the menu pane on the left
4. Click **Open in Editor** for the guide where you want to turn the Journey Tracker on

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

&#x20;5\. Open **Guide Settings**

<figure><img src="/files/7sep0THPDz6q6e5AYYxR" alt=""><figcaption></figcaption></figure>

6. Click on the **Track** tab&#x20;
7. Select the box next to **Track** to turn on the Journey Tracker

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

### Displaying the Journey Tracker as a Separate Widget Beside the Adopt Context Help

Once you have turned on the Journey Tracker in the Guide Settings, you can **Save** at this point. However, if you save your settings and don’t select the **Embed in Context Help** box, the Journey Tracker will be visible to the users as a separate widget beside the Context Help, and will disappear when the Journey is completed.

### Embeding Journey Tracker into Context Help

If you would like the Journey Tracker to be included in Adopt Context Help instead of a separate widget, select the **Embed in Context Help** box.

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

As the user progresses through the guides, the completion rate inside Context Help will adjust accordingly.

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

***Note:** The default behavior for completed guides in Journey Tracker is that they are marked as complete and disappear from Context Help. However, this can be changed in the Adopt console if you would like to give users the option to restart the completed guides.*

***Note:** Journey Tracker cannot be restarted in the Adopt console; only the default behavior can be changed.*

## Setting up the Journey Tracker

Once you have turned on the Journey Tracker in the Guide Settings and chosen either a separate widget or embedding in Context Help:

1. Provide an appropriate **Title** which will be visible to the end users
2. Choose an appropriate identifier from the **Journey tracker** dropdown\
   The Journey Tracker will tag them all together as a batch if you choose the same identifier for the selected guides. This enables you to create multiple Journey Trackers by defining different identifiers and categorizing them appropriately. For example, some guides will be part of Journey Tracker A, and some guides will be part of Journey Tracker B.
3. Journey sequences can be defined by assigning a number in the **Order in journey** field. The smaller the number, the higher the priority

***Note:** Consider assigning a negative number to increase the priority. For example, -1 would have higher priority than +5. If you have created multiple Journey Trackers, you can sort them in the Adopt Context Help widget by defining a number for Order in the journey. The lower number gets listed higher.*

4. Create rules, such as if you want Journey Tracker visibility to depend on an element on the same page;\
   a. Select the **Include guide in Journey Tracker when the element is present** box\
   b. Click **Reselect** to choose an element

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

This way, the Journey Tracker will only be visible when the chosen element is visible.

***Note**: For further information, refer to Adopt’s **Rule Engine Possibilities** guide to learn how to create rules that will define when, for whom, with which dependencies the guides will be visible.*

5. **Save** your changes

The **Journey Tracker** will then be **visible** to the application users and visitors. The users or visitors can now track their progress via the Journey Tracker.

***Note:** As the Context help is not visible while the Adopt Editor is running, you should turn off the editor to see Context Help in Agent Mode. To do this, click the checkmark icon in the Guide Settings.*

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

## Managing a Journey

As explained above,  you can create multiple Journey Trackers by defining different Journey Tracker identifiers and categorizing them appropriately. As in, you can include some guides that will be part of ”Journey Tracker Example A,” and some guides will be part of ”Journey Tracker Example B. ” To create such Journey Tracker Identifiers:

1. Sign in to the Management Console with your credentials
2. Click on the name of the Space you want to work on&#x20;
3. Click **Journeys** from the menu pane on the left
4. Click the **+ Create Journey** button

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

5. Provide an appropriate **Title** for the new Journey Tracker identifier&#x20;
6. Choose an **Action after journey is complete** from the dropdown. **No action** means that the Journey Tracker will disappear once the journey is complete , or you can choose to **leave the journey tracker visible**&#x20;
7. Choose an **Action after a tour in a journey is complete** from the dropdown. **No action** means that the Journey Tracker will remain visible, or you can choose to **open Context Help**&#x20;
8. Click the **Create** button

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

***Note:** There will be a **Your journey was created** message in the bottom right corner of the screen*

## Deleting a Journey

1. Sign in to the Management Console with your credentials&#x20;
2. Click on the name of the Space you want to work on&#x20;
3. Click **Journeys** from the menu pane on the left&#x20;
4. Click the ![](/files/Li5oGl6N2EEMKZHnsuZC) in the Actions column of the Journey you want to delete

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

5. Confirm the deletion by clicking **Delete**

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

6. If you change your mind, select **Cancel** to stop the deletion

***Note:** You will see a message confirming the deletion on the bottom right corner of the screen*


---

# 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://docs-adopt.nexthink.com/in-application-guidance/using-journeys-and-rules/using-journey-tracker.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.
