Adobe Experience Platform Tags (Adobe Launch) / Web SDK
How to configure Adobe Experience Platform Tags (Adobe Launch) / Web SDK 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, Personalise the website, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for the Adobe Experience Platform Web SDK delivered via Data Collection Tags (formerly Adobe Launch) and how to reflect them in the Consenter Manager. Individual Adobe products fed by the Web SDK (e.g. Adobe Analytics, Target) are covered by their own guides where available.
- 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. Web SDK consent handling in the Tags extension and the alloy library.
What the service does in this scope. defaultConsent accepts in, out and pending; with pending, data is stored locally until the user opts in via setConsent. If defaultConsent is not set, the default value is in. With pending and no setConsent, no data is collected and no cookies are set. The default is configured under Data Collection > Tags > Extensions > Adobe Experience Platform Web SDK > Configure > Consent. Consent status determines when an ECID is generated and identity cookies are set.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | defaultConsent: "pending"; Consenter triggers setConsent (general: in/out). |
| Configuration B — Higher risk (default configuration) | defaultConsent: "in"; collection and cookies from page load until opt-out. |
Step 1 — Configure Adobe Tags / Web SDK
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Per connected Adobe products | Per connected Adobe products |
| 2 | Default consent | Web SDK extension → Consent | Pending | In |
| 3 | Consent signal | Tags rule action / setConsent | Rule fired by Consenter choice | Opt-out only |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Adobe is a US enterprise; list the United States.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|
| Processing purposes | Improve the service, Personalise the website, Support marketing analytics | Improve the service, Personalise the website, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device identifiers, Device characteristics, Privacy choices | Browsing and interaction data, Device identifiers, Device characteristics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | Per connected products | Per connected products |
| Maximum storage duration | Per Adobe identity cookie documentation | Per Adobe identity cookie documentation |
| Processing location | United States | United States |
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