Tealium iQ Tag Management

abrahameaso · ‎01-03-2016

Hi All,

is it mandatory to deploy tealium container code to the web site every time a new data layer variable is added?

while i was working on few sites noticed that, even if the new data layer variables not deployed to the site, they come available on the tealium web companion and in web site.

So i was trying to understand the best practice on this process and any specific reason or issue due to which every time deployment is consided as a practice.

Basically during development and future enhancment stages, do we need to make sure application team deploy the new data layers into the site each time a new variable is added?. I was feeling its a teadious process when we have multiple web sites and faster deployment and testing needed.

Let me know if you need any more details.

Thanks & Regards

Abraham

Thanks & Regards
--------------------------------------------------
Abraham Easo
Principal Consultant
Numeric Analytics, LLC
Bartlett, IL (CST)
m: 980-422-2044
Abraham.Easo@numericanalytics.com | http://www.numericanalytics.com
Adobe Analytics Architect/Tealium Expert/Ensighten/Google Analytics Certified

roshan_gonsalko · ‎01-04-2016

Hi @abrahameaso,

Thanks for your question. No, you don't need to deploy a new container tag on your page each time a new data source is added to the data layer in Tealium iQ. There are many data sources that you will end up creating in Tealium iQ which may never be set in the Universal Data Object (UDO) on the page (i.e. the container tag). because you choose to populate them via Extensions (for example).

You only need to deploy an updated UDO (within the container tag) on your site if you want to set new data sources (which is a rare occurrence and entirely dependent on your business/data needs).

The container tag you see in the Tealium iQ is always updated with the full list of UDO data sources but this is really just to help developers understand how to set the UDO on the page so you can ignore this.

I hope this helps!

Thanks,

Roshan

abrahameaso · ‎01-04-2016

@roshan_gonsalko

Thanks for the quick clarification roshan.

Regarding the coment you have shared

"You only need to deploy an updated UDO (within the container tag) on your site if you want to set new data sources (which is a rare occurrence and entirely dependent on your business/data needs).".

I had a followup question. Sharing here below the details with an example.

For the case of setting a pageName from the application code into the utag_data object (utag_data ={ }). i was thinking to update the utag_data object using approach1 code. This code is executed outside of container code. Also i assume thise should execute before the tealium container code is loaded.

Approach1

--------------

utag_data["pageName"] = "Home Page";

By this way, there is no need to update the container utag_data object after the initial container code deployment.

Let me know if my understanding is correct or in case you need more details on what i am trying to explain.

Thanks

Abraham

Thanks & Regards
--------------------------------------------------
Abraham Easo
Principal Consultant
Numeric Analytics, LLC
Bartlett, IL (CST)
m: 980-422-2044
Abraham.Easo@numericanalytics.com | http://www.numericanalytics.com
Adobe Analytics Architect/Tealium Expert/Ensighten/Google Analytics Certified

roshan_gonsalko · ‎01-05-2016

Hi @abrahameaso,

No problem. That's right - you can keep on updating utag_data further down the page as long as it's done before you call utag.js. The risk of doing this though is that utag.js might be called quite late - we recommend to call it immediately after utag_data is set at the top of the <body> to ensure tags are loaded as quickly as possible. The implications of loading utag.js too late are:

Reduced data collected by tags (due to the user moving page before Tealium has a chance to load all of the tags)

Example impacts of this are:

Reduced page views in analytics tools (and therefore higher bounce rates)
Missing sales for commerce websites (this is one of the more common issues reported by clients who have a low utag.js call)

Have I understood your question correctly?

Thanks!

Roshan

abrahameaso · ‎01-05-2016

@roshan_gonsalko Truely Appreciate Your help. Yes you help me clearly clarify my queries. Thanks

Thanks & Regards
--------------------------------------------------
Abraham Easo
Principal Consultant
Numeric Analytics, LLC
Bartlett, IL (CST)
m: 980-422-2044
Abraham.Easo@numericanalytics.com | http://www.numericanalytics.com
Adobe Analytics Architect/Tealium Expert/Ensighten/Google Analytics Certified

roshan_gonsalko · ‎01-05-2016

No problem :)

Tealium iQ Tag Management

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

Re: is it mandatory to do a deploy tealium container code,every time a new datalayer variable is add

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

Re: is it mandatory to do a deploy tealium container code,every time a new datalayer variable is add

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

Re: is it mandatory to do a deploy tealium container code,every time a new datalayer variable is add

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

Re: is it mandatory to do a deploy tealium container code,every time a new datalayer variable is add

is it mandatory to do a deploy tealium container code,every time a new datalayer variable is added?

Re: is it mandatory to do a deploy tealium container code,every time a new datalayer variable is add

Products

Company