Add an exit rate goal

You can add an exit rate goal to an experience to help assess and improve visitor interactions on a website. It enables you to track how many visitors leave your site from a specific page, after navigating through other pages.

Sitecore Personalize calculates the exit rate using the VIEW event. It counts a VIEW event as an exit if the visitor views one or more web pages then exits on the page that runs the experience. We recommend setting up this goal to monitor the visitor journey up to the point they exit on the page hosting the experience.

For example, you can create an experience in Sitecore Personalize and add an exit rate goal to track the rate at which visitors exit a specific page. Additionally, you can specify a goal target, quantifying the exit rate percentage you are hoping to achieve with the experience.

Warning

The Personalize API is what developers use to run interactive experiences. If you add an exit rate goal to an interactive experience, ensure that your organization uses the browserId attribute when calling the Personalize API. This ensures that the goal is attributed to the correct browser session and the attribution rate is accurate when viewing performance analytics.

To add an exit rate goal:

In the experience builder, click the Goals tile and click Add Goals.
In the Goals pane, click Exit rate.
In the Exit rate pane, in the Goal name field, enter a descriptive name for the goal. This name will display on the Performance screen.
In the Goal target field, enter the exit rate percentage you want to achieve. For example, if you set a target of 10%, this means the experience will meet the goal when 1 out of every 10 visitors exit your site from the tracked page, after exploring other pages on the website.

Note

Adding a Goal target does not affect any calculations. This value will be displayed as a baseline metric on the Performance screen, designed to help you compare the actual exit rate against your targeted goal.
In the Track pages section, select one of the following operators to track the page:
- Equals - matches the page name you enter in the text field exactly with the page parameter from the VIEW event.
  
  Example: If you entered home in the adjacent text field, this option will only track the page with a parameter that exactly matches this string.
- Regex - matches the page parameter from the VIEW event using a Regular Expression (RegEx) pattern. The RegEx should result in a full match of the page name, not a partial match.
  
  Example: If your page parameter is home, using the RegEx pattern [a-zA-Z] will not match the full string home but only one of its letters, like h. However, if you used the pattern [a-zA-Z]+, it will match the entire string and be able to track that page.
- Starts with - matches the beginning of the page parameter from the VIEW event with a specific string.
  
  Example: If you entered home in the adjacent text field, this option will track any page with a parameter that begins with home such as home or homepage.
In the adjacent text field, enter the full or partial name, or RegEx pattern of the page you want to track. This must be the same page on which the experience is configured to run and corresponds to the page parameter from the VIEW event.

Warning

You must enter the exact page parameter in the text field. The page parameter you enter in the text field depends on how the webpage was tagged when it was integrated with Sitecore Personalize. If you do not know it, ask a member of your technical team.
Optionally, to add additional page parameters, click Add and provide the details to track the page.
Optionally, to add more details about the goal, click Description.
Sitecore Personalize automatically creates a Friendly ID as you enter a Goal name. You can use this ID to refer to the goal when integrating.

To edit the ID, click and enter the new ID for the goal.

Note

When editing, use a-z, 0-9, and underscores for spaces.
Click Save. The goal is added to the Goals tile.

Exit rate goal snapshot

What it tracks - users who leave the site after viewing a specific page.
Conversion - occurs when the user views one or more pages and then exits from the designated target page before the session ends.
Attribution - identifies and credits the experience that influenced the user's decision to either stay or leave.
First-touch example - if a user views a personalized homepage and exits from the checkout page, the hompage is credited for contributing to the exit (goal conversion), and influencing the user's journey, even if the purchase wasn’t completed.

Next steps

Start the experience for personalization to take effect.
View the analytics. After starting the experience, you can immediately see operational data. Within 24 hours, you’ll see the goal target as a baseline on the Performance screen. This lets you easily identify whether the experience has reached its target.

Do you have some feedback for us?

If you have suggestions for improving this article,