Tealium Learning Center

You'll need to add the property through Google's interface, which is referenced in this Google Article, otherwise, the platform won't know what to do with the information. ... View more

This is expected because the tag doesn't exist. If you'd like to see more error handling or some sort of console output instead, you can submit a product idea to our engineering team to add that to our product. To submit a product idea, click on the "Resource Center" link within the Tealium product and then click on "Submit Your Idea".  ... View more

You can submit a request through the support portal which can be routed to our education team that can assist with access to the website. ... View more

You can access all e-learning courses at university.tealium.com. Once you register and log in, you can search in the top bar for "Tealium IQ basic exam" and the course should show up for you. If you still can't find it, please reach out to your Customer Success Manager and they can assist you further. ... View more

The only way to combine those visitor profiles (or pull an existing visitor profile) is to match the current visitor ID (tealium_visitor_id for anonymous users) or through visitor stitching (with a known visitor ID). Otherwise, the system won't know how to associate the visitors together and will keep them separate. ... View more

This functionality is not currently available in the product UI. If this is something you would like to see in our product, you can click on the "Resource Center" link in the top right of your Tealium screen, then click on "Submit Your Idea". The ideas submitted through this form are visible to our engineering team and reviewed for addition to our product. If someone else has already submitted the same idea, you can "upvote" the idea to let our team know more of our customers would like to see that feature. ... View more

No, there currently is not. If this is something you would like to see in our product, you can click on the "Resource Center" link in the top right of your Tealium screen, then click on "Submit Your Idea". The ideas submitted through this form are visible to our engineering team and reviewed for addition to our product. If someone else has already submitted the same idea, you can "upvote" the idea to let our team know more of our customers would like to see that feature. ... View more

After the function triggers in the timeout, you can clear the timeout and it won't trigger again. https://www.w3schools.com/jsref/met_win_cleartimeout.asp ... View more

The way Tealium is designed, all "date" attributes are actually stored in epoch format on the backend, which is why it needs to be formatted every time if you don't need the date in an epoch format (and also why it must be stored in a "string" format). If you like, you can submit a product idea to our engineering team to suggest handling date formats differently to make it easier for the user. You can do this by clicking on the "Resource Center" at the top right of your Tealium screen, then clicking on "Submit Your Idea". These ideas have direct visibility by our product team for consideration. ... View more

We still don't support that current functionality, but if that is functionality your team would like to see available out-of-the-box, I've included the information about our Product Ideas forum below and we recommend adding a new idea for our Engineering team and other customers to see, as our Engineering team uses this forum to prioritize new features: Product Ideas Submission: https://productideas.tealium.com/app/#/user/suggest. You can also access this form via the Resource Center menu after logging into Tealium (announcement blog). How Product Ideas Work: https://community.tealiumiq.com/t5/TLC-Blog/How-to-Submit-a-Great-Product-Idea/ba-p/20792 ... View more

In this case you'll want to combine your two events (Adobe and Facebook) into a single "utag.link()" call. You can add the parameter "fb_event_name" to the existing link call that is triggering Adobe. That single link event will trigger the Tealium Collect tag and you can then create separate event feeds in EventStream to trigger both Adobe and Facebook. For example: Current Multiple Events utag.link({ "adobe_event":"event42" }) utag.link({ "fb_event_name":"view_content" }) Combined Single Event utag.link({ "adobe_event":"event42", "fb_event_name":"view_content" }) This approach can work for your client-side tags as well and will reduce the number of events being triggered on your site/page, helping Tealium run more efficiently. ... View more

Hi Marielle! We recently compiled the following article on Facebook CAPI Best Practices for configuration. Those tips should help, but keep in mind that CAPI is meant to be a fallback in the case that the client-side pixel is not received. To achieve this result, you'll want to ensure that your event feed conditions match those of your client-side tag and how the event is being triggered. For example, if you have a load rule on your Facebook tag to allow for consent and you trigger a "ViewContent" event when "tealium_event" equals "product_view", then your Facebook event feed will need to cover the consent piece AND the event trigger (tealium_event = product_view). This will ensure that both the client-side and server-side events are triggering in parallel and are not dependent on each other (ex: an event ID being present).  If you are seeing the event trigger but the event ID is not present, then please refer to the article linked above on how to configure the client-side tags to allow for the event ID to generate in time for the Tealium Collect tag to send it in the final data payload.  ... View more

Hi John! These items are created with the event object but are not readily accessible to connectors through event attributes (with the exception of the timestamp - we do store a "Last event timestamp" attribute by default). If you need to access these items, they are available through the Data Transformation feature, as you can access the full Event object . You can then set those values to new UDO variables and access them through event attributes in that manner. Once they are stored as event attributes they can be mapped to event connectors or used in AudienceStream attributes. ... View more

We recommend files no larger than 100MB. It is beneficial to break down files that large to increase processing speed as well, otherwise it can take an extended amount of time since the file is so large. I would still try to keep it at around 100K rows or less per file.  ... View more

