Cross-Domain Device Tracking allows you maintain a consistent device identifier as a user browses multiple domains that you own. This feature is helpful if you would like to draw insights from user behavior across all your owned domains, but have not been able to capture any persistent identifiers on that user yet, such as an email address.
To activate Cross-Domain Tracking, you will need the following to be set up and implemented for each domain:
- The Sync Injector
- A MetaRouter Cluster
To demonstrate how Cross-Domain Tracking works, we'll use a fictional organization, CompletelyOutdoors.com. This organization has recently purchased three brands to bolster its portfolio of outdoors companies that own the following domains:
Our example user has never interacted with any of these brands before. When they decide to visit EverythingFlyFishing.com, the Sync Injector calls to MetaRouter cluster endpoints to determine if the user has been seen before across any of CompletelyOutdoors' domains. No identifier is found, so it sets a Cross-Domain ID value of
Two weeks later, the user visits PowderSkiing.com. When the Sync Injector loads and does not detect an existing Cross-Domain ID within PowderSkiing.com's first-party cookie space, it calls the available cluster endpoints. This allows it to access cookies stored by EverythingFlyFishing and PowderSkiing.com. Since a Cross-Domain ID value was created and stored within the EverythingFlyFishing.com cookie, the value
123abc is pulled and set as the Cross-Domain ID value on PowerSkiing.com.
A few days later, the same user navigates to CompletelyOutdoors.com. Now, the Sync Injector moves through the same process and sees that Cross-Domain ID value has been set on both EverythingFlyFishing.com and PowderSkiing.com. It sets the
123abc value on CompletelyOutdoors.com as well.
CompletelyOutdoors.com can now analyze their user data within a persistent data storage destination (e.g. a CDP or data warehouse) and join the user data across domains based on the persistent Cross-Domain ID value that has been set. They would see that the user has an affinity for fly fishing and skiing, and can now serve relevant experiences to that user.
Configuring Cross-Domain Tracking requires a few simple steps:
- Reach out to your MetaRouter Customer Success Manager to confirm that Cross-Domain Tracking has been activated on your data processing cluster(s).
- Note the Ingestion Website URLs for each of the domains you'd like to sync a Cross-Domain ID between. These can be found within the File Builder of each domain's production pipeline.
- Navigate to a pipeline for which you'd like to activate Cross-Domain Tracking. Open the File Builder.
- Scroll down to the Cross-Domain Identity Sync section. Add the Ingestion Website URLs you gathered in Step 1, with
/v1/cross_domain/idappended to the end. This may look something like
https://a.completelyoutdoors.com/v1/cross_domain/id. Ensure the URLs are comma-separated.
- Save and build your file, and install the new file.
- Repeat this process for each domain you'd like to sync a Cross-Domain ID between. That's it!
To use the Cross-Domain IDs that MetaRouter generates, you must first map the Cross-Domain ID input value to your destination. The input value will typically be
context.providers.crossDomain.id but be sure to validate that this is the correct input generated by your Analytics.js file. Within your integration, add this input with a Mapping transformation, Direct Assign type, and the correct Output key for your integration. This will vary per integration.
Once you begin to see your Cross-Domain ID populating within your destination, you will be able to apply any logic you'd like within that destination to take advantage of your Cross-Domain ID.
How long is the Cross-Domain ID cookie value stored in the browser?
The Cross Domain ID will live for up to 365 days in Chrome. It may live within other browsers for a shorter duration, depending on browser restrictions.
Does Cross-Domain Tracking work on Safari or Firefox?
Cross-Domain Tracking may not work on Safari or Firefox due to State Partitioning.
What happens if a Cross-Domain ID conflict occurs?
MetaRouter will perform "re-check" sync to ensure Cross-Domain IDs remain consistent across domains. This will occur every seven days.
It is possible that a user might have separate Cross-Domain IDs set for different domains. One reason this might happen is if a sync to one domain times out. If this occurs, then a new Cross-Domain ID could be set despite one already existing. In any scenario where a user’s Cross-Domain ID is different among domains, we’ll use most common ID set by the configured domains. If there is a tie in the sum of IDs, then we’ll use the order of the domains within the UI configuration and pull the first ID in that list.
Are calls to each Ingestion Website URL asynchronous?
Yes, the Sync Injector calls all the domain URLs at the same time. If a Cross-Domain ID is not resolved within the timeout period, it is ignored.
Updated 3 months ago