Does Adobe Campaign web tracking require consent?

Yes. Adobe Campaign is a marketing-category vendor. Its web tracking scripts attribute visitor behavior to specific marketing campaigns and set cookies for visitor identification and campaign correlation. GDPR requires explicit consent for this processing, and ePrivacy requires consent before the uuid230 cookie is placed.

What cookies does Adobe Campaign set?

Adobe Campaign sets uuid230 (1-year, visitor ID for campaign attribution), nllastdelid (last campaign delivery ID interacted with), nlbi_[instanceID] (session, load balancer affinity), and AC (session, tracking server session). Tracking endpoints are typically operator-configured custom subdomains.

How does ConsentStack handle Adobe Campaign tracking?

ConsentStack classifies Adobe Campaign as marketing. Tracking scripts are blocked until marketing consent is granted. Once consent is obtained, campaign attribution pixels fire so conversion events and form submissions can be correlated with specific campaign sends in Adobe Campaign reporting.

What tracker domains does Adobe Campaign use?

ConsentStack has catalogued tracker domains for Adobe Campaign including neolane.net. These are the network destinations Adobe Campaign's scripts contact, which a consent platform blocks until a visitor agrees.

Adobe Campaign - Marketing Automation & Consent Info

Back to Vendor Library

Overview

Adobe Campaign is a cross-channel marketing automation platform used by enterprise organizations to orchestrate email, SMS, push notification, and web-based marketing campaigns. When its tracking scripts appear on a website, they are measuring campaign-driven traffic, capturing conversion events, and attributing website actions back to specific marketing campaigns. Adobe Campaign Classic (on-premise) and Adobe Campaign Standard (cloud) both deploy web-facing tracking components.

What This Script Does

Adobe Campaign deploys tracking scripts and 1x1 tracking pixels on websites to measure the effectiveness of marketing campaigns. When a visitor arrives from a campaign link (email click, SMS link, etc.), the scripts capture the campaign attribution parameters and track subsequent visitor behavior.

Key cookies set:

uuid230 — the Adobe Campaign visitor identification cookie. Stores a unique visitor ID for campaign attribution. Expiry varies by implementation but is commonly set to 1 year.
nllastdelid — records the last delivery (campaign) ID the visitor interacted with. Used to attribute conversions to specific campaign sends.
nlbi_[instanceID] — load balancer cookie for Adobe Campaign infrastructure. Session-scoped.
AC — session management cookie for Adobe Campaign tracking server. Session-scoped.

Tracking endpoints are typically hosted on dedicated subdomains configured by the organization (e.g., t.example.com or tracking.example.com) that proxy to Adobe Campaign's tracking infrastructure. Data collected includes: campaign IDs, delivery IDs, page URLs visited after campaign clicks, conversion events (form submissions, purchases), timestamps, and browser metadata.

Adobe Campaign's web tracking module can also capture broader visitor behavior beyond campaign-attributed visits, depending on configuration. Mirror pages, landing pages, and web forms hosted through Adobe Campaign load additional scripts for form handling and response tracking.

Consent & Compliance

Adobe Campaign operates in the marketing category. Its web-facing scripts exist specifically to track marketing campaign performance and attribute conversions.

Under the GDPR, Adobe Campaign processes personal data including visitor IDs, email recipient identifiers (when correlating web visits with email recipients), IP addresses, and behavioral data tied to marketing campaigns. This processing serves marketing purposes and requires explicit consent as the lawful basis.

The ePrivacy Directive requires consent for the tracking cookies set by Adobe Campaign. The uuid230 visitor ID cookie (typically 1-year expiry) is used for marketing attribution, not essential website functionality, and therefore falls outside the strictly necessary exemption.

Under CCPA/CPRA, Adobe Campaign collects personal information and associates it with marketing campaign interactions. The correlation between email recipients and website behavior may constitute profiling. If this data is shared with other Adobe products or third parties, it may trigger "sale" or "sharing" provisions.

Should You Block This Without Consent?

Yes. Adobe Campaign's web tracking scripts exist to measure marketing campaign performance and attribute visitor behavior to campaigns. The tracking cookies are not essential to website functionality and require consent before being set.

Is Adobe Campaign GDPR compliant?

Adobe Campaign typically loads marketing trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Adobe Campaign can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Adobe Campaign, not on Adobe Campaign itself.

Visit website