Below is a list of the errors by number: Error 0: invalidScheme Error 1: commandIdNotFound Error 2: commandNotFound Error 3: remoteCommandsDisabled Error 4: requestNotProperlyFormatted Error 5: invalidFileName Error 6: couldNotConvertData Error 7: couldNotDecodeJSON Error 8: errorLoadingRemoteJSON Error 9: mappingsNotFound Error 10: commandsNotFound Error 11: commandNameNotFound Error 12: noResponse Error 13: invalidResponse Error 14: notModified I would review your JSON file to ensure it is in the proper format. An example of the JSON file can be found here. ... View more

I reviewed the tag template and for custom data to be added, it need to be mapped as follows: custom.my_custom_param where "my_custom_param" is whatever parameter you want to send the data to for Snap Chat. See a screenshot example below: Please give this a try. ... View more

Each server-side profile is its own instance, so there is not a way to copy the keys between profiles. The keys are randomly generated when a datasource is created. With separate server-side profiles, all visitor profiles are also separate, and those cannot be copied between profiles (nor can database tables, as each server-side profile has its own database and store files if those products are in use). You can think of each server-side profile as a bucket, and the data cannot go between buckets, but stays in its own bucket.  In this case, you'll need to use the key generated in the new profile when sending data into the new profile. ... View more

Each collect tag can only be configured for one profile at a time. If you want to send data to multiple server-side profiles, you will need a Tealium Collect tag for each server-side profile that you want to send data to. If it's conditional (sometimes it goes to one profile or another), you could then use extensions to populate the different values. This will still only send to a single server-side profile. ... View more

If your link event is actually triggering and the tag is not firing, I would check the mappings to ensure they are set up as follows: Event Name The mapping should show as "tealium_event" --> global_navigation:global_navigation where the value after the colon is the name of the event in GA4 (the value before the colon is the variable's value that will trigger the event. In this case, when "tealium_event" equals "global_navigation", the GA4 "global_navigation" event will be sent to Google. Event Params The event-specific parameters use the event name first, then the param name second: "_ga4_param1" --> global_navigation.param1 In this case, the value of "_ga4_param1" will be sent to the parameter named "param1" with the "global_navigation" event. You'll want to make sure your param names align with the names configured in GA4 or Google won't know where to put the data. If you need assistance beyond this information, I would suggest submitting a support request through our support portal. ... View more

It's hard to know exactly what is being sent without looking at the configuration, but I would try to ensure that the metrics are being sent over that Google needs for the reports. I was able to find the following article regarding attribution in GA4: https://support.google.com/analytics/answer/10596866?hl=en#zippy=%2Cin-this-article If everything is showing as "Direct", it's possible the referrer is not being updated on page changes and the referrer needs to be mapped to the tag instead of using the one Google pulls from the browser. Also, mapping any UTM parameters might help as well to ensure any campaigns are pulled in by Google.  ... View more

You'll need to write your own event tracking for keyboard events using a JavaScript Code extension. An example would show as follows: jQuery(<<SELECTOR HERE>>).keypress(function(e) {     utag.link({         "tealium_event": "search"     }); });  The extension would need to be scoped to DOM Ready to ensure the element is on the page to attach the event. If any of the events needed aren't available in the dropdown for the JQuery Event Handler extension, you'll need to implement the event in this manner. ... View more

When it comes to load rules, we have two options available when multiple rules are being used - "Match All Rules" or "Match Any Rule", meaning "AND" or "OR" respectively. If you have certain conditions whether the variable is defined or not, I believe the "OR" (Match Any Rule) would be the best approach. You'll then need to craft individual rules that meet each criteria. For example: RULE 1 var1 IS DEFINED AND var1 EQUALS "hi" AND page_name IS DEFINED AND page_name CONTAINS "home" OR var1 is not defined AND page_name IS DEFINED AND page_name CONTAINS "home" RULE 2 consent IS DEFINED AND consent CONTAINS "c0003:1"   Setting these rules to "Match All Rules" would mean that Rule 1 AND Rule 2 must evaluate to TRUE for the tag to fire. Setting these rules to "Match Any Rule" would mean that if Rule 1 is TRUE and Rule 2 is FALSE, the tag will still fire because at least ONE rule was matched.  If this still is not clear, I think it would be best to submit a request to our support team so they can look at your individual use case and advise on how to configure the rules.  ... View more

If you do not allow Tealium to set the "utag_main" cookie using the "nocookie" configuration override, a new value for the visitor ID and session ID will be generated every time. If this is not the case, I would suggest submitting a request to our support team  so that they can look into the issue further. Information that may help the support team would include the device and browser being used, as well as any steps necessary to re-create the issue. ... View more

All first-party cookies are read by the utag.js script and added to the data layer using the "cp." prefix. If your cookie is set before Tealium executes, you should see it show in the data layer as "cp.LILO". You'll still need to add it as a UDO variable in Tealium IQ to be able to use it in mappings. You can go to the data layer tab, click on the blue "Add Variable" button, then enter "LILO" in the variable name box. Please ensure the type is set to "First Party Cookie". Once you have added the variable in the data layer tab, you can use it in your Adobe tag to map to "prop27". You can have multiple variables mapped to the same prop, however, know that mappings are set from top to bottom, so if you have two, the bottom value is what will be used. If you want to use the cookie as a fallback, you can use a Set Data Values extension to set "user_hashedID" to the cookie value if the variable "user_hashedID" is not defined. You would then map "user_hashedID" to "prop27" in the Adobe tag. I hope this helps. ... View more