Set up a TCF or non-TCF consent configuration
Set up TCF or custom consent for Unity Ads, with Unity now a registered TCF vendor, ensuring GDPR compliance and proper regional data handling.
Read time 1 minuteLast updated a month ago
Note
TCF and non-TCF consent configuration only applies to you if your app falls under GDPR requirements.
- A TCF-compliant CMP (recommended)
- A custom or non-TCF consent setup
- Mediation or Google-specific frameworks, where applicable
Consent based on geographic location
When implementing a custom consent solution in your app, ensure that your app accounts for regional privacy regulations and any consent frameworks it supports. Privacy requirements might vary depending on the user’s location. For users in regions such as the European Economic Area (EEA):- You must collect user consent before processing personal data
- You must pass consent status to the Unity Ads SDK
- Consent requirements might differ
- You can configure your consent flow accordingly
TCF CMP users
Important
Unity is a registered TCF vendor (listed in the IAB Global Vendor List) and can do the following:
- Read consent signals from the TCF string
- Publishers using a TCF-compliant CMP can include Unity as a vendor
- Consent handling for EEA/UK traffic is now aligned with industry standards
- Unity might not receive user consent signals
- This can limit data usage for ad serving and measurement
- This might impact participation in certain demand sources
Add Unity to the CMP vendor list
If your CMP doesn’t automatically include Unity as a vendor, follow these steps to add Unity to the CMP vendor list:- Search for "Unity" in your CMP vendor list.
- Enable Unity as a vendor.
- Republish your CMP configuration.
Non-TCF users
Non-TCF setups are typically used in custom implementations or outside standard CMP frameworks. If you don't use a TCF-compliant CMP, you must manually handle consent collection and signal passing with one of the following approaches:Using a mediation provider
Check your mediation provider’s documentation to determine if they support sharing user consent status with the Unity Ads SDK. Some mediators provide APIs that allow you to set a user’s consent status and automatically communicate this status to Unity Ads.Note
Some mediators might also support Google’s Additional Consent mode, a mechanism for sharing consent with non-TCF vendors. Mediators like LevelPlay can read the Additional Consent string and pass the consent status to Unity Ads when applicable.
Without a mediation provider
If your mediator doesn’t support consent sharing or if you don't use a mediator, you can use the Developer Consent API to directly pass the user’s consent status to the Unity Ads SDK. If consent is passed to Unity using the Developer Consent API, the Unity Ads SDK will not display its built-in consent prompt.Consent support for integrations with other CMPs
Review the following table to understand what you need to do based on your integration type and whether you're using a mediation provider to pass consent signals back to the Unity Ads SDK.Integration type | Action required |
|---|---|
| Using an integrated CMP |
|
| Using a mediation provider |
|
| Without a mediation provider |
|
Where to pass consent signals
The following table details where to find instructions for passing user consent statuses to the Unity Ads SDK:Integration type | TCF CMP users | Non-TCF users |
|---|---|---|
| Using a mediation provider |
|
|
| Without a mediation provider |
|
|