Highlighted

Launch tealium Profile B from within tealium profile A

Silver Contributor
Silver Contributor

I'm trying to separate my analytics and other 3rd party tagging and data layer - and so am thinking the best way will be to have my site load my analytics profile (A), and then within that profile, i'll either add a custom container or set it within an after load rules extension to include profile B to fire various 3rd party calls and such.

 

How can I do that? and any thoughts like "Don't do that!  that's crazy!!" ?.... etc...?

3 REPLIES 3
Highlighted

Launch tealium Profile B from within tealium profile A

Employee Emeritus

 

It sounds like you are looking for a profile library. You can read about them here https://community.tealiumiq.com/t5/iQ-Tag-Management/Managing-Profile-Libraries/ta-p/13622.

 

Launch tealium Profile B from within tealium profile A

Silver Contributor
Silver Contributor

Hi @steve_thurner, I'm familiar with profile libaries, but my issue with using them is that in the actual published profile the flags that identify when tags actually get loaded and fire can't be set for a single tag (sepcifically the flag for preventing tag fire until dom.complete). So i was hoping to have my analytics profile launch on the page as normal with no delay flag, then have it in turn call the 3rd party tag profile which would have the flag set for dom.complete.  

 

.. Perhaps there isn't much value in doing this?  I'm hoping for performance benefits - but am not sure there will be some.  Any ideas?

 

Highlighted

Launch tealium Profile B from within tealium profile A

Employee Emeritus

@Michael_Kim_shc All the tags in a given profile will not run till DOM Ready. There is a Wait flag for each tag that controls if the tag waits for DOM Ready. You can set this to No for your analytics tag and leave it Yes for the others.

Screen Shot 2017-08-02 at 9.17.19 AM.png

If you wait till DOM complete you will increase the chance that a user will navigate away from the page before the tags fire. From a performance perspective I would suggest looking at precieved load time which is when the user gains control to navigate the page (DOM Ready) rather than document complete.

 

You can't load multiple utag.js files on the same page our library checks for that and will not execute the second time. There is a configuration to halt all tags till document complete https://community.tealiumiq.com/t5/JavaScript-utag-js/Config-Overrides-for-utag-js/ta-p/14048 but you can't set that per tag.

 

If you absolutely want to delay the other tags till document complete I would suggest setting a load rule to look for a value in the data layer like doc_complete = true. Set all the tags that you want to wait to that load rule. Then you can fire a utag.view command passing in the datalayer at dom complete with the added variable doc_complete=true. I would suggest adding an extension scoped to the analytics tag to return false when doc_complete=true so it doesn't run twice. While this might serve your purpose, this wouldn't be a recommended practice and might cause unintended issues.