Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Silver Contributor
Silver Contributor
Also is there a good way to use dynamic variables to help put a friendly pagename together. Currently we use a join extension that pulls our data source variables together e.g. page.l1(s.channel) + page.l2(prop1) + page.l3(prop2) + page.l4(prop3). I would really like to try and trim my image request down and do something like s.pageName = 'D=ch+":"D=c1+":"D=c2+":"D=c3';
7 REPLIES 7
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Tealium Employee
Hi Joe, I don't think there is a good reason for not compressing on a utag.link call. We can add support for that. I'll put that on the list for the next SC template update. For the second request, the "chaining" of compressed values gets a little more complex. The compression algorithm in the Tealium SC template right now doesn't try to more that the basic substitution when entire values match. This is typically all you need to stay under the 2K limit for IE pixels and send maximum data to Adobe data collection servers. That said, we can build this if you need support for a more complex compression algorithm. Ideally, we'd like for SiteCatalyst to build this logic into their tag by default. Can you reach out to Adobe/Omniture and see if they have plans to build in this algorithm? We'd also like for SiteCatalyst to behave like another analytics tag (Coremetrics) that only sends the browser plugin data on the first hit of a session. If we can just help one tag vendor reduce their pixel size then we've done our job to save the internet.. and the planet.. from unnecessary data transfer. :-)
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Silver Contributor
Silver Contributor
Thank you. If you could please have the compressing of the utag.link call in the next template update that would be great. I will reach out to my Adobe/Omniture team and see what, if any plans they have for building a compression algorithm into their tag as well as ask them about the browser plugin data being sent only once.
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Tealium Employee
Thanks for your patience, the updated template is scheduled to be released this week. It should be available in the UI on Wednesday. (Also, for reference, Joe discovered that Adobe does have this as a plugin.)
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

We are using Site Catalyst Tag template version H25, and started using this a month back - but I'm not seeing this compression happening for utag.link() calls, do we have explicitly copy the template.
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Tealium Employee
Hi Venkat, If you can update to H26, this should be fixed. If you delete your current template (Manage -> Templates.. click the trash icon). AND change your SC version dropdown to "H26" you should see the variable compression for utag.link calls. New features (or bug fixes) for SiteCatalyst are only added to the latest template.

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Is this functionality (automatic setting of dynamic variables) supported in AppMeasurement 1.4.1 currently offered in Tealium? Also, Ty Gavin mentions above: "(Also, for reference, Joe discovered that Adobe does have this as a plugin.)" What plugin is discussed and where to get it?
Highlighted

Is there a reason tealium only automatically does omniture dynamic variables (d=) for utag.view calls and not utag.link calls? Is there an easy way to set this up? It would dramatically reduce our image request size.

Employee Emeritus
Hi Stas, It should be. I've deployed a client with AppMeasurement specifically and I'm seeing it as such in the network calls. I believe the plugin being referred to is the one that sends browser data (like color depth) once per session. You should be able to get official plugins from your Adobe rep.