User consent communication in Unity Ads
Understand what user consent means and how consent communication works with the Unity Ads SDK.
Read time 1 minuteLast updated a month ago
Use the Unity Ads SDK privacy APIs to communicate user consent and privacy preferences from your app. Correct implementation of user consent ensures ad delivery respects your users’ choices under supported privacy frameworks such as GDPR, CCPA, and COPPA.
If your app already uses a Consent Management Platform (CMP) or a custom consent dialog, you can pass those consent values directly to the Unity Ads SDK.
How user consent communication works
When your app receives a user's consent choice, you communicate it to the Unity Ads SDK as follows:
- Opt in (consent given) – Your app sends a consent signal to the SDK. The SDK enables personalized ad delivery.
- Opt out (consent denied) – Your app sends an opt-out signal to the SDK. The SDK restricts ads to contextual (non-personalized) delivery.
Note
The SDK acts only on the consent values it receives. It doesn’t collect consent, show dialogs, or interpret legal requirements. Your app or consent management platform (CMP) is responsible for gathering user choices and passing them to the SDK.
If you don’t send any consent signals, the SDK defaults to serving contextual (non-personalized) ads.
However, for full control over user experience and to align with your app’s design, you may opt to implement the Developer consent solution for a custom consent flow and pass the results to the SDK using the UnityAds Privacy API.