Tracking snippet

Learn how to enable visitor tracking on your website.

Prerequisites

• Configure the following permissions in PureCloud:
  • Journey > Settings > Edit, or View permissions

Overview

1. Review Before you begin.
2. Copy the snippet.
3. Optionally customize the snippet.
4. Deploy the snippet.
5. Verify that the snippet works.
6. Configure web tracking.

Tip

See a solutions article that includes the tracking snippet: Genesys Predictive Engagement with advanced chat routing

Before you begin

Before you deploy the Genesys Predictive Engagement tracking snippet be sure you understand:

• All about tracking with Genesys Predictive Engagement.
• How to deploy the tracking snippet to be compliant with General Data Protection Regulation (GDPR).
• The effect of ad blockers on Genesys Predictive Engagement.

Ad blockers

Ad blockers are plug-ins or browser extensions that improve page load times and minimize questionable tracking. The majority of ad blockers tested with out-of-the-box settings do not interfere with Genesys Predictive Engagement's tracking capabilities. However, there are a couple considerations if you use uBlock Origin:

• uBlock Origin disables Genesys Predictive Engagement's tracking web beacons; this effectively prevents Genesys Predictive Engagement's tracking capabilities.
• uBlock Origin and uBlock Plus Adblocker block popular tag managers such as Adobe Tag Manager, Google Tag Manager, and more.

Important

If you use a tag manager to manage JavaScript and tracking on your website, consider adding ad blocker detection to your site in order to notify your users with detected ad blockers that they may be missing some important functionality. Also, instead of using tag a manager to deploy the Genesys Predictive Engagement tracking snippet, consider manually placing the tracking snippet directly in the body or header of your website.

Copy the snippet

Genesys Predictive Engagement provides a tracking snippet that you can copy and paste. Since you are logged in to PureCloud, the tracking snippet already contains your organization ID and region.

1. Click Admin.
2. Under Altocloud, click Tracking Snippet.
3. To determine which snippet to use:
   • Read about the types of snippets.
   • Review the snippet recommendations.
4. Click Copy Snippet.
5. For information on where to paste the snippet, read Deploy the snippet.
   

Types of tracking snippets

Website snippet

The Website snippet provides tracking support to traditional webpages that contain little or nodynamic content. Traditional websites load a new HTML page whenever the user navigates to a different URL. To provide tracking support to traditional webpages, the Website snippet calls ac('pageview') each time the a new page is loaded by the web browser.

SPA snippet

The SPA snippet can track activity on Single Page Applications (SPAs). SPAs load dynamic content on demand without requiring a hard reload of the HTML page. The SPA snippet can also track when users click relative links, which the Website snippet does not. The SPA snippet works on SPAs such as Angular, React, Vue.js, and so on. For more information about the additional tracking options available with the SPA snippet, see [[ATC/Current/SDK/autoTrackURLChange|]].

Snippet recommendations

If you have this type of website...	Use this snippet...
Not sure	SPA
Mix of traditional and SPA pages	SPA
Traditional pages only	Website

Customize how the snippet tracks activity (optional)

If needed, you can customize how the snippet tracks activity on your website:

• If you need to refine how Genesys Predictive Engagement tracks activity on your website, see About event tracking with tag managers.
• You can also customize the Genesys Predictive Engagement tracking snippet with functions from the Journey JavaScript SDK. For example:
  • Use the Journey JavaScript SDK to track page view events and to configure how Altocloud updates cookies.
  • Configure advanced tracking to enable tracking across multiple domains.

Deploy the snippet

Important

The Genesys Predictive Engagement tracking snippet loads JavaScript asynchronously without slowing down page loading. For more details about how the tracking snippet works, see About the tracking snippet.

After you copy the snippet, review the deployment notes. Then follow the instructions to deploy the tracking snippet:

• Deploy the snippet with a tag manager.
• Deploy the snippet manually.

Deployment notes

Important

Remove the script tags from the snippet before you deploy it.

• Deploy the Genesys Predictive Engagement tracking snippet on the main window of the website you want to track.
• Paste the tracking snippet in the head section of the website template page before the closing tag.
• Do not deploy the tracking snippet in an iframe.

Deploy the snippet with a tag manager

To easily deploy the Genesys Predictive Engagement tracking snippet, use your preferred tag manager. For example:

• Deploy the tracking snippet with Google Tag Manager
• Use Adobe Launch with Genesys Predictive Engagement
• Any other tag manager

Important

If you use uBlock ad blocking software, do not use a tag management system to deploy the Genesys Predictive Engagement tracking snippet. For more information, see Ad blockers.

Deploy the snippet manually

1. Admin > Altocloud > Tracking Snippet.
2. Next to the type of snippet you need, click Copy snippet.
3. Before you paste the snippet on your website, review the deployment notes.

Verify that the snippet works

When the tracking snippet is properly executed and initialized:

• Use Live Now to verify that Genesys Predictive Engagement is tracking your website activity.
• You should see an update every 4-5 seconds.
  

Troubleshoot the snippet

If the tracking snippet does not work properly when you load it on your web pages, check the following things:

• Is the snippet on the correct page?
• Is the snippet correctly placed in the header?
• Are all of the parameters specified correctly?
• Are there any typos, missing characters, or extra white space?
• Have any characters been replaced by their printable equivalents?
• Is the domain on the list of allowed domains?

For more suggestions, see Deployment notes.

Error reference

Error code	Description
403 error	Is your domain in the list of allowed domains?
404 error	Is there extra white space in the snippet? Note: In a URL, white space is encoded as %20.
Bad request	Is there extra white space in the snippet? Note: In a URL, white space is encoded as %20.
Initialization error	Are there any of the following in the snippet: Typos Missing characters Dashes and quotes in URLs replaced with printable equivalents