In addition to the default publish environments, Dev, QA, and Prod, custom publish environments can be created. Learn how to enable this feature, create custom environments, and publish to them.
In this article:
The environments that you publish to 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:
If you have the need for more than three environments, you can create custom environments to give you more options. The name of a custom publish environment is lower-cased to create the environment portion of the URL to utag.js. For example, if you create a custom publish environment named "Stage", the URL path to the utag.js file in that environment would be: /utag/account/profile/stage/utag.js
Before you can create to a custom environment, first you must enable the feature.
To enable custom publish environments:
Once the feature is enabled, you can create new environments.
To create a custom publish environment:
You can delete a custom environment by clicking Delete in the upper right corner of the Code Center dialog window. You will receive a prompt confirming deletion.
Once you have created a custom publish environment, you can now publish to it. Permission to publish to custom environments is granted via the Publish Dev.
To publish to a custom environment: