Implement the Google Tag Manager Source

• Tags – Snippets of JavaScript or tracking pixels
• Triggers – This tells GTM when or how to fire a tag
• Variables – Additional information GTM may need for the tag and trigger to work

​

Before you Begin

​

Overview of Zeotap Collect Tag Template

​

Steps to Configure Zeotap Collect Tag in GTM

1. Add/Import the Zeotap Collect Tag Template
2. Add the Tag
3. Configure the Tag a. Initialisation Options b. Tracking page views and events c. Login and Identities Setting d. Google Analytics Configuration e. Advanced Settings
4. Set up the Trigger
5. Validate the Configured Collect Tag

​

Step 1 - Add/Import the Zeotap Collect Tag Template

​

Method 1

1

Log into your GTM account and click Templates from the left menu.

2

Under Tag Templates, click the Search Gallery on the top-right corner.

3

Search and choose Zeotap Collect Tag Template from the list.

4

Click Add to your workspace to add the Tag Template for further usage.

​

Method 2

1

Check with your Zeotap Product Operations Manager for the template file. It is shared as a .tpl file.

2

Log into your GTM account and click Templates from the left menu.

3

Under Tag Templates, click New on the top-right corner.

4

In the top-right corner, click the vertical ellipses and select Import.

5

Select the .tpl file shared in step 1 above.

6

Name the template as Zeotap Collect Tag and save it for further usage.

​

Step 2 - Add the Tag

1

Log into your GTM account and click Tags from the left menu.

2

Click New and name the tag descriptively. For example, Zeotap Collect.

3

Click Tag Configuration and search for Zeotap Collect Tag Template. The Tag is listed under the Custom tab.

4

Click Zeotap Collect Tag Template. To configure the tag, follow the steps mentioned under Configure the Tag.

​

Step 3 - Configure the Tag

• Initialisation Options
• Tracking page views and events
• Login and identities setting
• Google Analytics Configurations
• Advanced Settings

​

Initialisation Options

• Write Key - When you create a GTM-based source in your Zeotap CDP account, a write key is provided in the source details. This is a mandatory field for recording events.
• User Country - This is the ISO Alpha 3 country code that is used to determine the region for storage. If this country code is not sent, then the Zeotap servers use the IP Address to determine the same. Therefore, use this country code if your account is set up only for specific regions.
• Event Key - This the key against which event names are stored in the dataLayer object. You can choose not to fill this if you are using the GTM’s default key - event.
• Data Persistence - In case of multi-domain websites, the identifiers are reset once the user navigates to a webpage with a different domain name. In such scenarios, you can click the Persist data in cookie storage check box, which continues to store their identifiers in the Cookie storage, irrespective of the domain name of the web page they browse through.
• Consent Method* -The Collect SDK has three options that can be used to determine consent actions. . a. Default Opt-in - This option sets the optOut option to false and is used to record events. Choose this option to fire the tag only for the consented users. The consent communication happens through other methods such as API integration, file upload and so on. You can also use the options available under Additional Consent Settings to send TC string and custom brand consent.
  
  b. Check TCF CMP– This option sets the useConsent and checkForCMP options to true. The JS automatically checks for the presence of the cmp.js script and the __cmp variable in the global scope. The JS also queries the TCF API to fetch the latest Publisher consent before recording the events on each JS load. Ensure that you configure the parameter Purposes for tracking of events, while using the GDPR consent module. This option is used to pass a list of purpose IDs, based on which you can manage the consent for tracking. By default, the three options shown in the image below are selected. However, you can modify them based on your requirement. You can also use the option available under Additional Consent Settings to send custom brand consent.
  
  c. Custom Consent – To configure custom consent, select Custom Consent as the consent method under the Initialization Options. Then, specify the following details in the SDK Consent Signals section:
  NOTE:You can also use the option available under Additional Consent Settings to send TC string and custom brand consent.
  • Event name: Choose the dataLayer event that is fired when custom consent is set.
  • Other Variables: Choose the dataLayer variables for setting the values of Track, Identify and Cookie Sync signals.
  

​

Tracking Page Views and Events

• Page View Tracking Event Name*–* By default, we track page view for the gtm.js event name. When using some other event name, ensure to update that event name in the input for overriding.
• Event Tracking – Enter a regex pattern that matches all the event names you want to track. If you want to track just a single event, then just enter that event name. By default, we use the .* pattern to identify the events.
• Special Events – If you want to track event names apart from the regex provided, then add all such events here.
• Pre Defined Properties – Input the properties that you want to attach or override. You can either define the values from your variables or provide static values for them.
• PII to be excluded – Enter all the PII and user-related fields in the dataLayer that need to be from in the event properties. For example, email is pushed into the dataLayer in the raw form. This option is also used to exclude other non-essential keys that need not be recorded.

