Advanced Settings

GDPR – Managing Consent

OpenMediation’s mediation platform supports publisher communication of a user’s consent choice to mediated networks (for supported networks).

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

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

[OpenMediation setGDPRConsent:YES];

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

[OpenMediation setGDPRConsent:NO];

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


CCPA Compliance

OpenMediation’s mediation platform 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 a “setUSPrivacyLimit” setting, by setting its value to “true” or “false”.

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

[OpenMediation setUSPrivacyLimit:YES];

If “sale” of personal information is permitted:

[OpenMediation setUSPrivacyLimit:NO];

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



If your app is primarily directed at children, please set "setUserAgeRestricted" to "YES".

[OpenMediation setUserAgeRestricted:YES];

If your app is not primarily directed at children:

[OpenMediation setUserAgeRestricted:NO];

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.

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

  • Device Properties: the OpenMediation SDK collects certain standard parameters that pertain to the users’ device automatically such as region, 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 OpenMediation platform.

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

Supported Segment Properties

Segment Properties Type Limitation Description
Age Int 1-99

The user’s age

Gender enum OpenMediationGenderMale or OpenMediationGenderFemale

The user’s gender

IAP float 1-999999.99

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

UserId string unique

Unique identifier for each of your users

Custom Tag(s) key=string, value=string/strings[]/number/numbers[] Alphanumeric

Any additional data you’d like to dispatch to our server

Set user's age  

[OpenMediation setUserAge:20];

Set user's gender

[OpenMediation setUserGender:OpenMediationGenderMale];


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 any time after SDK initial successfully.

[OpenMediation userPurchase:12.5 currency:@"USD"];
OpenMediation.userPurchase(12.5, currency:"USD")

Set UserId

[OpenMediation setUserId:@"USER_ID"];

Set Custom Tag

You can set and modify Custom Tags at any time, we recommend that you set it before initialization.

[OpenMediation setCustomTag:@"key" withString:@"value"]; // Set User Tag
[OpenMediation removeTag:@"key"]; // Remove User Tag
[OpenMediation allCustomTags]; // Get All Tags and the Values
OpenMediation.setCustomTag("key", with:"value")
Was this article helpful?
0 out of 1 found this helpful



Article is closed for comments.