The Zeotap Collect Extension is configured directly in your Adobe Experience Platform tag property. Settings live on the extension configuration screen (Extensions → Zeotap Collect → Configure).
Core options
| Field | Description |
|---|
| Write Key | Required. Auto-generated when you create an Adobe Tag Extension Source in the Zeotap CDP. |
| Country Code | ISO Alpha 3 country code attached to every request as user.user_country. Determines storage region. Defaults to IP-derived country when omitted. |
Consent Method
The extension supports three consent strategies. Pick one in the configuration. You can send Brand Consent under any method.
Default Opt-in
GDPR
Custom
The extension records every event without checking external consent. Use this when you’re firing the Zeotap Action only for users you’ve already consented elsewhere (e.g. through your own backend).
- The
setConsent string (track, cookieSync, identify fields) is ignored under this mode.
- When a TCF API is available, the TC string can still be sent.
- To send brand consent, use Rules → Actions → Extension: Zeotap Collect → Action Type: Set Custom Consent.
Automatically reads the TCF 2.0 CMP on the page. The extension queries the TCF API and fetches the publisher’s consent before recording events.Parameters:
- Purposes for track — list of TCF purpose IDs that gate tracking. Defaults to
[1, 3, 4]. Modify via the dropdown.
- Check for Zeotap vendor consent — when checked, the extension verifies the Zeotap vendor in
tcdata before capturing events. Default unchecked.
- When a TCF API is available, the TC string is sent.
- To send brand consent, use Rules → Actions → Extension: Zeotap Collect → Action Type: Set Custom Consent.
Use this when you have your own custom consent flow and don’t rely on TCF.
- You must implement the Set Custom Consent Action in a Rule that fires when the user makes a consent choice. The Action accepts
track, cookieSync, and identify flags.
- When a TCF API is available, the TC string can still be sent.
- Brand consent flows through the same Set Custom Consent action.
PII Hashing Configurations
Pick how PII (email, cellphone, login ID) should be sent.
| Option | Behavior |
|---|
| PIIs are hashed by the customer | You send pre-hashed PII keys (email_sha256_lowercase, etc.) in Sync User Identities. |
| PIIs are raw and must be hashed by Zeotap | You send raw PII (email, cellno); the extension hashes to sha256, sha1, md5 before forwarding. |
| PIIs are raw and must be consumed as is | You send raw PII (email, cellno); the extension forwards them unchanged. |
This setting applies only to PII (email / cellno / loginid / fpuid). Custom identities (crmID, ECID, etc.) are always forwarded as-is.
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.
A typical config
For a TCF-CMP site with raw email/phone:
| Section | Setting | Value |
|---|
| Core | Write Key | (from Source) |
| Core | Country Code | DEU |
| Consent | Consent Method | GDPR |
| Consent | Purposes for track | [1, 3, 4] |
| Consent | Check for Zeotap vendor consent | ✓ |
| PII | Hashing | PIIs are raw and must be hashed by Zeotap |
