Set up your bannerConfigure Your ToolsAnalytics

Adjust

How to configure Adjust at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics, Customise online ads

Overview

This guide explains how to implement different privacy configurations for the Adjust Web SDK and how to reflect them in the Consenter Manager.

  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. The Adjust Web SDK for web attribution and measurement. Adjust GmbH (Berlin) belongs to AppLovin Corporation, a US company.

What the service does in this scope. The URL strategy sets the endpoint and data residency; EU data residency uses eu.adjust.com. Adjust.trackThirdPartySharing with a ThirdPartySharing instance controls whether Adjust shares the user's data with third parties; granular options pass partner-specific consent (e.g. google_dma keys ad_user_data, ad_personalization). gdprForgetMe sends an erasure request.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskAttribution only; EU data residency; third-party sharing disabled; after consent.
Configuration B — Higher riskAttribution with third-party sharing to ad partners and consent signals passed; after consent.

No configuration without prior consent. Attribution requires identifying the device across visits.

Step 1 — Configure Adjust

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Customise online ads
2URL strategy / data residencyAdjust.initSdk({ urlStrategy … })EU data residencyEU data residency
3Third-party sharingAdjust.trackThirdPartySharing(new Adjust.ThirdPartySharing(…))falsetrue, with granular partner options
4Google DMA consentGranular options for google_dma—Pass ad_user_data, ad_personalization from Consenter
5LoadingConsenter script blockingAfter consentAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. EU data residency; Adjust belongs to a US group subject to the US CLOUD Act; list the United States. Each ad partner receiving data needs its own entry as an independent controller.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesSupport marketing analyticsSupport marketing analytics, Customise online ads
Tracking methodFirst party tracking (cross-session)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP addressAs A, plus Privacy choices, Users' profiles
Legal role of data recipientProcessorProcessor (Adjust); ad partners as Individual Controller
Personalisation modelNo personalisationProfile based
Maximum storage durationPer Adjust data retention settingsPer Adjust data retention settings
Processing locationEU; United StatesEU; 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

On this page