COPPA compliance can be handled at the app level in DT Exchange, which causes all the placements associated to that app to inherit the same settings. Alternatively, it can be handled at the placement level. This is useful for publishers with age gates that can set different placements with different COPPA-related settings.
App Level Settings
By marking the checkbox below, you are confirming that your app is not directed at children under the age of 13 or to a general audience which may include children under the age of 13. In addition, you are confirming that it complies with the Children's Online Privacy Protection Act.
When adding a new app to the console the following window is opened for you to confirm your COPPA Compliance.
Placement Level Settings
If your app has a mixed audience, with separate waterfalls for non-COPPA and COPPA. You can set up COPPA at the placement level. This placement level configuration overrides the app level setting.
By marking the check box below, you are confirming that this placement is not directed at children under the age of 13 or to a general audience which may include children under the age of 13. In addition, you are confirming that it complies with the Children's Online Privacy Protection Act.
User Level Settings
Starting from iOS SDK version 8.2.1 and Android SDK version 8.2.3, DT Exchange provides an additional method of flagging users as COPPA at the user level. If your app has a mixed audience and has an age screen or gate implemented, you can check the app or placement level settings check box (see examples in the images above) and implement the COPPA API to flag specific users as children instead of treating all users as children on either an app or placement level.
In the event of a conflict between the settings in the Console and what is passed in the COPPA API, the COPPA-compliant setting is used.
To implement the COPPA API, click for the appropriate operating system: