Custom publish environments

How it works

If you need more than the three default environments, create a custom environment. Custom environments are useful for the following scenarios:

• Creating a sandbox or local environment for developers to make changes over a longer period of time without impacting the regular workflow.
• Creating a staging environment to match your organization’s internal testing environments.
• Creating an alternative production environment so that changes can be released in phases to smaller subsets of customers to minimize any potential negative impacts.

The environments to which you publish a profile correspond to the URL of the Universal Tag (utag.js) that you load on your site. The default environments correspond to the following URL paths:

• Dev - /utag/account/profile/dev/utag.js
• QA - /utag/account/profile/qa/utag.js
• Prod - /utag/account/profile/prod/utag.js

Custom environment names are case-sensitive in the URL for utag.js. For example, if you create a custom environment named Preview, the URL path to the utag.js file in that environment would be: /utag/ACCOUNT/PROFILE/Preview/utag.js

To test custom publish environments, you can use Web Companion or the Environment Switcher Tealium Tool.

Enabling custom publish environments

Before you can create a custom environment, you must enable the feature.

To enable custom publish environments:

1. In the admin menu, click Configure Publish Settings. The Publish Configuration dialog appears.
2. In the Implementation section, set the Custom Publish Environments toggle to On.
3. Click Save.

The feature is now enabled.

For information about how to manage custom environments, see Manage custom publish environments.

When you create a custom publish environment, it is added to the Publish Locations for every tag, extension, and event listener on the profile.

Publish to a custom environment

To publish to a custom environment:

1. Click Save/Publish.
2. In the Publish To section click the new option, Custom. A Custom Environment drop-down will appear above the custom publish history area.
   

   

3. If you have more than one custom publish environment, you must select the environment you want to publish to from the drop-down list.
   • You can publish to only one custom environment at a time. To publish to multiple environments, repeat the publishing process for each one.
4. Click Publish.