“To understand the best is to work on its implementation” - Jean-Marie Guyau

On this note, we are here to clearly guide you all on how to implement Zync Container tags within your websites.

The Zeta Global Container Tag bundle, which should be triggered to fire upon the DOM ready state, provides compatibility with the marketer's chosen TCF2.0 compliant Consent Management Platform (CMP) and is compatible with all the enterprise tag management systems (TMS), either via a specific Zeta Global template or a custom HTML template. However, if deploying directly within a content management system (CMS), the marketer should implement the tags just before the closing </body> tag in the relevant HTML documents.  

  • The Zeta Global Container Tag bundle should not be piggybacked by a third-party technology vendor platform that utilizes iframes to deliver piggybacked tags, as owing to its nature, the iframe blocks script access to the parent document.  

  • The tag code samples provided here are for the purpose of illustrating the implementation process only; they are not to be implemented on the marketer's site. You can find unique marketer-specific Zeta Global Container tags in the .txt file within the zip archive that accompanied your onboarding.  

Refer to the Common Implementation Methods section for screenshots of correct implementations in various systems.  

Please alert your Zeta Global Account Manager once tagging implementation has been confirmed. If a pre-production sandbox environment is available, please provide it along with any relevant credentials. If tags are on production pages, please confirm from which webpage URLs, the tags should be reviewed. Zeta will view the web pages using a web debugger and check back-end platforms and databases for activity in order to verify successful implementation.  

Implementing via Tag Management Systems 

You may already have a tag management system integrated throughout your website. These are some instructions on how to add the Zeta Tag Bundle to various common systems:

  • Google Tag Manager 

  • Adobe Launch 

We would recommend not using frequency capping or conditional firing rules as they may provide an incomplete understanding of your audience. 

Google Tag Manager

1. Add a new Custom HTML tag.

2. Paste the Zeta Global Container tag within the HTML input field.

3. Select the Support document.write checkbox.

4. Replace the cachebuster placeholder with {{Random Number}}

  • See Additional Notes below for the steps on how to configure {{Random Number}} based on the Google Tag Manager version

cachebuster not applicable to EU implementation

5. (If applicable) Replace additional parameter value placeholders with the appropriate GTM Variable:

  • GTM Variables will be of the format: {{Variable Name}}

6. Select appropriate Firing Triggers:

  • For Universal Tag: Trigger should include all website pages except the conversion page(s)  

  • For Conversion Tag: Trigger should include website conversion page(s) or event(s)

Additional Notes about Google Tag Manager: 

  • Use the chart below to confirm the {{Random Number}} cachebust macro is set up correctly.

Google Tag Manager Version

Access URL

To Enable {{Random Number}}



Create a new user-defined variable (macro) of type Random Number.



Activate the Random Number Built-in Variable.

  • Ensure firing rules (called Triggers) are correctly set up. If incorrectly set up, this can lead to unexpected conditional firing. 

  • Confirm that the most recent changes have been published to the live container. 

Adobe Launch

1. Select the appropriate Rule that corresponds to the expected implementation methodology  

  • For Universal Tag: Rule should include all website pages except the conversion page(s)  

  • For Conversion Tag: Rule should include website conversion page(s) or event(s)  

2. Within the Rule, add a new Action

3. Select Extension: Core, Action Type: Custom Code, Language: HTML  

4. Open the Editor  

5. Paste the Zeta Global Container Tag  

6. (If applicable) Replace parameter value placeholders with the appropriate Adobe Data Element

  • Adobe Launch Data Elements will be of the format: _satellite.getVar('Data Element Name')

Implementing via Direct Placement in HTML

When a tag management system is not available, the tags can be placed directly into the HTML. Below are the instructions on where to place the tags:

1. Implement within the </body> element in the HTML on relevant page(s)

2. (If applicable) Replace parameter value placeholders with the appropriate code snippet or variable

Implementation Tips

Be careful with Duplicate / Multi-pixel calls 

In order to facilitate the correct setup, page view pixels should only be placed once (1x) on the pages they were designed to be placed on.

For example, a coupon download pixel should only be placed once on the coupon download page, a home page pixel should be placed once on the home page, and a landing page pixel should be placed once on the landing page, etc.

Most importantly, the conversion pixel should only be placed once (1x) on the intended user conversion action and nowhere else.  

Debugging Tools 

Google Chrome Dev Tools is the recommended tool to view pixel fires on a page within its Network tab and comes included with the Google Chrome browser.