I have IQ and Audience Stream (AS), and am trying to maximize the usage of the Google Analytics Premium Rollup properties, where multiple properties are combined and dedupe based on a given user ID.
I have an ID that I'm identifying within AS that i'd like to use to populate to google as the user ID, but is that possible to do in the realtime tag firing with an enhanced attribute?
Or would it be possible/better to use a matching table through the lookup extension and send the resulting translated value to Google?
@Michael_Kim_shc My question to you is, if that data is already being fed to AudienceStream via Tealium iQ, then why is AS needed for this when you can send the data on the standard page request?
I would guess that data is coming into the system from an external source like Omnichannel? If so, it is possible to trigger an action to Google based on Audience data. You can trigger an action based on that visitor data source being captured. I would setup something like this:
Attibute Type - Attribute Description
Trait - stores visitor data source
Trait - stored Google Cookie ID
Audience - when both Traits are not empty
Action - when the visitor joins the Audience
This is high level, and I'm taking a few assumptions based on the question so I'm hoping this points you in the right direction. Feel free to post another clarifying question here and we will handle accordingly. This may be a better question for your Digitial Strategist who is more familiar with you deployment.
Hi @dan_george, thanks for your response. I think i'm gonna adjust the question..
Say I have 2 different kinds of IDs. ID-A and ID-B. ID-A is firing on the site and getting picked up by IQ. However I want ID-B to be sent in the Google Tag. I have a lookup/reference table I can load to the IQ Lookup extension that maps ID-A to ID-B. But there is a security constraint that restricts me from passing ID-B in any public server call from our site.
Is it possible to get ID-A translated to ID-B and sent to Google for the relevant pageloads?
Another facet is that ideally in Google, I'd be ablet to send ID-B in every server call thereafter for cross-browser/device tracking. Is that also possible?
Last bit - if the security constraint of not being able to use ID-B on the site is the big kicker, then would it be possible to use a master ID from tealium to pass through? (a master ID that is persistent and has all events from it's base tealium IQ IDs?)
06-16-2016 10:48 AM - edited 06-16-2016 10:48 AM
Thanks for the additional info.
So there is not a Tealium master ID that can be used. We have a utag_main_v_id cookie that we set that is device based, and a third party cookie on the .tealiumiq.com domain, but it's also device based. These do not persist with a visitor as they switch devices.
Any ID defined in AudienceStream is based off of your - the client - secondary identifier(s) a.k.a. visitor id attribute. Meaning we leave it up the client to manage their customer identifiers and we key off of any ID(s) that you have (customer id, customer email, facebook id, etc).
I would not recommend using a Lookup Table to try to output the ID-B becase the user base would be far more than JS can handle and would be a huge hit to performance. I get where you are going though with trying to use the single ID, but this should be handled with a different type of lookup.
You should find out if you can even pass ID-B, and then if so then we can discuss how this can be done. Does that sound like a plan?
07-05-2016 12:43 PM - last edited on 07-05-2016 01:12 PM by kathleen_jo
I've gotten some more feedback from others, and in my head it still seems like it's possible (and probably best as far as i can see) to use the Tealium ID a the primary ID to tie everything together in the roll-up properties.
My reasoning is that to my understanding, if device A and Device B both start out with separate tIDs, then after a user authentication on both devices, both devices tIDs will be overwritten to be the value of the later created tID.
Additionally, if 3rd party cookies are enabled, then the in addition to the scenario above:
I have browsed Domain A and Domain B on both Device A and B, and 3rd party cookies are enabled on Device A.
Based on this, i'd have 3 tIDs (1 for Device A beacuse of 3rd party cookie, and 1 for each domain on Device B where 3rd party is blocked).
I then Authenticate by email on Domain A of Device A --> then I still have 3 IDs, one of which is tied to an Email.
then I authenticate on Domain A of Device B --> then I have 2 IDs, as the next time i browse on Device A, the ID from Device B overwrites the stuff on Device A, both Domains.
Then i authenticate on Domain B of Device B --> then i have 1 ID, for the same reason as the previous action.
I don't see how this isn't the ideal ID to use for cross-domain /cross-device user stiching since it incorporates 3rd party cookie sharing when avaialble, but also 1st party cookie authentication?
The only concerns i have at the moment is if i'm misunderstanding something, and then also householding (i.e. a single visitor having multiple Emails that get authenticated on the same device. And matching corruption as well to some degree.
Please let me know if I'm grossly misunderstanding something.. Thx!
07-05-2016 04:43 PM - edited 07-05-2016 04:44 PM
@Michael_Kim_shc just letting you know that I got this. Please give me some time to fully digest your comments so that I can respond accordingly. I may need to diagram this because we are getting this question often so I may answer this with a separate article :)