​

Login and Identities Settings

• Login Event – Choose the dataLayer event that is fired on user login.
• Are your identities hashed? – Based on whether you want your identities to be hashed or not, perform one of the following actions:
  • If your identities are hashed – Select this checkbox and make the following selections for the identities:
    • Hashed Email– Select the Capture hashed email checkbox and then proceed to add a row for the hash algorithm. Click Add Row and then choose the appropriate Hash Algorithm and its corresponding Hashed Email Variable from the drop-down menus. You can add more rows as per your requirement.
    • Hashed Cellphone with country code – Select the Capture hashed cellphone number with country code checkbox and then proceed to add a row for the hash algorithm. Click Add Row and then choose the appropriate Hash Algorithm and its corresponding Hashed Cellphone Number Variable from the drop-down menus. You can add more rows as per your requirement.
    • Hashed Loginid – Select the Capture hashed Loginid checkbox and then proceed to add a row for the hash algorithm. Click Add Row and then choose the appropriate Hash Algorithm and its corresponding Hashed Loginid Variable from the drop-down menus. You can add more rows as per your requirement.
  • If your identities are not hashed – Then do not select this checkbox and proceed to the next option.
• Is hashing of raw identities required?– Based on whether you want to hash the raw identities or not, perform one of the following actions:
  • If hashing of the raw identities is required – Select this checkbox and make the following selections for the identities:
    • Raw Email– Select the Capture Email checkbox and then choose the appropriate Email Variable from the drop-down menu.
    • Raw Cellphone with country code– Select the Capture cellphone number with country code checkbox and then choose the appropriate Cell number variable from the drop-down menu.
    • Raw Loginid– Select the Capture Loginid checkbox and then choose the appropriate Loginid Variable from the drop-down menu.
      
  • If hashing of the raw identities is not required – Then do not select this checkbox and proceed to the next option.
    Note:To know about the hashing guidelines for email and cell phone numbers, refer here.
• Create First Party ID+ cookie on user login – If you are a Publisher who is using Zeotap’s ID+ services, then ensure to select this checkbox to activate the ID+ calls.
• Organisation partner ID – This ID is provided by Zeotap after enabling ID+ for your organisation. Ensure that the ID is properly added.
• User Logout – Specify the dataLayer event that captures the user logout. The same event is used to unset the email address, phone number or loginid from the subsequent events.
• User Attributes – Specify the dataLayer variables that contain user-related information. The same variable is passed in the setUserProperties call.
  

​

Google Analytics Configuration

• Pick Google Analytics client ID – Select this checkbox if you want the Zeotap tag to pick the Google Analytics client ID that is used for user identification.
  • GA Client ID Cookie Prefix – If your GA cookie is configured with a cookie prefix, you can add the same here. For example, a typical GA cookie that was named _ga, may be configured with a brand name prefix User ID variable in your GA settings, you can configure the corresponding cookie name here.
• Use only for Login Event – If this checkbox is selected, then the GA User ID is attached only for the post-login events.

​

Advanced Settings

​

Step 4 - Set up the Trigger

• If you want to fire the tag only for tracking page views, then use the All Pages built-in trigger.
• If you want to fire the tag to capture all the events, then use the All Events trigger.

​

Method 1

1

Go to the Trigger Configuration section from your left menu.

2

Click New to add a trigger.

3

Provide a descriptive name for the Trigger.

4

Click anywhere on the Trigger Configuration block. This will open up the Choose trigger type slider window on the screen.

5

Under Other, choose Custom Event as the Trigger Type.

6

Type ‘Login event’ as the event name.

7

Select the Use regex matching checkbox to add your own regex, if your events follow a specific naming convention. Type ^(?!gtm\.load)(?!gtm\.dom).* if you want to set this regex for all the events.

Note:This regex sets the trigger for all the events except GTM’s internal events, gtm.load and gtm.dom.

8

Select the All Custom Events radio button. Note that the trigger is set for the login event only.

9

Click Save.

10

In the Tag addition, add this as the trigger for the Zeotap Collect tag. This means, our JS will fire an event collection call for each event on the website.

​

Method 2

​

Step 5 - Validate the Configured Collect Tag