Tealium Learning Center

Hi @vijay_yadav  Glad to help.  When submitting a request for a demo, someone should have reached out to you via email to provide you with account info, however, since it has been about 3 months since you posted this issue your demo account may have expired.  I am unable to access your demo account and it's not recommended to post any account information within this forum, so I would suggest resubmitting a demo request here: https://tealium.com/cdh-demo-2/ There is a comments section where you can explain that your demo account didn't work and even reference the URL of this forum post.  Our team will happily set you up with another demo account. Thank you.   ... View more

Hi @tealium23    Thanks for the clarification.  Since this is a trial account, I recommend reaching out to the Account Manager or Tealium Rep that provided you with the credentials.  They will be the best means of support for this particular issue. ... View more

Hi @leonlee    It depends on what you mean by manage.  There is not currently a feature to classify cookies into categories within the context of Consent Preferences Manager, however, Consent Preferences can be customized, however any modifications will need to be developed and QA'd by your team.  This may be something you'd want to submit support ticket for so that a Support Enginner can review your account.   Thanks ... View more

Hi @Teuszie  Thanks for reaching out. When variables are added to TiQ and a publish is made to PROD.  They will automatically be added to EventStream as an "any-type" attribute, and as you have experienced, it will limit the available conditions that can be applied to it.  You are correct in your thinking, the two options would be to: 1. change the Event Attribute from "any-type" to "array" 2. Create a Visitor Attribute Array that is based off of the Event Attribute Great job! ... View more

Hi @allanpaixao    Great question.  There is currently no feature to adjust the timezone within TiQ.  However, we offer 3 different timestamps: If you need to capture the time in a specific timezone and format, you can use a Javascript extension and leverage the built-in Javascript Date Object to capture and adjust the time to your needs.  Here are some helpful articles on working with dates in Javascript: https://www.digitalocean.com/community/tutorials/understanding-date-and-time-in-javascript https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date ... View more

Hi @tealium23  Thank you for reaching out. Hopefully, this issue has been resolved, but to answer your question, our Support Team has not had reports of clients unable to load their profiles.  I recommend submitting a Support ticket if this continues to occur.  Additionally, we have a Status website that can provide you more insight on sitewide issues: https://status.tealium.com/ Please let me know if this helps. Thank you ... View more

Hi @cravn I believe there are a few FlashTalking Pixels in the marketplace, but the same should apply to both.  To validate if a Pixel is firing multiple times, you can use the Network Tool in Chrome Dev Tools.  If you filter by "Flash" you can see all the network calls related to FlashTalking and determine if there are any duplicates.  It may be useful to enable "Preserve Log" in the case there are any redirects, but make sure you clear the log before reloading the page: Please let me know if this helps. ... View more

@ELSAGUILLON  The feature of a preloader is to run code before utag.js has completed.  At the point a preloader runs, utag_data will only contain the values that it is originally defined with on that page.  It will not contain cookies, dom variables, or any other Tealium provided variables and therefore you will not have access to use those variables from a Tealium perspective. If you do want to check the value of a cookie, you can use a function similar to what is described here: https://stackoverflow.com/questions/5968196/check-cookie-if-cookie-exists   ... View more

Hi @Fabi    My apologies, I completely overlooked that you wanted to activate the audience within the time frame of 7 days.  To do there are 4 steps: Create a Visitor Scoped Timeline Attribute to capture when a customer visits a PDP page and expires after 7 days Create a Visitor Scoped Number Attribute that captures that enriches by capturing the number of entries in the timeline Create a Visitor Scoped Badge Attribute that enriches based on the Number Attribute Create an Audience based on the Badge   Step 1: Create a Visitor Scoped Timeline Attribute to capture when a customer visits a PDP page and expires after 7 days  Add a visitor scoped Timeline Attribute Add an enrichment to capture the timestamp on ANY EVENT with a rule that the page_type equals PDP (may be different on your website)  Add an enrichment that sets the expiration of the timeline, within this example: 7 days   Step 2. Create a Visitor Scoped Number Attribute that captures that enriches by capturing the number of entries in the timeline Add a visitor scoped Number attribute Set the Type to Integer Add an enrichment that sets the Number attribute to the number of events captured in a Timeline Select the Timeline you created in Step 1 Step 3. Create a Visitor Scoped Badge Attribute that enriches based on the Number Attribute Add a visitor scoped Badge Attribute Add an enrichment to assign the badge when the number attribute created in Step 2 is assigned and greater than or equal to 3 (optional) Add an enrichment to remove the badge when the number attribute created in Step 2 is unassigned and less than 3 Step 4. Create an Audience based on the Badge   Please let me know if this helps! ... View more

Hi @Fabi    To implement this use case, you will need: Visit Scoped Number Attribute Visitor Scoped Badge Attribute Audience  Step 1:  Create a Visit Scoped Number Attribute with an enrichment that will increment by 1.  In this example I call it "PDP Visit Count" Add a rule so that the enrichment will occur when the user visits the PDP page In the image below, the rule is driving the enrichment and in this example, page_name is used to identify if a webpage is a Product Detail Page (PDP), it may be different on your website. Step 2: Create a Visitor Scoped Badge to assign when the Visit Scoped Number Attribute equals 3 Create a Visitor Scoped Badge, for example, "Visited PDP Page 3 Times" Add an enrichment to Assign this badge with a rule for when the "PDP Visit Count" Number Attribute equals 3 (optional) If you want this badge removed after each visit, you can add an additional enrichment to remove that badge when VISIT ENDED Step 3: Create an Audience based on the Badge you just created. Create an Audience based on the "Visited PDP Page 3 Times" Badge just created   After that, you should be all set. Hope This helps!!  ... View more

Hi @DDZS2020  If you want to track a button click, there are generally two options.     1. Within your source code. You will want to leverage a utag.link() tracking call and pass in the data you want to get picked up.  When the event listener is triggered, the utag.link() call fires, which prompts utag.js to run and the extension to process the data layer.  Here is documentation on our tracking calls:  https://community.tealiumiq.com/t5/Customer-Data-Hub/How-to-Pass-a-Google-Analytics-Custom-Dimension-through/ta-p/26371?advanced=false&collapse_discussion=true&search_type=thread 2. Within TiQ using a jQuery or Javascript Extension. you can leverage a jQuery Extension or javascript Extension to place a tracking call within TiQ.   Based on your code snippet, it looks like you want to leverage jQuery.  Here is the documentation on that extension: https://community.tealiumiq.com/t5/iQ-Tag-Management/jQuery-onHandler-Extension-jQuery-1-7-and-up/ta-p/9868 It contains great code examples and at the bottom breaks down how the jQuery code looks within utag.js Also, I noticed a typo in your code sample, that may be the issue as well: Hope this helps! ... View more

You could add a condition to the preloader javascript extension that doesn't trigger on non SPA pages. But even if the page is a non SPA, by using the "window.utag_cfg_ovrd = {noview : true};" configuration, that disables all auto pageviews, meaning you could also manually trigger a utag.view() call on a non SPA part of the site. ... View more

Hi @jbalandranocoro    I just realized that you may have been asking how to trigger events within the MixPanel Tag within TiQ: In your example, you want to send an event like: mixpanel.track('eventName', { ...eventProperties })  This can be achieved through Data Mappings.  For example, if you wanted to track when a user adds something to their cart and also pass the product_id here are the steps: Let's say when a customer clicks add to cart on the site, an event listener triggers a utag.link event and passes this object: { tealium_event : "cart_add", product_id : ["123456"] } Knowing this, within Tealium we can configure the MixPanel to send that event like so: 1. Open the Data Mappings within MixPanel and choose the variable tealium_event and within the mappings: Select Events in the Category Column set the trigger, in this case, we want to trigger a track event whenever tealium_event equals cart_add   2. Next, we can pass an event name, within this example, we can use cart_add , since that is also the name of our event. Select tealium_event from the dropdown within the mappings section, go to Event in the left column In the first drop down we want to choose which event tealium_event will be associated with, in this case Track In the second dropdown, we can choose where tealium_event  is assigned within that event, in this case, Event Name 3. Lastly, we will want to configure product_id to be sent whenever the cart_add event occurs.   Select product_id from the dropdown within the mappings section, go to Event Parameters in the left column In the first drop down we want to choose which event tealium_event  will be associated with, in this case Track In the second dropdown, we can choose where cart_add is assigned within that event, in this case, Event Name After we complete the data mappings and publish.  When a user clicks on an Add to Cart Button, the tag will fire and pass this event: mixpanel.track('cart_add', { product_id : "12345" }) If you want to look at the Tag Template, it may help you get a better idea of how the code is being processed, for example here is the mixpanel.track function at work: To view the tag template, it is within the Advanced Settings of the Tag Configurations. https://community.tealiumiq.com/t5/iQ-Tag-Management/Managing-Tag-Templates/ta-p/21713   Good luck and let me know if that helps.     ... View more

Hi @jbalandranocoro    Here is a link to a previous post that may help: https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/utag-track-method/m-p/24578 Additionally here is the documentation for the tracking events: https://docs.tealium.com/platforms/javascript/track/   Please let me know if this helps. ... View more

Hi @nathan  Without seeing how it's configured, it would be difficult to troubleshoot.  If there are other events occurring on the page, they might be triggering the Date attribute to reset, you could try to add a rule to the Date attributes that only sets them when  ut.event equals 'view' This will ensure that the date is being captured on page views. I tested this in my sandbox and both my Date attributes look like this: Here is my Number Attr:  In my trace, I can see the calculation working fine after spending a minute on the page: It sounds like there could be other events happening on the page that are resetting the date captured.  If adding the additional rule does not help, you may want to submit a support ticket so an Engineer can investigate your webpage and profile. Thanks ... View more

Hi @ChrisWallis  I recommend adding the code at the preloader level.  You can use DOM variables, such as  document.location.pathname just not utag.data["dom.pathname"] because utag.data would not have been defined yet.  ... View more

Hi @AshokPrasad  Great question.  We have two jQuery Extensions: If you are migrating from jQuery v1.6 or below, you will need to update any jQuery extensions to the current v1.7 and above version. If you are migrating from jQuery v1.7 or above, you will not need to make any updates to your current set up. The jQuery extensions are scoped to DOM READY and cannot be changed This scoping means that the jQuery Extensions load with utag.js and could potentially cause issues only if using the Custom Feature of the extension to add additional code: With regards to the most current jQuery Extension v1.7 and above, the code that is injected into utag.js will look something like this: jQuery('#feedbackForm').on('mousedown', 'input.submit-action', function(e) { utag.link({ "tealium_event" : 'feedback_submitted', "feedback_message" : $('#feedbackForm textarea').val(), "username" : utag.data['username'] }) }); This is the extent of how we utilize jQuery - we make a reference to the library and use the standard on method to define what event to listen for.   Therefore the only dependency issues could stem from custom code that utilizes jQuery like in a javascript extension or using the "Custom" setting within the jQuery Extension as I stated above. For more information on our jQuery Extension, here is a link to the documentation: https://community.tealiumiq.com/t5/iQ-Tag-Management/jQuery-clickHandler-Extension-jQuery-v1-6-and-below/ta-p/13707 https://community.tealiumiq.com/t5/iQ-Tag-Management/jQuery-onHandler-Extension-jQuery-1-7-and-up/ta-p/9868#toc-hId-735859166   Hope this helps! ... View more

Hi @ksugam  A solution to this would depend on how things are setup within your website and Tealium account. Here are some general approaches that will work, but may need to be tweaked depending on your setup.   Method 1 If you know that two tags will fire by default.  Once consent is granted, you can specify what tags are triggered in a utag.view() call.  It accepts an array of UIDs as one of it's parameters. utag.view(data object, callback function, array of UIDs) So if Tags 1 and 2 fire at page load.  You can configure your event listener to fire utag.view({data object, null, [3,4,5]) Caveat is that you need to ensure that this function is kept up to date.  If you turn off a tag in TiQ and do not update the utag.view call to remove the UID from the array, the call breaks and no tags fire period.   Method 2 Pass an event variable into the utag.view call, then set up a load rule on the 2 default tags to not fire on that event. Ex.  Page loads, Tags 1 and 2 fire > User opts into tracking and click ok > utag.view({"tealium_event": "opt_in"})  Then set up a load rule on tags 1 and 2 within TiQ that only fires the tags when tealium_event does not equal "opt_in")   I prefer method two, but of course, it may depend on how your set up is.  Also since Tealium is run on Javascript, if you can think of an alternative solution, a javascript extension is a powerful tool.   Hope this helps! ... View more

Hi @Vaytekus_Olha      1. Add a Javascript Extension and Scope the Extension to the Adobe Analytics Tag so that it runs after the library is available 2. Add the function you provided for the ID sync 3. Add conditions to only fire when the user is logged in and authenticated Please let me know if that helps.   ... View more