Tealium Learning Center

There may be something else going on here. A few things to check: (1) Is your JS Extension scoped to your SiteCatalyst tag? (2) Is the configuration for your tag set to use the "s" object? // Sample SiteCatalyst JS Extension in Tealium s.usePlugins=true; window.s_doPlugins = function(s) { // custom code here utag.DB("Inside s_doPlugins function"); } s.doPlugins=window.s_doPlugins; ... View more

Most likely your s_doPlugins function is not defined in the global namespace. // Define the s_doPlugins function in the global namespace window.s_doPlugins = function(s){ // my doPlugins code } ... View more

I *think* Google only uses the header to get IP address for GEO-location lookup info. The referrer is part of the param list. The "dr" param is used to send the referrer to Google Analytics. This is documented here: https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#dr That said, this "dr" param is not currently supported in mapping for Google Universal Analytics in Tealium. This would be an enhancement request and I'm sure we can add it for you. Please contact your Account Manager to make sure the enhancement is logged and prioritized. ... View more

I found your code block in this library: https://github.com/blueimp/JavaScript-MD5/blob/master/js/md5.js Maybe someone has pasted this library in a JS Extension? (or a pasted in a library that uses this md5 library)? ... View more

We may need more details here. Do you have a JS Code Extension in Tealium IQ that is creating the "define" function? ... View more

A workaround posted here: https://community.tealiumiq.com/t5/Mobile/How-do-you-map-UDO-elements-to-context-data-variables-for-a-non/m-p/5261 ... View more

Joe, Thanks for bringing this to our attention. The cookie fix is now included in the utag.js version 4.37 template. The template update is set to release tonight and be available on Feb 20, 2015. This is a great catch. Previous utag.js versions would treat the "$" as a delimiter in the utag_main cookie. This resulted in a messed-up cookie. Combine that with the comma in "$50,000" and you would see the strange cookie created. (Note that cookies set outside of utag_main were not impacted as they would not use the "$" as a delimiter for name/value pairs.) We've also added logic to clean up cookies in a bad state (this will remove the comma in previous cookies.) ... View more

This seems like a good feature for those with a lot of profiles. Here are some options: (1) Build a client-side script to poll your set of utag.js files out there and return the version (2) Contact your AM to have us run the report server-side (this is done.) :-) For doing "mass updates" of tag templates, we also have two options: (1) Writing a script to login to each account and remove the template. This shouldn't be too difficult, but you would have to leave your browser open while it does the work. (2) For a really large account (i.e. 100 profiles) we could submit a ticket to our DevOps team to do server-side template removal. ... View more

Hi Andrew, New Relic team had a strong preference for their JS to be inline in the HTML source and politely requested to be removed from our marketplace. From a technical standpoint, a fully functional New Relic code snippet can be inserted into the utag.sync.js container and run synchronously in the HEAD. However, the New Relic team has let us know that running their code from within an external container is not officially supported. (Our previous async tag did only support a subset of their features.) For more detailed information, please open a ticket at support.newrelic.com. ... View more

// For reference, here is the code to run in the Console to set the cookie. // (Replacing the upper-case values with actual lower-case values) document.cookie="utag_env_ACCOUNT_PROFILE=//tags.tiqcdn.com/utag/ACCOUNT/PROFILE/qa/utag.js; path=/; domain=YOURSITE.com"; ... View more

There are probably a couple ways to do this. Current version of utag.js will bring in the GUA tag and fire for a manual utag.view call on the page (assuming the manual utag.view call would not have an order_id in the data layer passed to it.) For your scenario, you might do this: (1) Keep the load rule at "All Pages" for GUA (2) Create a JS Extension to block the extra order event from tracking (be sure to persist the current transaction id in a cookie *after* this extension runs so you capture the original order) // Sample JS Extension (scoped to GUA tag) to stop a specific event if (b.order_id && b["cp.transaction_id_coookie"] == b.order_id){ return false; } ... View more

This is typically solved in E-Commerce by not allowing the customer to view the order confirmation page again. (The data layer order_id value is only set for the first purchase.) You can also put in a client-side fix in by setting a cookie with the transaction id. The load rule would fire your Google tag when: (1) On a page that is not the order page (no order_id value) OR (2) On the order page AND the transaction id cookie does not exist (first time order) OR (3) On the order page with order_id set AND the transaction id cookie exists AND its value does *not* match the current order_id value in the data layer Use Tealium's Persist Variables Extension to persist your transaction id in a cookie. ... View more

