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.
Each signal supports two values:
  • granted
    : 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.
  • denied
    : 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.
Consent Mode is a core component of Unity’s Developer Data framework and applies specifically to your use of Developer Data pursuant to framework controls. Obtaining the proper consent from your end users is often critical. Consent Mode helps you align with privacy regulations and user expectations while maintaining transparency and control over how Developer Data is used across Unity products and services. If no default end-user consent is configured via Consent Mode, Unity assumes that you’ve chosen to manage those states using another method, such as a developer-controlled implementation or service-specific consent APIs. In the event no end-user consent state is knowable or available, Unity interprets the lack of signal as if the set values were the following:
  • analytics_intent = granted
  • ads_intent = denied
These defaults ensure most services can function in a privacy-conscious manner until consent from the end user becomes explicit.