Highlighted

Send the UDH Visitor ID back into the Tealium iQ Data Layer

Silver Contributor
Silver Contributor

Since Audience Stream / UDH stitches many Visitor IDs together, we are pondering whether it makes sense to abandon the "old" Visitor IDs for our tracking and simply take the UDH Visitor ID since it is already the "stitched" one. 

How can we access it and is this recommended at all?

3 REPLIES 3

Send the UDH Visitor ID back into the Tealium iQ Data Layer

Silver Contributor
Silver Contributor
Not too many answers at once! :)
Highlighted

Send the UDH Visitor ID back into the Tealium iQ Data Layer

Employee Emeritus

LOL Haven't you had enough answers for one week @loldenburg?!?!?!  ;-P

Remember to give me a kudo if you like my post! Accepting my post as a solution is even better! Also remember that search is your friend.
Highlighted

Send the UDH Visitor ID back into the Tealium iQ Data Layer

Tealium Employee

@loldenburg

 

Beyond the 1st party and 3rd party cookies, and the "secondary ID" keys that are defined by the client, there is no other ID available within AudienceStream to be used as a master visitor ID.

 

Basically, the idea is that we allow businesses to declare multiple Visitor ID attributes and all can be used to reference a single visitor.

 

Cheers,

-Dan