Update endpoint configurations

After you have configured First-Party Domains and validation has been completed, you need to update your endpoint configurations to use First-Party Domains with Tealium iQ Tag Management and Tealium Collect.

Tag management

Tealium’s environment switcher supports First-Party Domains. However, the environment switcher Basic option does not work with First-Party Domains. Use the URL redirect option on the Advanced tab. For more information, see Tealium Tools: Environment Switcher.

To use your first-party domain with Tealium iQ Tag Management you must also make the following changes:

• Update the Universal Tag (utag.js) code snippet wherever it is installed.
• Set the publishing URLs.
• Edit the template for utag.js to adjust the location of utag.v.js.

Update universal tag loading script

To update the Universal Tag code snippet:

1. In the client-side user menu, under MANAGE CLIENT-SIDE, select Code Center.
2. Under Choose Domain, select your first-party domain.
   

   

The example code snippet is updated to use your first-party domain.

The new URL only uses the profile name and environment in the path. The account name and /utag/ portions are omitted.

The URL to the Universal Tag on a first-party domain is:

https://**sub.your_domain.com**/PROFILE/ENV/utag.js

For example, the code snippet for tags.tealiumecommerce.com would be:

<!-- Loading script asynchronously -->
<script type="text/javascript">
    (function(a,b,c,d){
    a='**https://tags.tealiumecommerce.com/ecomm/prod/utag.js**';
    b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true;
    a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a);
    })();
</script>

Update publishing URLs

If you have multiple first-party domains configured for a profile, see Update publishing URLs when a profile has multiple first-party domain for information about updating the publishing URLs.

The publishing URLs determine where to load the additional utag.#.js files for each default environment. If the publishing URLs are not updated, then the vendor tag files loaded after utag.js will not originate from your domain.

Follow these steps to set the publishing URLs:

1. In the client-side user menu, under MANAGE CLIENT-SIDE, select Configure Publish Settings.
2. Scroll down to Publishing URLs, then enter a URL for each environment that uses your first-party domain. For example, tags.example.com and collect.example.com.

   

   
   Publish Dev URL: //sub.your_domain.com/your_profile/dev/
   Publish QA URL: //sub.your_domain.com/your_profile/qa/
   Publish Prod URL: //sub.your_domain.com/your_profile/prod/
3. Click Save.
4. Save and publish.

Update publishing URLs when a profile has multiple first-party domains

If you have multiple first-party domains configured for a profile, you will not be able to update the publishing URLs from the client-side menu.

You need to add a script similar to the following to update the publishing URLs, replacing the example path with the appropriate path for the page (it will match the utag.js inclusion path, which can be updated at the same time). This script must be added before the script that specifies the URL for utag.js.

<script>
window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}
window.utag_cfg_ovrd.path = '//tags.example.com/main/prod'
</script>

For more information, see Settings.

Update Tealium Collect endpoint

To use your first-party domain with Tealium EventStream API Hub or Tealium AudienceStream CDP, you need to update the data collection URL in your installation of Tealium Collect. For websites, this requires setting the Tealium Collect Endpoint field for the Tealium Collect tag. To use the visitor service, you also need to provide a Visitor Service Override.

To update the Tealium Collect tag:

1. Navigate to Tags and expand the Tealium Collect tag.
2. In the Tealium Collect Endpoint field, enter your first-party domain endpoint.
   For example: sub.your_domain.com/your_account/your_profile/2/i.gif
3. In the Visitor Service Override field, enter the visitor service URL. Omit the protocol and path. For example: your-visitor-service.example.com
4. Click Apply.