Journey Report
Luiza Gircoveanu avatar
Written by Luiza Gircoveanu
Updated over a week ago


The report for a Journey shows all the activity that took place on each step during the Journey run. Each step is represented on the screen by a small thumbnail that reveals a larger screenshot when selected.


Each step of the Journey is captured in a screenshot that takes place after the action is executed (including wait time). To see the screenshot full size, click the screenshot again. This is helpful for troubleshooting a Journey; if the Journey fails, view the steps preceding the step where the failure was recorded to see if all the data was entered, or each option selected as expected. For example, if a login fails, check the screenshots of the steps where the username and password were entered to verify they actually were entered correctly.

Note: You can use the arrows on your keyboard to quickly navigate to the next step in the Journey.

Tag Presence Tab

The list of all tags found or initiated on the step are listed here with a comparison of tags present on the current run and previous run. If a tag has multiple accounts, rows will be added for each unique account.

In the top right corner, there is a toggle labeled "Only Show Changes". Once enabled, the tag presence report will exclude any tags where no differences were found.

Additionally, you can see Primary Tags Only if you switch on the button:


Variable Summary Tab

The list of all tags found or initiated on the step are listed here with each of the variables and associated values that were collected. It also displays tag load time, status codes, and comparison results.

Note: To configure tags for comparison and add match criteria, you'll need to edit a tag in your account settings (admins only).

We have written a short guide with examples on how to setup Match Criteria in your Account Settings.

Tag Load Time

The tag load time helps indicates the weight of a tag. While some tags are asynchronous and don't directly impact the user experience, this number gives us a pulse on how large some technologies are.

Tag Status Code

Status codes can help with troubleshooting issues with data collection on specific actions.

Comparison Results

This column will show "No Changes" or the number of changes that were found between the most recent run and the previous run.

Note: You can hover over the work "No Changes" or the "# Changes" to see how the Match Criteria distinguished which tags are which.

If the Journey has only run one time or if no tags were enabled and assigned Match Criteria, you will see a message prompting you to complete the comparison setup.

Note: If you are not seeing comparison data for a specific technology, you need to enable that technology for comparison and set up match criteria

To see the details including latest run and previous run values and which values changed, click the tag you want to inspect.

Once expanded, the table shows the variable name, the associated value on both runs being compared, and the results of that comparison.

Note: An em-dash β€œβ€”β€ indicates that there was nothing to compare for that variable and its associated value.

Click the Add Rule button to create and apply a rule on the fly.

Clicking this adds a rule based on the values found. See Creating Action Rules in Journey Reports for instructions

Cookies tab

The Cookies tab shows the cookies found during the Journey and some details about them such as Name, Domain, 1st/3rd Party, Total Initiators.

Rules Tab

The Rules tab displays the results of the action rules and show whether they Passed, Failed, or were Not Applied to each individual step in a Journey. They can offer valuable insight about where your Journey is functioning as intended and where they may need some work. Click each rule that fails to see what the rule was looking for and what caused the failure on that step. Clicking the Set As Expected button updated the expected value of the rule to be the actual value reported.

See Journey Rules Reporting in Help for an explanation of this tab.

Note: You can use the edit and remove icons to update rules or remove them from the action without leaving the Journey report.

Action Details Tab

Actions, network request logs, and console log data associated with each action can be inspected, sorted, and filtered. Depending on the action used, it will show one of the following:


The URL that the step should navigate to. This is always the first step of any Journey.


The ID of the HTML element to be clicked.


This shows two fields: the ID of the HTML element and the value to be typed into the text element.

Masked input

This is the same as the Input action, except the value is encrypted and shows as masked for security.


The element's ID and the value of the select list's option that should be chosen.


The ID of the checkbox or radio button that is to be checked.


The ID of the checkbox or radio button that is to be unchecked.


The code of a JavaScript snippet or jQuery string. If the code has more than one line, each line of code is delimited by a semicolon.


The number of seconds the Journey should pause (The total amount of time available to be used during a month is based on contract.)

Generated Actions

Generated actions are secondary results that take place during a step, such as a page redirection.

Note: Whenever an ID is used in an action, a name attribute could also be used, but name attributes are not as reliable because there can be more than one element on a page with the same name.

In the Console Log section, icons can be selected or de-selected to filter out log information by category.

Journey Rules Reporting

Journey rules are different from action rules because they look at the Journey as a whole and identify if a rule executes successfully one time. This allows you to identify if a tag or condition is in fact correctly implemented throughout the entire user path or is missing something in portions of the user Journey. See Journey Rules Reporting in Help for a full explanation.

Journey Exports

This Journey Exports Tab on the left gives you the option to export all components of a Journey in Excel files so that you can analyze them and have them listed all in one place. You can either preview them or download the files directly.

Script Services

If a Journey contains an action failure, the Have Journey Support Fix The Issue is button is available. Selecting this requests the professional services of the ObservePoint Script Services team.

If your Journey has an action failure this option is available.

After selecting Have Journey Support Fix The Issue, a modal appears and displays the number of Journey fixes your account has remaining.

Confirm whether you want to request Script Services to fix your journey.

Did this answer your question?