Tealium Learning Center

Hi @mitchellt,   You can use a jQuery onHandler extension, configure a jQuery selector for the link (or element) that you want to track and trigger a "view" to fire a virtual page view, or a "link" to fire a link event.   Depending on the tag that you want to track this for, you may need to set/populate a certain UDO variable.   e.g. Set "event_category" to equal "button", "event_action" to equal "click for Google Analytics event tracking, using a "link" trigger   e.g. Set "page_name" to equal "Quick View Product Page" for Google Analaytics page tracking, using a "view" trigger   For tracking virtual page views, you may want to be doing "AJAX tracking".  If so, please read up on this here (https://community.tealiumiq.com/t5/iQ-Tag-Management/AJAX-Tracking-in-Tealium/ta-p/14034)   Does this help? ... View more

Hi @LCasadiego,   Here is a list of the data-layer variables for Anroid (https://community.tealiumiq.com/t5/Tealium-for-Android/Data-Layer-for-Mobile/ta-p/16851) and iOS (https://community.tealiumiq.com/t5/Tealium-for-iOS/Data-Layer-for-Mobile/ta-p/16329).  "exception_name" and "exception_trace" are not standard variable names.   You can still define these if you'd like.  To track exceptions, I recommend using a try-catch statement.  In the code block of the catch statement, you would code a Tealium trackEvent call and pass exception value.   Android: https://community.tealiumiq.com/t5/Tealium-for-Android/Adding-Tealium-to-Your-Android-App/ta-p/16846#track_events iOS: https://community.tealiumiq.com/t5/Tealium-for-iOS/Adding-Tealium-to-Your-iOS-App/ta-p/16327#track_events   ... View more

Hi @giacomo_ritucci,   You can define a Time-based Load Rule to fire a tag from Date/Time A to Date/Time B, but not the other way around.  Unfortunately, you cannot defined one to be the opposite (i.e. to not fire a tag from Date A to Date B) Instead, you can create two copies of the tag: one to fire before Date A, and one to fire after Date B.  This way the tag never fires from in-between Date A to Date B. ... View more

Hi @00pritchard,   You should just be able to set the props and eVars directly.  For example, say you have foo mapped to prop1 and eVar 1.  You can set foo to text "bar" using a Set Data Value extension under the same conditions as when you are using the u.addEvent method.   ... View more

Hi @vdevaraj,   I've seen this plugin fire/set the eVars/props as needed on the subsequent pageviews/refreshes.  Do you still not see it when refreshing the page? ... View more

@steve_fernandez,   The new Twitter Universal Tag is using a new library (https://static.ads-twitter.com/uwt.js). I believe you will need to get a new code snippet to replaced the old one that still uses (analytics.twitter.com). ... View more

@rushikesh_naik,   What version of jQuery is your site using (i.e. below or above 1.7)?  Make sure you are using the correct jQuery extension as we have (2) of them.   One for jQuery versions 1.6 and below.  Another one for jQuery versions 1.7 and above.  Both use different jQuery methods. ... View more

@gelerind,   Ideally, you would want to hardcode a utag.link or utag.view call directly in the a success of your AJAX responses.  However, since the code is out of your reach then this is not a option for you.   One solution may be to use a jQuery onHandler Extension, select a certain element you want to trigger off of say a "mousedown" event of a "Next" button.   Another solution, would be to use a custom JS extension and attached an event listener to the ajaxComplete event.  From there, you can check each request to see if it is the correct AJAX response you want to trigger your utag.link / utag.view event. jQuery(document).on('ajaxComplete', function (a,b,c) { // Check a, b and/or c if (a.url === 'http://www.foo.com/?quickview=true') { // Fire Tealium utag.link({ event_type : "next step" }); } }); ... View more

@jmillan,   That is correct.  If you want to merge data from a utag.link then you can use a === "link" ... View more

@Christopher_M,   You can add the "jQuery" tag from the Tealium Marketplace.  It will automatically inject the jQuery library on all pages.     Just click on the "Tags" tab, click "+ Add", then search for "jquery". ... View more

@loldenburg,   Are your DOM-Ready scoped extensions relying on this other service?  If so, then you will have to change the scope of your extension(s) to execute when the other service has finished.  Otherwise, you will continue to run into issue of a race condition. All track calls (i.e. view/link) will have to be consolidated to fire when and only when your other service(s) has finished and returned its data back to you. ... View more

@jan_van_damme,   Yes, that is the expected behavior.  Any track call (e.g. utag.view or utag.link) will merge the data into your UDO.   In our latest version of utag.js (v4.40), this behavior no longer "merges" the data.  If you'd like to upgrade to the latest version, please reach out to your Account Manager and they can help with this to ensure a smooth transition.   Here is our release notes for v4.40 with its changes https://community.tealiumiq.com/t5/uTag/utag-js-version-4-40-Release-Notes/ta-p/12946 ... View more

@loldenburg,   Building off of @steve_lake's comments, this will disable the initial pageview trigger that "utag.js" sends by default when it is loaded.   When doing so, you then will have to have to fully gather/generate all your data points into your data object (e.g. utag_data).  Once you know you have all the data you need in your object, then you'll manually trigger the your page view call, passing in your data object. For example:     // Waiting for 3rd-party data to come back here var thirdPartyData = "foo"; // Pushed 3rd-party data into my utag_data object window.utag_data = window.utag_data || {}; window.utag_data.product_id = thirdPartyData; // Then manually trigger your page view utag.view(utag_data);     There's really no other robust solution as Tealium does not know when your asynchronous service will finish and return its data.  You will have to control that logic and manually send the page view call when you have received your data. Just to reiterate as Steve already mentioned, using the "noview" override will 100% disable the page view call from triggering before your third-party service finishes.   Hope this helps!   ... View more

@abrahameaso,   The VisitorAPI is already in the latest AppMeasurement template.  You just need to add your Marketing Cloud ID in the Tag Configurations.  Once you've done that then the template will automatically load the VisitorAPI. ... View more

@mitchellt,   If you want certain data-sources to be captured in the your utag.view call then you will need to make sure they are defined in your data-object that you are passing in the call itself.   For example:   utag.view({ page_name : "foo", page_type : "bar", event_type : "banner_viewed" }); Another solution would be to use a Set Data Value Extension, and set the page_name to JS Code utag.data.page_name with some conditions, contingent that you already have page_name defined in your data-layer and you want to use the same value.   See below:     Remember to scope the extension to your tags, unless it is for all tags.  Hope this answers your question!   ... View more

@per_lundqvist,   When you first add and configure the Tealium Pixel (or Iframe) Container, the tag template will auto-generate depending on the setting you selected (e.g. Iframe or Image) on your first publish.   If you've selected "Iframe" then the template code that gets generated will be for firing an <iframe> pixel.  If you decide to change it to an "Image" then you will need to drop the template so that the template code will get re-generated for the <img> pixel.  Otherwise, it will continue to fire an <iframe> pixel.   When you first switch the configuration, there should be a warning alert box that pops up to remind you to drop the template.   Steps to update the template: 1. Change the drop down selection to "image"     2. A notification box will pop-up. Click "OK".     3. Go to Edit the Tag Configuration > Advanced Settings > Edit Template     4. Click on "trashcan" icon located in the upper-right corner 5. Click on "Save Profile Template"     6. Publish to your target environment (e.g. DEV, QA and/or PROD)   Let me know if this does the trick for you. ... View more

@per_lundqvist,   You should consult with your tag vendor rep if they accept <img> tags.     In addition, if you originally were using the IFRAME setting, you will have to drop the template to grab the IMG version of the template.  My guess is you have the latest template, but it may still be the IFRAME version. ... View more

@redfuel318,   Generally, our multi-CDN edge nodes will grab the latest published tag templates every 5-10 minutes if there was a change.  I think at this point you may need to reach out to your Account Manager to investigate your issue a bit deeper. In regards to getting your utag.js upgraded, you will also have to consult with our Account Manager to ensure a smooth transition.  There may be significant changes in the latest version (4.40) that could affect your profile when migrating over.  We'll need an engineer to review your profile altogether and make any adjustments (if needed), plus a thorough QA before going live. ... View more

hi @redfuel318,   Unfortunately at this point in time, we only have release notes for the Tealium Collect Tag and utag.js.  Generally, we recommend to run the "Tag Status Checker" on a regular basis to make sure all your tag templates are up-to-date.  This can be found by clicking on your name located in the upper-right corner and clicking on "Tag Status Checker" within the drop-down menu.     Also, within the tag templates itself, there are comments that say what was changed since the last version including a date stamp.     Let me know if this helps.   In the future, if you ever experience a similar issue, please feel free to reach out to your Account Manager directly to get it looked at immediately. ... View more