Double Tealium Tag, iframe and container

[andrea_manfredi]

Hi All, we are facing a strange behaviour and we would like to know how it works. The scenario is that we have page ( container ) in which we have the sync and the async scripts and an iframe in which we have inserted the sync and the async scripts again. Our purpose isn't to stop the iframe view via the "utag config override no view" but to have 2 views or 1 views per time for some cases. What we are seeing is that the utag.js and the utag.sync.js are loaded twice ( one for the container and one for the iframe) but seems that the other utag.x.js are loaded only from the container scripts and not also from the iframe script. Further we noticed that this behaviour doesn't happen if the iframe is called throught https (since tealium tags inherit the parent protocol ). Since that the utag.x.js in the iframe is not called the extensions related to the iframe aren't executed. Somebody know something about this? Thanks

[samrat_dsouza]

Don't know about the issue, however, you could skip including the utag.js files in the iframe and just use parent.utag.view({variables}) or parent.utag.link({variables}) to pass utag variables and fire tags. else it's two different utag accounts. Cheers Sam

[andrea_manfredi]

Thanks for the quick response. Your approach can work only having access to the iframe source code, and this is not our case sadly.

[adrian_browning]

Andrea, If you load the iFrame in a new tab, and look at the debug / tracking. Do you see what you expect with tags loading, and the extensions running through? Adrian

[andrea_manfredi]

Yes, indeed we developed all the custom code looking the iframe in a separate tab ( it was more handy ). When we came back to the page that contains the iframe to test the whole behaviour we noticed the matter.

[adrian_browning]

Andrea, Do you have an example page? Could you please list it on here or send it over to support-emea@tealium.com, and I will take a look at the page. Thanks, Adrian