End-user consent
Manage user consent dynamically with Consent Mode
Read time 2 minutesLast updated 2 days ago
As the controller of your Developer Data, it’s your responsibility to respect end-user consent as is applicable to your business. Generally, this means you must present your users with appropriate opportunities to affirm or reject the various ways in which you intend to use their personal data. To help you fulfill this responsibility, Unity has introduced the End-User Consent Mode: a developer-friendly way to manage user consent dynamically across supported Unity services. Consent Mode allows end users to express their desired intent when making a particular consent decision. As a result, Unity products and services will be able to understand end-user consent relative to a particular use case – as opposed to service level Collect/Don’t Collect APIs that may unnecessarily suppress the value of the service to developers. Consent Mode is fully integrated with the Developer Data framework and consolidates end-user consent management for all Unity products and services that operate using Developer Data. It works by allowing you to declare default consent states for your users and to maintain changes to their consent states in near real time along the following dimensions:
-
analytics_intent
Controls whether Developer Data may be used in analytics and analytics-derived use cases that involve user-level identifiers. -
ads_intent
Controls whether Developer Data may be used in personalized advertising use cases and the collection of ads-specific device identifiers.
- : Unity will proceed with data collection and will use the data from the consenting user in accordance with the customer’s Developer Data usage settings.
granted
- : Unity will suppress purpose-specific identifier collection for the unconsenting user, and may, where applicable, limit the collection of data events which are specific to applicable intent. Unity will act in accordance with the customer’s Developer Data usage settings, however, personal data from unconsented users will be filtered-out as indicated by the user.
denied
analytics_intent = granted
ads_intent = denied