Tracking ID

This is for:

Business Analyst System Administrator

A tracking ID is a unique identifier used to differentiate and categorize Coveo Usage Analytics (Coveo UA) data between distinct sections or properties within a client’s organization. Similar to the organization ID which identifies the organization itself, the tracking ID points to specific parts within the organization, effectively creating a way to divide and manage events as needed.

In a user journey, all events should be tied together for consistency and for accurate data analytics. The tracking ID is therefore the common thread that ties all user actions together, facilitating the process of analyzing the data including user behavior and preferences.

Note

A single user journey can’t span multiple tracking IDs, and UA data is segregated by tracking ID. Therefore when you analyze metrics like page views, clicks, or conversions, the UA reports will show them separately for each tracking ID.

The tracking ID is versatile and can be leveraged according to your own specific requirements. It can be adapted to different setups, including but not limited to variations in languages, regions, and business strategies.

Important

  • The tracking ID shouldn’t be confused with other factors such as the site’s domain, locale, or catalog ID.

  • A single user journey or experience in a website or app needs to maintain the same tracking ID.

Single vs. multiple tracking IDs

One tracking ID can span across various locales and/or top-level domains, while multiple tracking IDs can be used for a single top-level domain.

Examples

  • Your website includes translated pages where each one contains the same core content. Each page is assigned the same tracking ID since the context remains the same regardless of language.

  • You have separate web properties that cater to North American and Asian audiences. Each property is therefore assigned its own tracking ID since the content differs from one property to another.

When deciding between using single or multiple tracking IDs, you must consider the following:

  • An eCommerce ordering and checkout process can’t span more than one tracking ID, because it represents a single journey.

  • A service episode can’t span more than one tracking ID, because it represents a single journey even though it may cross different top-level domains.

Tip
Leading practice

We recommend using different tracking IDs in the following scenarios:

  • Your web properties have different branding, different domains, and no cross-navigation.

  • Your web properties have the same top-level domain, but their individual audience, indexed content, and visitor behavior, are quite different, meaning there’s no cross-navigation in a single journey.

  • You want to explicitly separate reporting between properties.

    For example, the following sites https://www.barca.com/nl-nl and https://www.barca.com/fr-fr could have two different tracking IDs and treated as separate sites with segregated reporting. Alternatively, they could be considered as a single site, using the same tracking ID for unified reporting. This choice is dependent on the desired setup and the similarity in underlying content.