Documentation

Unity Monetization

Unity Ads User Acquisition

Levelplay

Offerwall

Unity Monetization

Set the correct consent signal mappings

Make sure your consent signals are mapped correctly for opt-in, opt-out, and age-restricted user APIs, according to the privacy frameworks you need to support for user privacy consent.
Read time 2 minutesLast updated 11 hours ago
Refer to the following information to identify which consent signal to use for each privacy framework supported by the Unity Ads SDK.

Opt-in frameworks

Use the 
setUserConsent()
API when a framework requires explicit opt-in consent before collecting or processing personal data. The user must actively opt in. The default is opt-out until you receive opt-in consent. If the user doesn’t give consent, the default is opt-out.

Opt-in framework

Region

GDPREuropean Economic Area (EEA), United Kingdom
Quebec Law 25Quebec, Canada
Apple App Tracking Transparency (ATT)Global

Opt-out frameworks

Use the 
setUserOptOut()
API when a framework grants users the right to opt out of data collection or targeted advertising. The user is opted in by default (if the user is not a child), unless they opt out. If the user doesn’t opt out, the default is opted-in.

Opt-out framework

Region

California Consumer Privacy Act (CCPA)California, United States
Virginia Consumer Data Privacy Act (VCPDA)Virginia, United States
Colorado Privacy Act (CPA)Colorado, United States
Connecticut Data Privacy Act (CTDPA)Connecticut, United States
Utah Consumer Privacy Act (UCPA)Utah, United States
Florida Digital Bill of Rights (FDBR)Florida, United States
Oregon Consumer Privacy Act (OCPA)Oregon, United States
Texas Data Privacy and Security Act (TDPSA)Texas, United States
Montana Consumer Data Privacy Act (MCDPA)Montana, United States
Iowa Consumer Data Protection Act (ICDPA)Iowa, United States
Nebraska Data Privacy Act (NDPA)Nebraska, United States
New Hampshire Data Privacy Act (NHDPA)New Hampshire, United States
Delaware Personal Data Privacy Act (DPDPA)Delaware, United States
New Jersey Data Privacy Act (NJDPA)New Jersey, United States
Tennessee Information Protection Act (TIPA)Tennessee, United States
Minnesota Consumer Data Privacy Act (MNCDPA)Minnesota, United States
Maryland Online Data Privacy Act (MODPA)Maryland, United States
Rhode Island Data Transparency and Privacy Protection Act (RIDTPPA)Rhode Island, United States
Kentucky Consumer Data Protection Act (KCDPA)Kentucky, United States
Indiana Consumer Data Protection Act (ICDPA)Indiana, United States

Age-restricted users specification

Use the 
setNonBehavioral()
API when a framework or policy requires non-behavioral (contextual only) ad delivery, typically for content directed to children or younger users.
Important
If your app is child-directed, ensure the following:
  • The 
    setNonBehavioral
    API is set to 
    true
    prior to SDK initialization
  • This setting is applied consistently across all traffic for your app, not just select sessions
If this is already part of your integration, no further action from you is needed to ensure your child-directed consent implementation is set up correctly and identifiers are handled appropriately on-device before the first ad request is made.

Framework

Region

COPPA / CARU
  • United States
Google Play Families Policy
  • Global