Privacy with LiveIntent

image-20261014-084807.png

LiveIntent forwards privacy and consent signals to external partners during permitted cookie syncs. These signals allow partners to receive the privacy context associated with each request instead of relying on fixed values in their sync configuration.

This behavior applies to partner cookie syncs from the liadm.com domain.

Parameters forwarded to partners

Partner URL parameter

Purpose

gpp

Global Privacy Platform consent string

gpp_sid

GPP section IDs identifying the applicable sections of the consent string

gdpr

Indicates whether GDPR applies to the sync request: 1 or 0

gdpr_consent

IAB Transparency and Consent Framework consent string, included when GDPR applies and the sync is permitted

us_privacy

Legacy U.S. privacy string, retained for backward compatibility

Inbound GPP values may use different parameter names. LiveIntent maps gpp_s or gpp to the partner’s gpp parameter, and gpp_as or gpp_sid to the partner’s gpp_sid parameter.

Optional privacy strings are forwarded when present and non-empty. LiveIntent does not append a parameter when the same key already exists in the partner’s configured URL, so fixed privacy values in partner configurations must be reviewed.

How GDPR is handled

LiveIntent uses the request’s GDPR signal and the user’s country lookup to resolve GDPR applicability.

Request and location

Result

gdpr is missing, and the user is in the EU, EEA, or UK

Treat the request as gdpr=1 and validate consent

gdpr is missing, and the user is outside those regions

Set gdpr=0

gdpr=1 is supplied, and the user is in a GDPR region

Validate consent

GDPR is supplied, but the user is outside a GDPR region

Send gdpr=0 to the partner

If consent is missing or invalid, LiveIntent blocks the sync and does not fire a partner pixel or redirect.

For permitted requests where GDPR applies, the partner receives gdpr=1 and gdpr_consent. Where GDPR does not apply, the partner receives gdpr=0, and gdpr_consent is omitted.

GPP and legacy U.S. privacy strings do not override the GDPR allow/block decision. Requests must also satisfy the configured country eligibility rules.

Guidance for tag implementations

Preserve the standard privacy variables and macros supplied with your Zeta tags. These variables carry the consent signals used by downstream services. If your deployment environment cannot populate them correctly, contact your Zeta representative for assistance.

See Best Practices for Tag Data Capture for privacy-variable definitions and deployment guidance.


LiveConnect and LivePixel use a visitor’s consent choices to determine whether tracking and identity resolution can take place.

Where GDPR consent is required, the visitor must consent to LiveIntent and all four required purposes in the IAB Transparency and Consent Framework (TCF): purposes 1, 2, 3, and 4. Consent to only some of these purposes is insufficient.

Until the required consent is available, LiveConnect prevents tracking-cookie and local-storage access, tracking pixels, cookie syncing, and identity resolution. LivePixel also checks consent before processing incoming data.

Visitors can change their choices through your website’s consent management platform (CMP) while browsing.

LiveConnect monitors these changes through the CMP’s TCF interface. If a visitor withdraws the required consent, LiveConnect stops tracking and identity resolution, removes its applicable tracking cookies, and clears the associated tracking information from local storage.

If the visitor later provides the required consent again, LiveConnect can resume permitted tracking without requiring a page reload. Processing remains subject to the applicable regional restrictions.

LivePixel uses the visitor’s IP address to determine whether the request comes from a GDPR region. A GDPR value supplied by the website does not override this location check. If the IP-based lookup identifies a GDPR region, LivePixel applies the required consent checks before processing the request.

Preparing your website

Your website’s CMP must support the TCF interface used by LiveConnect to receive consent updates. Keep the standard privacy variables supplied with your Zeta tags in place so that requests continue to carry the appropriate consent information.

After implementation, verify that tracking responds correctly when a visitor grants consent, withdraws it, and grants it again.