Adobe Analytics
Enterprise analytics that does not resell your data, with real residency controls — but it is cookie- and identifier-based, and consent honoring depends on your implementation.
verified 2026-06-08 · grade set per the published methodology
How the grade breaks down
How little it collects, and whether collection is purpose-bound.
Whether it respects GPC, consent state, and tracking-prevention signals.
Cookieless vs. persistent IDs, cross-site linkage, fingerprinting risk.
Where data lives and whether it is shared with third parties.
How verifiable and documented its real behavior is.
At a glance
Adobe Analytics operates as a processor and does not monetize customer data for its own advertising, which differentiates it from ad-platform analytics. It supports data-residency options and granular governance. However, it relies on cookies and the Experience Cloud ID (ECID), can be configured in ways that approach device fingerprinting, and its consent behavior is only as good as the Adobe Launch/Tags and consent-framework implementation around it. Privacy outcomes vary widely between well-governed and default deployments.
Sources & basis for grade
Grades reflect documented behavior, vendor documentation, and ad.rip scans as of the date above. Each assessment is reproducible and vendors may request correction.
- Adobe Experience Cloud ID (ECID) documentation
- Adobe Analytics data-governance / data-residency docs
- Adobe consent-framework (OneTrust/Adobe) integration docs