Add a page view goal to an experience in Sitecore Personalize

You can add a page view goal to an experience to measure the views of a particular page, guiding strategies to improve content design. Sitecore Personalize calculates this using the VIEW event that is configured to be sent to the platform when a visitor views a page.

For example, you can create an experience in Sitecore Personalize and add a page view goal to track the views of a specific page. Additionally, you can specify a goal target, quantifying the page views you are hoping to achieve with the experience.

Warning

The Personalize API is what developers use to run interactive experiences. If you add a page view 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 a page view goal:

In the experience builder, click the Goals tile and click Add Goals.
In the Goals pane, click Page views.
In the Page views 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 page view percentage you want to achieve. For example, if you set a target of 50%, this means the experience will meet the goal when the tracked page is viewed 5 out of 10 times.

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 page views 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.

Page view goal snapshot

What it tracks - users who visit a specific page, such as a product page, that is being tracked.
Conversion - occurs when the user successfully views the target page.
Attribution - identifies and credits the experience that influenced the user to visit the target page.
First-touch example - if a user first interacts with a personalized homepage, and then navigates to the product page (the goal), the homepage experience is credited for driving the conversion.

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,