Consent Mediation¶

This feature was introduced in its beta version with the release of 2.7.0. Starting from version 2.11.0, it has transitioned to a stable version, offering enhanced functionality.

To simplify the process of signalling consent to third-party SDKs, we added a mediation feature, that works with APIs of SDKs listed below. This feature will update the consent when necessary within your application. Moreover, this functionality allows you to effortlessly activate Google Consent Mode and connect to advertising and mediation tools that, for instance, may not be part of TCF.

Once correctly implemented, this feature simplifies the transmission of the consent signal and privacy choices to selected third-party SDKs.

However, it is always advisable to review and assess the documentation, privacy policy, and privacy section of third-party vendor SDKs before deciding to work with them or integrating any.

Please note that Usercentrics cannot fully guarantee the compliance of collection mechanisms of third-party vendors and SDKs.

How it works?¶

The Consent Mediation feature on Unity operates by integrating SDKs APIs in order to stream user consent.

Most Unity SDKs use a native implementation, serving as a bridge to their respective native platforms. Our approach integrates with these native libraries designed for Android and iOS.

The supported SDKs listed below all utilize this integration method. If you encounter a library that doesn't follow a native implementation, please let us know by providing feedback.

You can access a comprehensive overview of the native implementations for mediating consents here.

Enable Mediation¶

Supported SDKs¶

It is essential to thoroughly review the documentation of each SDK to identify the specific APIs necessary for accurately signaling user consent.

Be aware that some SDKs, such as Crashlytics, may automatically collect data by default.

Although most SDKs maintain consistent contracts for Privacy APIs in their updates, any changes must be noted, and the appropriate API should be used accordingly. Remember, rigorous testing is vital for success. While our feature addresses a majority of scenarios, it is imperative that you personally verify the expected behavior in your specific use case.

Unity End-User Consent Mode (Vector)¶

Unity's Vector ad optimization product requires apps to signal consent through Unity's newer EndUserConsent.SetConsentState API (AnalyticsIntent and AdsIntent), which is conceptually equivalent to Google Consent Mode v2 but for the Unity ad ecosystem. This is separate from the legacy gdpr.consent/privacy.consent MetaData APIs that Unity Ads uses above, and from the automatic Consent Mediation feature described earlier on this page.

UC consent categories are configured per project and don't map to a fixed "analytics" or "advertising" name, so you must tell the SDK which of your configured category slugs correspond to Unity's AnalyticsIntent and AdsIntent signals:

Usercentrics.Instance.Options.UnityConsentMode.Enabled = true;
Usercentrics.Instance.Options.UnityConsentMode.AnalyticsCategorySlugs = new List<string> { "analytics" };
Usercentrics.Instance.Options.UnityConsentMode.AdsCategorySlugs = new List<string> { "advertising" };

Set these before calling Initialize(). Once enabled, the SDK will:

• Call SetConsentState once immediately after initialization, using the user's current consent decision.
• Call SetConsentState again automatically whenever the user changes or withdraws consent during the session — no app restart required.

Category-to-intent mapping¶

The SDK grants a category's intent whenever at least one of your services under that category slug has an active TRUE consent; otherwise it denies the intent. Accept-all and deny-all work automatically, since every service's status changes together in those cases:

Supported Mediation SDKs¶

These SDKs mediate consent for selected SDKs themselves. Make sure you set up the correct TemplateIDs to automatically pass consent to mediated SDKs.

Adjust¶

Check out the documentation page to get an insight on the Partners API. Note that we only support the ones listed below.

Amazon Ads — Amazon Consent Signal (ACS)¶

Unlike the partners listed above, Amazon Ads is not selected via a Template ID override. There is no native Amazon SDK bridged into Usercentrics — instead, the signal is forwarded through Adjust's granular third-party-sharing API (partner name amazon_dma) automatically whenever both of the following are true:

• Amazon (IAB TCF vendor ID 793, "Amazon.com Services, Inc.") is a declared, consented vendor in your configuration
• Adjust itself is configured as a Data Processing Service (DPS) for your tenant (Template ID Jy6PlrM3)

When both conditions are met, the SDK derives a granular consent object from the TCF purposes and signals it to Adjust:

This mirrors the existing Google Consent Mode signal (vendor 755), except Amazon does not use ad_personalization or eea flags. Added in version 2.29.1.

Debugging¶

When running your application with Consent Mediation enabled, you should expect the following events:

Enable Confirmation

Immediately after initialization, you will get a confirmation that Consent Mediation is Enabled:

[USERCENTRICS] Consent Mediation is Enabled

Scan

After your configuration has been loaded, the SDK will provide an overview of the supported services:

[USERCENTRICS][Mediation] 2/6 Services are supported: Unity Ads | Google Analytics for Firebase

Mediation

Whenever a user provides consent or the SDK has been initialized, the SDK will apply the latest user choices to each supported SDK:

[USERCENTRICS][Mediation] ✅ Google Analytics for Firebase: TRUE
[USERCENTRICS][Mediation] ✅ Unity Ads: FALSE