As a partner of the NinthDecimal network, we will require all publishers to send us compliance flags via an API endpoint to make sure we have a documented audit trail for every piece of data we use in the platform, ensuring full compliance that every consumer was presented with a CCPA compliant data collection and data sharing notification, and a clear indication that the user has not opted-out of the sale of data.
JSON Payload Components
Below is a list of all the payload components.
- app_key: NinthDecimal application key found in the dashboard
- bundle_id: Apple App Store or Google Play bundle
- dns_compliance: A boolean documenting whether they are CCPA compliant in terms of disclosures and DNS at the time the data was collected
An array of users objects containing:
- device_id: The Advertising Identifier or MAID provided by the device
- user_compliance: A boolean documenting whether the user has opted out of selling data
- state: (optional) home state of the user, (e.g. CA for California)
- user_id: (optional) A unique ID the publishers uses to identify the user in their app.
The publisher can call the API at a regular interval, or only call it when users change consent information or new users are acquired.
Alternative GET Method
Although the POST method is the recommended way, publishers can also use the GET method instead.