Your approach seems right with respect to creating a new data point and then mapping this value in your tag. The code below (in a JS Extension) is to create the new data point called "event_date". If you want GMT. Use "toUTCString()" instead. b.event_date = (new Date(parseInt(utag.data["cp.utag_main_ses_id"]))).toUTCString() ... View more

The client-side session start timestamp is available in the built-in data layer as "cookie" data type called "utag_main_ses_id" You could create another variable event_date (UDO type) // JS Extension to add current time (in a string format) to data layer b.event_date = (new Date(parseInt(utag.data["cp.utag_main_ses_id"]))).toString() ... View more

Hi Drew, Thanks for the follow-up. The utag.js template version 4.35 (released today) has additional debugging for manual utag.view calls. For dynamic code, the utag.DB(e) should be in there for Load Rules very soon (next month? don't quote me on release dates..) We're also adding additional debugging output in each of our tag templates moving forward. Let your Account Manager know if you have a favorite template that would benefit. One more recommendation. Add this as a JS Extension scoped to your tag (or scope to multiple tags.) // output data layer snapshot at the point when this tag runs utag.DB(b); If you do a lot of data layer manipulation you may wish to add this as two Extensions. One that runs first and another that runs after all the others. ... View more

Hi Koen, I'll have to refer you to your account manager for more specifics (cost, etc), but I can answer a few of these. For #1, the main use case for server-to-server is pixel reduction. Let's say you have 3 or more Analytics Vendors on your web site and you want to reduce the 3 tracking calls to 1 Tealium DataCloud tracking call. For example, you have SiteCatalyst, Google Universal Analytics, and your own internal data collection server. With server-to-server, one DataCloud tracking request client-side can send data to all 3 locations server-side. For #4, only the most popular analytics tags are currently supported: SiteCatalyst and Google Universal Analytics. Although with the Tealium Generic Tag you can send data to any data collection server. For #7, you're right. The reading the 3rd-party cookie client-side is required in many cases -- this makes it less likely you would want to run other tags (non-analytics) pixels server-side. For most of these use cases, Tealium's AudienceStream server-side connector integration may be a better way to go. For #8, extensions run client-side to manipulate the data and then the data layer data points are then mapped to the right place. Depending on your use case, you may be more interested in AudienceStream badging and integrations with DoubleClick (DFP) in AudienceStream. For #9, I recommend using Google Universal Analytics for debugging. You will need to: (1) Look at data layer that is sent (in DataCloud tag in the browser) (2) View report in your analytics tool to confirm it arrived For AudienceStream, there is a set tools available for real-time debugging and reporting of your data layer. ... View more

In terms of a workaround, this may be an option // wrap in anonymous function to allow for return false in code (function(){ utag.DB("DOM Ready Extension"); return false; })(); ... View more

I see, you're saying "return false or a JavaScript error." Using the return false probably doesn't make sense here (when Extension is scoped to DOM Ready). For JavaScript errors, a JS Extension scoped to DOM Ready is wrapped in its own try-catch block. There is some isolation that comes built-in with respect to potential JS errors. ... View more

If you "return false" in an Extension scoped to a Tag then it will stop all subsequent Extensions scoped to that tag from running and ultimately stop the tracking event itself (for that tag.) This is a feature that allows you to stop the tracking for a specific scenario. // stop tracking for a specific value in the data layer if (b.event_type == "private") return false; A similar feature in Web Analytics might be setting the "s.abort" feature in SiteCatalyst: http://microsite.omniture.com/t2/help/en_US/sc/implement/abort.html With "return false" feature, Tealium is effectively giving you this same functionality for all tags in the Tealium Marketplace. ... View more

Hi Joe, We need this feature and I will add your name to the list of clients requesting. The short term solution is to build a JS Extension (use Javascript code) to accomplish. That will allow code for the logic "when this should run" to be included in the same Extension. We can help build this for you of course. -Ty ... View more

Nora/Alessandro, Thank you both for the feedback and tips. Every time we remove a synchronous script, we make the world a better place. :-) ... View more