Advanced Settings

GDPR – Managing Consent

AdTiming’s mediation platform (Android SDK Version 6.5.0 and above) supports publisher communication of a user’s consent choice to mediated networks (for supported networks).

To use AdTiming’s API to update a user’s consent status, use this functions:

If the user provided consent, please set the following flag to true:


If the user did not consent, please set the following flag to false:


It’s recommended to set the API prior to SDK Initialization.


CCPA Compliance

AdTiming’s mediation platform (Android SDK Version 6.5.0 and above) supports publishers to restrict the sale of end users personal information under the California Consumer Privacy Act (CCPA).

The notification about personal information of specific users located in California should be handled based on setUSPrivacyLimit setting, by setting its value to true or false.

If the user has opted out of “sale” of personal information:


If “sale” of personal information is permitted:


It’s recommended to set the API prior to SDK Initialization. 


COPPA Compliance

To protect children, AdTiming does not advertise for users under the age of 13, be sure to follow the following guidelines:

1. In order to add new application at AdTiming publisher platform and successfully create ad placement, you have to agree to the COPPA compatibility option. Please make sure your app is not designated as a child-directed mobile application. And if it is, please do not check the compatibility option.


2. If your app is not a child-directed application but the users may include people under the age of 13, then you must have a mechanism in the app to determine whether the current user is over 13 years old. If the user is under the age of 13, please be aware that you should not initialize AdTiming SDK in the application for load&show ads. If your application initializes AdTiming SDK for load&show ads, we default that the current user for the app is 13 years old or above.

AdTiming’s mediation platform (Android SDK Version 6.5.0 and above) supports setAgeRestricted flag that helps publishers monetize their user base while remaining in compliance with the Children’s Online Privacy Protection Act (COPPA).

You should indicate whether a user is a child. If the user is known to be in an age-restricted category (i.e., under the age of 13) please set the following flag to true.


If the user is known to not be in an age-restricted category (i.e., age 13 or older) please set the following flag to false.


It’s recommended to set the API prior to SDK Initialization. 


Define Segments

You can now easily tailor the way you serve your ads to fit a specific audience! You’ll need to inform our servers of the users’ details so the SDK will know to serve ads according to the segment the user belongs to.

AdTiming supports two methods to convey data to our servers to outline the user segment, namely:

  • Device Properties: the AdTiming SDK collects certain standard parameters that pertain to the users’ device automatically such as location, device model, device manufacturer, app version, OS, etc. You do not need to convey this data to us.
  • User Properties: comprehensive user data such as age, gender, IAP, etc. (see full list of supported segment properties with descriptions below) must be relayed through the API. Follow the instructions to send us your user’s details so our SDK can categorize your different users based on the segments you defined on the AdTiming platform.

Once you’ve defined segments on the AdTiming platform, you should inform our servers of the user’s particulars.


Supported Segment Properties

User Properties Type Limitation Description
Age int 1-99

The user’s age

Supporting SDK Version 6.5.0

Gender String male or female

The user’s gender

Supporting SDK Version 6.5.0

IAP float 1-999999.99

The total amount of money that the user has spent on in-app purchases

Set user's age  


Set user's gender



IAP, an acronym for in-App Purchase, can be understood as an in-app purchase. We need you to pass the current device user's IAP data to the SDK through the setIAP method in the APP so that we can provide more accurate advertising.

AdTimingAds.setIAP(float iapCount, String currency);

The parameter currency is a String represents the currency code of the ISO, based on the International Organization for Standardization's national code, is published in the ISO 4217:2008 standard and is used to represent money and funds.

You could set IAP after SDK initial successfully, such as at the time the IAP data is changed.

AdTimingAds.setIAP(12.30f, "USD");



Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.