Overview
partnerConsentKeyMap lets you control Zeotap’s cookie syncing feature on a per-channel-partner basis. By default, the cookieSync key in setConsent enables or disables cookie syncing globally across all partners. With partnerConsentKeyMap, you can grant or deny cookie sync consent for individual partners (e.g. Google, Meta) independently.
You define a mapping of Zeotap Partner ID → key you use in your setConsent call. When setConsent is called, the SDK reads those keys and determines which partners are consented for cookie syncing.
This feature is only active in custom consent mode (useConsent: true, checkForCMP: false).
How It Works
- Define
partnerConsentKeyMapin yourinitoptions — a map of Zeotap Partner ID to the key you will pass insetConsent. - Call
setConsentwith those keys set totrueorfalse. - The SDK extracts the partner-specific values and uses them to control cookie syncing for each partner individually.
- These keys are forwarded to Zeotap as Consented Channel Partners (CCP).
Setup
Step 1 — Configure during init
Step 2 — Call setConsent with partner cookie sync keys
How the SDK Processes the Consent Object
Given the above example:Full Example
Notes
partnerConsentKeyMapmust be a plain object. Keys are Zeotap Partner IDs and values are the corresponding keys in yoursetConsentcall.- Partner consent keys are extracted before the consent object is processed, so they will not appear in the brand consent payload.
- If
partnerConsentKeyMapis not set or is not a valid object, the SDK skips partner-level cookie sync consent extraction. - This feature has no effect when
useConsentisfalseorcheckForCMPistrue(TCF/CMP mode).
Supported Channel Partners
To get the full list of supported Zeotap Partner IDs contact support.