Adobe Analytics
How to configure Adobe Analytics at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Adobe Analytics and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Adobe Analytics web data collection (AppMeasurement or the Adobe Experience Platform Web SDK). Adobe Target, Audience Manager and the Experience Cloud Identity Service are covered in the Adobe Experience Cloud guide.
What the service does in this scope. Data collection libraries generate a visitor ID per browser, stored in a cookie; if no cookie can be set, a fallback method ties hits to the same visit. Report suite settings can replace the last octet of IP addresses with zero before geo reports are populated, and IP Obfuscation can further hash or remove the IP address. With the Web SDK, IP obfuscation can also be applied at the Edge Network in the datastream configuration.
Legal role. Adobe processes Analytics data on behalf of its customers under its data processing terms. Adobe Inc. is a US company.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Last octet replaced with 0 and IP obfuscation (remove/hash); no customer IDs; after consent. |
| Configuration B — Higher risk | Full IP processing (no obfuscation); customer IDs and marketing channel data used for attribution; after consent. |
No configuration without prior consent. The visitor ID cookie is persistent; no consent-free configuration is documented.
Step 1 — Configure Adobe Analytics
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics |
| 2 | Replace last octet | Admin > Report Suites > Edit Settings > General > General Account Settings > Replace the last octet of IP addresses with 0 | On | Off |
| 3 | IP Obfuscation | Same page > IP Obfuscation (obfuscate / remove) | Remove IP address | Disabled |
| 4 | Web SDK datastream IP obfuscation | Data Collection > Datastreams > IP Obfuscation (Web SDK only) | Full | None |
| 5 | Customer IDs / declared IDs | Implementation (s.visitorID, identity map) | Not used | Used |
| 6 | Loading | Consenter blocking of the library / tag | After consent | After consent |
| 7 | Data retention | Admin > Data Governance / contractual retention | Short (e.g. 13 months, illustrative) | Long (e.g. 25 months, illustrative) |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Adobe Inc. is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential processing and access location.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Non-precise location data | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address, Non-precise location data, Authentication-derived identifiers, Users' profiles, e-commerce Activity (if commerce events are tracked) |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | 13 months (illustrative) | 25 months (illustrative) |
| Processing location | Per data centre; United States as potential access location | Per data centre; United States as potential access location |
Privacy-policy follow-up
- Adobe as processor; visitor ID cookie; IP handling; retention; US provider and potential access by US authorities.
Verification checklist
- No Adobe Analytics beacons before consent.
- Report suite IP settings match the configuration.
- Retention period documented in the contract.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on