Tealium Learning Center

@amitkanakrai Check out: https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/Self-Hosting-the-utag-js-Files/ta-p/10135     "On the General Publishing tab, under the Publishing URLs section, enter the domain and full path to your self-hosted files, one for each environment (omit the actual file name) eg. //example.com/custom/path/prod/" Let us know if that helps. Brian ... View more

@Michael_Kim_shc Out of the box, all Tags loading via Tealium will fire at DOM Ready. You can change this setting to DOM Complete, but you cannot have both DOM Ready and DOM Complete, you gotta pick one. You will want a JavaScript Extension scoped to PreLoader with the following code:  window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; utag_cfg_ovrd.dom_complete = true; Now that said, there is one other setting called the wait flag which is set on a tag by tag basis.  For each tag where the wait flag is no, that tag will load as soon as possible and will not wait for DOM state to change.  You can read more about the override flags here: https://community.tealiumiq.com/t5/Browser-utag-js/utag-Config-Overrides/ta-p/14048 You can read more about the wait flag in the Advance Settings section of: https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/Tags/ta-p/5016#toc-hId--1470671774   ... View more

@davidsbridal-pm Good question, I will bring this up with our integrations team as it should be something you can pick in the mappings toolbox.  However you do not need to wait on them, you can just type in the mapping.  So pick something in your data layer and map it to page_category.   ... View more

@redfuel318 One option is to persist in a cookie.   https://community.tealiumiq.com/t5/Tealium-iQ/Persist-Data-Value-Extension/ta-p/13623   Brian ... View more

@andrea_kebalo Make sure that what whatever you have in the "Join:" field and also the "and:" field of the Join Data Values extension is also in the Condition.   For the condition, you will want to make sure both of the values are "is populated"   Brian ... View more

@rohitsane Only the name.   If you want to lowercase the values we have an extension for that: https://community.tealiumiq.com/t5/Tealium-iQ/Lower-Casing-Extension/ta-p/5634   Brian ... View more

@rohitsane Sounds like you need to turn on lower case query string parameters.  By default Tealium will not lowercase the querystrings:   However you can override this setting and get the results you are looking for:     To override, you need a JavaScript Extension scoped to PreLoader with the following code:   window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; window.utag_cfg_ovrd.lowerqp = true;     Now you just map the querystings to any evar or sprop like you normally would in tag mappings.   The setup I am referring to does not use Adobe's code for getting the query string parameters, it use's Tealium.   Does that answer you question? ... View more

@Michael_Kim_shc Yes, but for this custom of a solution, you will have to write JavaScript.   There is an extension called Pathname Tokenizer which might get you started. Then use the JavaScript Extension and make up your own variable.     b["my_url"] = b["dom.url"]; if(check_something){   b["my_url"] = b["my_url"] + "/" + b["_pathname1"]; }else{   b["my_url"] = b["my_url"] + "thing2"; } If you scope these extensions to your tag then they will be limited to the tag.     Also you might be interested in: http://tealium.com/services/education/     ... View more

@Diconium-RO11 Great question. This is possible with a JavaScript extension.  However before going that far, I am wondering if you can use one of the built in Data Sources or join a couple of Data Sources together to get what you want.   For example find the section called "DOM ELEMENTS AS DATA SOURCES" in:  https://community.tealiumiq.com/t5/Tealium-iQ/Data-Source-Types/ta-p/10645 These are bulit in data sources you can pass to vendors like siteCatalyst.   So lets say you have https://www.example.com/some_path/index.php?foo=bar&biz=baz "dom.pathname" will be " /some_path/index.php " "dom.query_string" will be " foo=bar&biz=baz "   Knowing this, you can utalize the Join Data Values Extension make a destination of sc_url join pathname and querystring with the delemiter ? Now sc_url will be " /some_path/index.php? foo=bar&biz=baz " (no RegEx required :)   And then map the sc_url to a prop in the tag mappings.   Let us know if this works for you.   Brian     ... View more

@richard_udovich and @jan_van_damme If you scope to "All Tags" or "DOM Ready" then utag will be available.  The only scope that will not have utag is "Pre Loader".  If you need this extension to run first, then you can move it up higher in the list of extensions (you can drag and drop the extensions to change the execution order).    Also you can Scope to "All Tags" - "Before Load Rules" which run before the default "After Load Rules" Hope this helps.   If not, reach out by opening a support case and one of our engineers can work with you on your specific website: https://community.tealiumiq.com/t5/custom/page/page-id/support-contact-form ... View more

@jan_van_damme Great question and I am sure there are many ways to approace the solution.  The most common way would be the following:   if(typeof utag.runonce['my_code_init'] === 'undefined'){ utag.runonce['my_code_init'] = true; // run the rest of your code here. // your code will only run once because of the if block }   ... View more

@Srinivasan  Sorry there is not enough information here for me to provide a full custom solution.  Please open a support ticket and an engineer can work with you on your specific use case.   https://community.tealiumiq.com/t5/Feedback-Discussion/Open-Support-Case-from-Community/m-p/11550#M925 ... View more

Please see: https://community.tealiumiq.com/t5/Tealium-iQ/Publish-Workflow-Control/m-p/2213/highlight/true#M3935   "The Publish Workflow Control feature divides users into two groups: submitters and approvers. The submitters can only make changes and publish to the Dev and QA environments, but they cannot publish to Prod. Instead, submitters send a request to approvers to review and publish their proposed changes. Publishing to Prod requires an approver to publish the submitted version."   The system was only designed to limit the publishes to prod, @stefano75. ... View more

@tglaittli sounds like something that should be part of the data layer as part of the next link or view event.  I would reach out to your Deployment Team.  These types of questions are pretty common for a Tealium Deployment and differ on a per web applicaiton basis.  ... View more

@evelin utag.js should always remain async.  However if you have a tag or two that require sync, you can also have utag.sync.js run on your website.  This can be enabled under the Configure and Publish settings.  The setting is called " Generate utag.sync.js File "   If you are new to Tealium, I would encourage you to bring this up as part of your deployment so one of our deployment engineers can go over the pros and cons of Tealium's sync and async solutions.  Please make sure you understand all of the risks with using utag.sync.js before adding it to your website.   ... View more

@tglaittli As someone that is new to Tealium, I would encourage you to leverage your Tealium Deployment team.  You can point them at this post and they will be able to add this as part of your initial deployment.  The mappings are pretty much drag and drop and the code sample provided can hopefully be copy/pasted into a DOM Ready Extension.  ... View more

After further testing the option I purposed earlier does not give the desired results. I am pulling the post down.  See Adrian's comments below. ... View more