Tealium Learning Center

Reading the utag.js code directly, the session id is a just a timestamp tracking when someone landed on the page without a valid session in the cookie (after more than 30 mins). So theoretically two users arriving at the exact same time in milliseconds could be assigned the same session_id. We don't use that for any purposes than general tracking of user's sessions as far as I know. RDses: function(o, a, c) { a = (new Date()).getTime();//this is where the session is calculated c = (a + parseInt(utag.cfg.session_timeout)) + ""; if (!o["cp.utag_main_ses_id"]) { o["cp.utag_main_ses_id"] = a + ""; o["cp.utag_main__ss"] = "1"; o["cp.utag_main__sn"] = (1 + parseInt(o["cp.utag_main__sn"] || 0)) + ""; ..... ... View more

Hi,   This is not a normal behaviour. I would check with support for more details with the URL of the issue and profile. The first trace is the usual trace showing a page load normal call. The second trace seems to indicate that there is an extension "end of tags" triggering a manual call. I would review the configuration with the help of support.  ... View more

@NagaSai another possibility is to have a lookup table extension to put the IATA number and to create a new boolean variable in the datalayer (prefixed by the vendor for instance). You could then use the true/false variable in the load rule and use the extension to modify the numbers. ... View more

Hi Pavel, The behaviour will depend on which version of the consent manager you are using. The V1 version (the default version) doesn't queue the pageview or other events before consent is given. So you would need to manually add a utag.view() call on the event listener linked to the accept button in the JS script. However if you update to our 2.1 version of the consent manager this tracking call is automatically queued and sent. To check if you have that version, look in your template section and the version 2.* should have 4 templates prefixed by "Consent Manager". if you don't have it please ask support to configure it for you. Version 2 would have the header in the Consent Manager Central template //tv:2.0.0 Version 2.1 (generated from a new install) would have  //tv:2.1.0 Hope this helps,   Thomas I'd recommend upgrading for this purpose. ... View more

Hi Chipe, There is a setting called Page Data Object in the publish settings. This enables you to tell utag.js that you are using a datalayer with a custom name. Have you used that setting? https://community.tealiumiq.com/t5/iQ-Tag-Management/Publish-Configuration/ta-p/13632 Regards, Thomas ... View more

HI, To store and analyse this data, you need EventStream to forward those events to your own endpoint via a webhook or connector. The storing would then be managed by yourself. Alternatively if you have EventStore or EventDB, you can import the raw events from EventStore or analyse them directly in our Redshift database (EventDB) with a visualisation tool. EventStore has an unlimited retention period, whilst EventDb is more limited. I would check with your account manager if you have the licenses for either EventStream or EventStore/EventDB to do so. Hope this answers your question.       ... View more

HI, Actually personally I find IDs not very robusts as any one could remove and add a tag changing the IDs so your code would break. It's also hard to manage in terms of libraries: the tag would have a different ID in every profile. In this instance I would recommend using the trackEvent() method and create your own event for instance ("scroll", "ads_impression", etc..) You can then go in the template of the tag and add that event at the top  u.ev = {"view" : 1, "link": 1,"scroll":1}; So this means you can whitelist some tags and only the tags with that event will  fire when you trigger your call in React.  Hopes this helps ... View more