Tealium Learning Center

Hi Kayvan, The Tealium Custom Container template has comments in there to provide details on how to use it. In general, it may be better to write custom code in a Javascript Extension and scope it to your Custom Container. In that way, you don't need to go to "Manage Templates" in order to update your code.. just edit the Extension that is scoped to this tag. The only template that should need to be "Managed" on your end is the Tealium Custom Container. If there is a specific tag vendor template that appears to be different from an implementation guide you have received from the tag vendor, please let your account manager know. We'd like to update the master tag template to make sure it is current for all clients. Here is a post on the Tealium Custom Container: https://community.tealiumiq.com/t5/Tealium-iQ/Tealium-Custom-Container/ta-p/14015 Let me know if this is helpful or if you have a specific question around Templates ... View more

Take a look at this Extension: https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/SiteCatalyst-Visit-Details-Extension/ta-p/5131 Stay tuned.. this "page view (event) count" will be something you can grab from the utag_main cookie. Look for this in a utag.js template releasing next month. ... View more

Correct. This is a different approach. You would then segment on certain errors to see if: "Those who see this error are less likely to make it through the registration process." If you find that those who see the "fake phone number" error are less likely to complete the form, you would consider removing this field or removing this as a required field. I'll see if I can have your Account Manager contact you. :-) ... View more

Hi Mark, We do have a simple form abandonment tracking snippet of code we can provide. This is an Extension in Javascript form. It allows you to specify specific forms to track and you can report on "the last form field that had focus before the user clicked away from the page." Please contact your AM to get the code for this. Let us know if this is what you are looking for and we can make it a formal post of this code in the Community. To Adobe's response.. The data may show that it seems random or it's not clear what to do with the fact that field 12 has the same last-field-focus rate as field 5. So there may be better strategies for increasing conversion. One approach is to A/B test out a few forms and then just use a Funnel report to see which form has the highest "make it to the next step" rate. Another idea is to build in "utag.link" tracking calls into your form logic to report errors. For example, in your form validation logic, send a tracking request for each error message you display. utag.link( { form_name : "registration", event_name : "form-error", form_field : "phone number", form_error_message : "Bogus phone number entered" } ); (You would then map these values to s.props and eVars of course.) ... View more

I am assuming you are talking about the SiteCatalyst tag config? You should just need to enter "www.vpdev." as your filter to cover all your domains. The Omniture code just looks for a 'contains' match. ... View more

Joe, you're reading our minds. I just an an email to the team (today) and we have a volunteer to code this up. We'll put together a javascript extension that will collect this info and allow you to map to your analytics tool. ... View more

You can add the following call to log output to the console. This is "IE Safe" because the utag.js will wrap the console.log call in a try-catch. utag.DB("error: ..."); To enable debugging, set this cookie: document.cookie = "utagdb=true"; The issue right now is a lot of code generated dynamically (i.e. Load Rule code) has an 'empty' catch block. We have a pending enhancement to put utag.DB calls in there as well. I think this is what you're looking for. For those empty catch blocks... you can use a Charles Proxy tool to replace files/content. You can swap out any "catch(e){}" with "catch(e){utag.DB(e)}" as a workaround. Not an easy workaround, but I think this may be what you're trying to do. ... View more

When you click "Edit" to edit the tag config, you will see the "1.21" option for the "Code Version" ... View more

Did you delete your SC App Measurement tag template? And you are still seeing an issue? If yes, then probably best to submit a support ticket. Also, as an FYI.. We plan to update the App Measurement library code to the latest version this week. You will see another dropdown option in the tag config. ... View more

You're welcome. Give us about 3-4 hours more for our release to go out tonight. (Or get the new template first thing tomorrow.) Also, the u.addEvent sets b.sc_events behind-the-scenes which allows for a little less code. And, we've added support for passing a second param to u.addEvent (that contains the value.) This may be more intuitive way to assign values to events. // Updated code: if (a=='link') { switch (b.contenttype) { case 'Content Copy': u.addEvent("event40"); u.addEvent("event41=" + b.count); // NEW: u.addEvent("event41", b.count); break; } } ... View more

I think you're right with s.pageURL.. Your code looks good, except for the document.URL should be upper-case "URL" s.pageURL = removeQueryString(document.URL); ... View more

I don't remember if s.referrer is set or if it is just something you can use to override the default. Here is an update to your code: // In the "doPlugins" you could do this function removeQueryString(a) { return a.split("?")[0]; } // truncate s.referrer to reduce pixel size s.referrer = removeQueryString(document.referrer); ... View more

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

That should work too.. ... View more

If this script includes synchronous code (i.e. document.write calls), you will need to place this code in your HTML source at the point where you would like it to execute. ... View more

If you know that your visitor is "Opted In" to everything (from a legacy cookie or a server-side value) you can override the Tealium Privacy Manager Extension. // Assuming that utag_data (Data Layer) is in the HTML source above utag.js // Requires: // (1) This Extension is scoped to "PreLoader" // (2) This Extension is listed *below* the "Privacy Manager" Extension in the UI. This is important. // (3) Data Layer has a value that indicates if the server knows the visitor has already opted in // utag_data.optedin=true; if(utag_data.optedin){ // expire OPTOUTMULTI cookie document.cookie = 'OPTOUTMULTI=; expires=Thu, 01 Jan 1970 00:00:01 GMT;'; } ... View more

Lars, Thanks for these details. For now, you may have to open up an new "hidden" iframe on the landing page (an iframe in your domain) that will run the utag.js again on the landing page. This will allow utag.js to read the cookies and fire the tags on the first page of the user's visit (before moving to a new page.) This is probably not the ideal solution. Craig's solution may also work. I think this is what he is describing.. (1) Preloader Extension: // if this is the landing page (no cookies set yet) window.utag_cfg_ovrd = {noview : true}; (2) Show privacy solution (3) Call utag.view to fire tags One final note, we're working on a new utag.js template that will re-evaluate load rules with a utag.view call. This would allow you to call utag.view to "load" in new tags after they've adjusted their privacy settings. ... View more

Param, In order to accomplish "guaranteed" tracking, typically you would need to control all of your outbound links by "blocking" the built-in click functionality in the browser and doing the navigation in Javascript. This is shown here: https://support.google.com/analytics/answer/1136920?hl=en I generally don't recommend this because you are now introducing a chance that your custom Javascript has a bug and your links will no longer work. If you are willing to take on the risk, you should be able to build something in your page (or possibly in a jQuery Extension in Tealium) that is similar to the code in the Google support link above. You would replace _gaq.push(['_trackEvent' call with a utag.link call. ... View more

We recommend only running "Asynchronous" scripts on your website. By default all tags are set to "Wait" when added in Tealium. That means we are prioritizing your page render before loading in additional tags. From what I can tell, the AppNexus is not a "blocking" tag but a simple image pixel. Are you running a custom version of their pixel? Can you provide more details on how your site was "hung"? ... View more

Got it. I think that's the issue right now (large # of extensions.) From the other clients that have reported this, they have close to 200 extensions. I'm not sure who has most of the "blame" at this point (our algorithms or jQuery or some other library) for the slowness.. But it's something we will definitely fix. I don't have an ETA, but we've moved this to near the top of the list in priority. Your account manager can keep you updated on the latest status. ... View more