Tealium Learning Center

Jeff, Thanks for your feedback. I'm adding your comments to the existing bug for UI performance improvements. Please also contact your account manager with this information (include the specific account/profile.) In general, we use Chrome for the UI. The significant slowness you are seeing is not typical, but even a 2 second delay is too long. This morning, we did have some issues with Amazon servers (impacting many of Amazon's clients.) This specific issue is now resolved. Again, thanks for this detailed information. ... View more

If you use the "synchronous" utag.js implementation on your page, you can use the Maxymiser implementation described here: https://connect.maxymiser.com/560_The_OneTouch_Network_and_Tag_Management_Solutions/TMS_Bootstrap_Integration_Guidance Instead of running Maxymiser as a "tag", place the single line of code from Maxymiser in a Preloader scope Javascript Extension. Remember, you must have the utag.js coded in the "synchronous" format (seen in Code Center) in order to use document.write. Tealium does not recommend using synchronous scrips or document.write calls (as a best practice.) However, Maxymiser has a strong preference to be synchronous. ... View more

Eric, please contact your Account Manager for help. As Clint mentions, the "Tealium Pixel Container" or "Tealium Generic Tag" maybe the way get this pixel on your site right away.. before it is added to the Tag Marketplace. ... View more

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. :-) ... View more

Hi Marina, Most likely you'll need to trigger the event off of a different variable. In your Data Layer, most likely you have a page_type variable that is set for page view events. And, you have an event_name variable that is set for non-page view events. It might look something like this in mapping for your SiteCatalyst tag: page_type (js) ===> product_page:prodView,cart_page:scView event_name (js) ===> card_add:scAdd Please consult your Account Manger if you need more details for your specific profile. ... View more

Hi Kris, Your example should work if you want to use the "custom" option and call Webtrends functions directly. If you call "utag.link" then the template will call multiTrack for you. Just make sure to map "parameter1" in Mapping. Anything that is mapped and has a value will get sent along in a multiTrack function call. // manual call to utag.link // requires parameter1 mapped to WT.something in mapping utag.link({"parameter1" : "value1"}); NOTE: If you choose "link" option (instead of "custom") in the jQuery onHandler Extension then the extension will call utag.link. ... View more