Set up your bannerConfigure Your ToolsTag Management

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Medium riskdefaultConsent: "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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
1Processing purposesOperator decisionPer connected Adobe productsPer connected Adobe products
2Default consentWeb SDK extension → ConsentPendingIn
3Consent signalTags rule action / setConsentRule fired by Consenter choiceOpt-out only

Step 2 — Map the configuration in the Consenter Manager

Processing location. Adobe is a US enterprise; list the United States.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
Processing purposesImprove the service, Personalise the website, Support marketing analyticsImprove the service, Personalise the website, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device identifiers, Device characteristics, Privacy choicesBrowsing and interaction data, Device identifiers, Device characteristics
Legal role of data recipientProcessorProcessor
Personalisation modelPer connected productsPer connected products
Maximum storage durationPer Adobe identity cookie documentationPer Adobe identity cookie documentation
Processing locationUnited StatesUnited 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

On this page