Tealium Learning Center

I do not see this error when I visit that site.  However, from the screenshot that you included, it looks like the source of your error is in the custom JavaScript code in one of your extensions.  If you log in to TiQ, you can access that extension in the following location: Account: integratedmaster profile: lib-cookie Extension: Sitemorse preloader - Button bindings (UID 21) This code appears to be related to your OneTrust integration.  Is it possible that you have something running locally that is preventing cookies from being handled appropriately? ... View more

Yes, that approach would definitely work.  Just make sure to set an appropriate scope to your JS extension (e.g. pre-loader), so that the function is available before you call it in the Set Data Value extension. Another option would be to set the variable directly in your JS exention.  (e.g. instead of returning the value from a function, you would just set b['ga_hit_timestamp'] or utag.data['ga_hit_timestamp'] at the end of your JS code block).  There are pros and cons to either approach, though frankly, I prefer your approach overall (using the JS code combined with the Set Data Value extension). And since you are writing JS extensions, this article may be a useful knowing how to reference the data object (utag.data, b, etc.) at various points:  https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/Difference-between-the-b-utag-data-and-u-data-objects-in-the/m-p/16835#M5578 And lastly, remember that whenver you make changes in your JS extension, you must hit the "approved for publish" button in the extension, along with publishing the profile changes in TiQ in order for the JS extension code to begin running on your site.  This little step trips me up more often that I should admit. Cheers! ... View more

Most of our tags are designed to fire once per view/link. There are a few tags that can be fired multiple times per utag.view call, but those are the exception, and that information should be specified in the TLC documentation for those tags.  So in general, if you want a tag to fire twice, the easiest way is to make an additional utag.link or utag.view call, either coded onto your page or in a JavaScript extension.   To avoid unnecessary double-firing, it is possible to fire a view/link call that only triggers a certain tag(s).  To do this, you simply include the UID for the desired tag(s) in the utag.view() call.  The documentation for this process can be found here: https://docs.tealium.com/platforms/javascript/track/. Including the uid_array parameter will ensure that the specified tag(s) - and only those tags - are fired during that call. In your case, you could use the default utag.view to trigger the first round of events, and then use this method to specifically call the tags that need to fire an additional event.  That is probably the easiest solution for this type of scenario.   (Please note that this will bypass any load rules on the tag, so you will need to be sure of your logic if you hardcode the UID's into the view/link call in this way.  Also note that you will need to ensure any required data is included as the first parameter in the view/link call, as the page data will not be passed by default.) ... View more