Atlas Universal Tag implementation

[lukas_teply]

Hi, do you have any experience with implementing new Atlas Universal tags in Tealium. The new Atlas Universal tag looks like ? We tried to implement it by adding Atlas tag, iframe format, mapped data sources: "account" and base URL (//ad.atdmt.com/m/img). Then we set 2 extensions - one is for "set base URL" and second one is a look up table where we define URLs and as output we use "account". Any help would be appreciated. Thanks.

[meng_lim]

Hi Lukas, Based on the tag you've provided, you can use the Tealium Pixel Container. 1. Add this tag from the Tealium Tag Marketplace; search for "tealium pixel container" 2. Configure the tag: Set the URL to https://ad.atdmt.com/m/img;m=@@atlas_account@@;cache=@@random_number@@ 3. Add an Set Data Value extension, scope it to the tag itself, and set the atlas_account UDO variable to type "Text" and your account value. 4. Add another Set Data Value extension, scope it to the tag itself, and set the random_number UDO variable to type "JS Code" and "Math.random()" to set the cache.

[meng_lim]

Yes, in your case, you would then use a Look Up Table extension instead of the Set Data Value extension to set your atlas_account value.

[meng_lim]

Yes, that is correct. If you need to setup an iframe tag, you can use the same steps, but change the type to "Iframe". Hope this helps!

[milos_krissak]

Hi Meng, I am Lukas' colleague. Thank you very much for your help. It works for us. Great! There is just one more issue in fine-tuning the tag firing. I was trying to use a load rule saying: fire only if atlas_account_new is populated (and many similar variations) but it never worked for me. I need to let the tag fire for all pages and it works. Actually I used the custom javascript extension as a killer: if(typeof b.atlas_account_new=="undefined"||b.atlas_account_new=="none"||b.atlas_account_new==""){return false} this way it works nice, but I wonder, why I need to use special extension and load rule is not working. Do you have any idea about that? Thanks a lot! Milos

[meng_lim]

Hi Milos, What version of utag.js are you currently using right now? Sounds like you may be running on a version below 4.26, and if this is the case, only tags that are loaded on initial page landing will be available to fire. For example, say "atlas_account" is not defined or populated on initial page landing, and you want to fire the Atlas Universal Tag only when there is a value defined, then the tag will never get loaded, hence it will available to fire afterwards unless on a new pageview this value gets defined.

[lukas_teply]

Hi Meng, thank you for your answers. Actually, I would have one more question. If we need to match Atlas Universal Tag on a button click, do you think that a look up table is the best way how to do that? Thanks, Lukas