setEventProperties, setUserIdentities, setConsent, etc.). This page maps GTM template options to those underlying methods.
Template fields → SDK methods
| GTM template field | SDK method invoked |
|---|---|
Tag fires with Pre Defined Properties and event matched | setEventProperties(eventName, eventProperties) |
| Login Event fires with mapped identity variables | setUserIdentities({ email, cellno, loginid, ... }) |
| User Logout event fires | unsetUserIdentities() |
| User Attributes mapped variables on any event | setUserProperties({ ... }) |
| Custom Consent event fires | setConsent({ track, cookieSync, identify, brandConsent }) |
| Page View event fires | setPageProperties({ ... }) |
Reserved identity keys
The tag understands these reserved keys when mapping identity variables. Anything outside this list is treated as a custom identity and forwarded as-is. Raw PII (withIs hashing of raw identities required? checked):
emailcellno(with country code, e.g.49 1234567890)loginidfpuid
Are your identities hashed? checked, map a row per algorithm):
email_{sha256,sha1,md5}_{lowercase,uppercase}cellno_without_country_code_{sha256,sha1,md5}cellno_with_country_code_{sha256,sha1,md5}loginid_{sha256,sha1,md5}_{lowercase,uppercase}
crmID, ECID, visitorID, or any other first-party identifier. Hashing flags don’t apply.
Consent signal mapping
When Consent Method = Custom Consent, map thesedataLayer variables in SDK Consent Signals:
| Signal | Underlying Web JS field | Description |
|---|---|---|
| Track | setConsent({ track: ... }) | Allow event tracking |
| Identify | setConsent({ identify: ... }) | Allow identification / ID+ |
| Cookie Sync | setConsent({ cookieSync: ... }) | Allow partner cookie sync |
TCF purpose IDs
Default purposes for tracking:[1, 3, 4].
See the TCF policies appendix for the full list.
Auto-captured data
The Zeotap Collect Tag automatically appends contextual data to every event payload, just like the standalone Web JS SDK:- Page URL, path, referrer
- IP-derived country (overridden by
User Countryif set) - User-Agent-derived device OS, type, browser
zi(SDK-generated user ID)gdpr_consentstring (when TCF is in use)- GA Client ID / User ID (when GA capture is enabled)