This article describes how to configure publish settings for a user.
In this article:
Use the following steps to configure your publish settings:
Some settings require you to perform a publish to enable their functionality. See the following section for more information on each of the publish settings.
The General Publishing configurations are grouped depending on which aspect of your implementation they affect. The following sections provide descriptions of what each publish configuration does.
These configurations allow you to fine-tune how this profile's implementation is saved and published.
This setting is not longer supported. If this was enabled in your profile, you will no longer receive alerts emails.
These publish configurations affect the overall performance of the Universal Tag (utag.js) on your site.
These settings affect how you implement the Universal Tag (utag.js).
utag_maincookie. By default, Tealium automatically detects the domain of the page, so we recommend that you leave this field empty. By doing so, Tealium automatically detects the domain. However, you can set this value to the domain of your site. If you use multiple subdomains, you should set this to the root domain (ex. tealium.com instead of www.tealium.com)
utag_datavariables to send on every tracking call.
This setting is also required for Tealium's Flicker Free Adobe Test & Target solution.
For profiles created before Nov. 10, 2015, the default is ‘Off’.
Enabling this feature allows your website to set a cookie with any arbitrary value, which could expose your system to code injections. This feature is offered as a convenience for those who cannot use the Google Chrome browser. If you can use Chrome, Tealium recommends using the Tealium Tools Environment Switcher as a best practice.
These configurations allow you to specify a publication location other than Tealium's default multi-CDN infrastructure. If you want to publish your profiles to a non-standard location, e.g. your prod environment is not specified as "prod", then enter the URL in the appropriate field. You may do this for each of the three environments: Dev, QA, and Prod.
These configurations are deprecated, but remain to support legacy deployments and should not be used for newer implementations (utag.js versions 4.26 and later).
In this tab, you can activate mobile library support by clicking Activate Mobile Library. Learn more about Creating a Mobile Profile.