The Zeotap Collect tag is configured directly in the GTM UI. Settings are grouped into five sections.
Initialisation Options
| Field | Description |
|---|
| Write Key | Required. From your GTM Source’s IMPLEMENTATION DETAILS tab. Without it, no events are recorded. |
| User Country | ISO Alpha 3 country code. Determines storage region. Defaults to IP-derived country when omitted. |
| Event Key | Key against which event names are stored in the dataLayer. Defaults to GTM’s event key. Override only if you use a custom key. |
| Data Persistence | Select Persist data in cookie storage for multi-domain sites — keeps identifiers across domain navigation. |
| Consent Method | See Consent below. |
Consent Method
The tag supports three consent strategies. Pick one in the initialisation options.
Default Opt-in
Check TCF CMP
Custom Consent
Sets optOut: false. Fire the tag only for users you’ve already obtained consent from (through your own backend, API, etc.). The Zeotap tag itself records events for every fire.Use Additional Consent Settings to send the TC string or brand consent.No setConsent integration needed.\Cookie Sync
Cookie Sync with Zeotap’s integrated channel partners is enabled by default for the extension. To disable or restrict, contact your Zeotap representative. Sets useConsent: true and checkForCMP: true. The tag JS reads the TCF API on the page and queries the publisher’s consent on each load before firing events.Configure Purposes for tracking of events — a list of TCF purpose IDs. Defaults to [1, 3, 4] (modify as needed via the dropdown).Use Additional Consent Settings to send custom brand consent.
Sets useConsent: true and checkForCMP: false. You supply consent explicitly through a dataLayer event.In the SDK Consent Signals section:
- Event name — the
dataLayer event that fires when custom consent is set.
- Other Variables —
dataLayer variables for Track, Identify, and Cookie Sync signal values.
Use Additional Consent Settings to send the TC string or brand consent. Tracking Page Views and Events
| Field | Description |
|---|
| Page View Tracking Event Name | Defaults to gtm.js. Override if you use a different event for page views. |
| Event Tracking | Regex that matches event names you want to track. Default .* tracks everything. Use a specific event name to track only that event. |
| Special Events | Add event names that should be tracked even if they don’t match the regex. |
| Pre Defined Properties | Properties to attach or override on every tracked event. Use variables or static values. |
| PII to be excluded | dataLayer keys to strip from event properties before sending. Useful for raw PII like email that should not be forwarded as event data. |
country and city are blacklisted for ingestion — Zeotap derives these from the IP. See blacklisted fields.Login and Identities Settings
| Field | Description |
|---|
| Login Event | dataLayer event fired on user login. |
| Are your identities hashed? | Check this if you supply pre-hashed PII. Add rows per hash algorithm (sha256 / sha1 / md5) with the corresponding dataLayer variable for each. |
| Is hashing of raw identities required? | Check this to let the tag hash raw PII. Then map raw email, cellno (with country code), and loginid to dataLayer variables. |
| Create First Party ID+ cookie on user login | Enables ID+ calls. Only relevant for Publishers using Zeotap ID+. |
| Organisation partner ID | Provided by Zeotap when ID+ is enabled. Required for ID+ activation. |
| User Logout | dataLayer event for logout. Unsets email, phone, login ID from subsequent events. |
| User Attributes | dataLayer variables containing user-related info. Passed in the setUserProperties call. |
Google Analytics Configuration
Forward GA Client ID / User ID for cross-platform ID stitching (e.g. Google Optimize 360).
| Field | Description |
|---|
| Pick Google Analytics client ID | Enable to capture GA Client ID. |
| GA Client ID Cookie Prefix | If your GA cookie has a brand prefix (e.g. client_ga instead of _ga), enter the prefix here. |
| Use only for Login Event | If checked, the GA User ID is attached only to post-login events. |
Advanced Settings
| Field | Description |
|---|
| Tag firing | Set to Once per event — only supported value at this time. Leave other Advanced Settings fields untouched. |
A complete config
For a typical e-commerce site using TCF CMP:
| Section | Field | Value |
|---|
| Initialisation | Write Key | (from Source) |
| Initialisation | User Country | DEU |
| Initialisation | Consent Method | Check TCF CMP |
| Initialisation | Purposes for tracking | [1, 3, 4] |
| Tracking | Event Tracking | .* |
| Tracking | Pre Defined Properties | (vars from dataLayer) |
| Identities | Login Event | login |
| Identities | Is hashing required? | ✓ (raw email + phone) |
| GA | Pick GA Client ID | ✓ |
| Advanced | Tag firing | Once per event |
Last modified on June 22, 2026
