ContextQMD
Back to Unity

Set up a TCF or non-TCF consent configuration

en-us-ads-android-4-dot-19-dot-0-privacy-developer-consent-frameworks-gdpr-tcf-and-non-tcf-consent.md

latest5.9 KB
Original Source

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 minute

Last updated 3 days ago

Note

TCF and non-TCF consent configuration only applies to you if your app falls under GDPR requirements.

This guidance applies to publishers operating in regions with privacy regulations (such as the EEA) and using consent frameworks to manage user data.Unity is a registered vendor in the IAB Transparency and Consent Framework (TCF). If you are using a TCF-compliant Consent Management Platform (CMP), Unity can receive consent signals directly through the TCF string.The following sections explain how to implement custom consent using:

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

For users outside of regulated regions:

  • Consent requirements might differ
  • You can configure your consent flow accordingly

Refer to your legal guidance to determine how to apply consent requirements by region.

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

If Unity is not included in your CMP configuration:

  • 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

If you are using mediation or custom consent handling, ensure consent signals are correctly passed to Unity Ads. In most cases, no changes to your integration are required.Proper consent handling ensures access to demand sources and compliant use of user data for advertising and measurement.

If you’re using a TCF-compliant Consent Management Platform (CMP), Unity can receive consent signals through the TCF string. In most cases, your CMP will automatically include Unity as a vendor.

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:

  1. Search for "Unity" in your CMP vendor list.
  2. Enable Unity as a vendor.
  3. Republish your CMP configuration.

Refer to your CMP provider’s documentation for details.

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.

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 |

  • Follow your CMP provider’s guidelines to configure consent handling
  • Ensure user consent signals are passed to Unity Ads through your integration

| | Using a mediation provider |

  • Refer to your mediation provider’s documentation to determine how consent signals are shared with Unity Ads.
  • Consent signals being shared with the Unity Ads SDK are typically handled through APIs.

| | Without a mediation provider |

  • Retrieve the user’s consent value from your CMP
  • Use the Developer Consent API to pass this consent directly to the Unity Ads SDK

|

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 |

  • Refer to your mediator’s documentation to determine how consent signals are shared with the Unity Ads SDK using the TCF string, typically through APIs or Google’s Additional Consent mode.

|

  • Refer to your mediator’s documentation to determine how consent signals are shared with the Unity Ads SDK, typically through APIs.

| | Without a mediation provider |

  • Refer to the Developer Consent API (TCF string supported) to pass the consent status directly to the Unity Ads SDK.

|

  • Refer to the Developer Consent API to pass the consent status directly to the Unity Ads SDK.

|