Below, you will find an example of how ID5 creates the encrypted and publisher-specific TrueLink IDs for users across publisher media properties. Please take a look at the step-by-step commentary to learn more.
Your Encrypted TrueLink ID:
not set yet
Your Publisher TrueLink ID:
not set yet
Your Encrypted ID5 ID:
not set yet
Step 1
When the user visits the page with a TrueLink integration, for instance, Domain A, for the first time, they will see a privacy pop-up. ID5 will not generate the TrueLink ID or the ID5 ID unless the user provides their consent (in the applicable jurisdictions).
The TrueLink IDs will be undefined in the box above on your first visit.
Step 2
On a repeat visit, the consented user will be redirected to the ID5 domain, where the TrueLink ID will be set as a first-party cookie. The user will be immediately returned to the original page with the TrueLink ID, and the ID5 ID will be generated for them once they are back to Domain A.
Refresh this page to see this process live! The redirection occurs swiftly, typically within milliseconds, and is invisible to the user's eye. The box above will display the encrypted TrueLink ID, the publisher-specific TrueLink ID and the ID5 IDs that were created for you in the process.
Step 3
When the same user visits other webpages across your media properties, ID5 will recognize them and return the same TrueLink ID to the page.
Visit our other demo page, Domain B, to see it in action.