Advanced Settings

GDPR – Managing Consent

OpenMediation’s mediation platform (Unity SDK Version 2.0.0 and above) 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(We will save your latest settings):

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

Om.Agent.setGDPRConsent(true);

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

Om.Agent.setGDPRConsent(false);

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 setUSPrivacyLimit setting, by setting its value to true or false(We will save your latest settings)

If the user has opted out of "sale" of personal information:

Om.Agent.setUSPrivacyLimit(true);

If “sale” of personal information is permitted:

Om.Agent.setUSPrivacyLimit(false);

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

 

COPPA Compliance

To protect children, OpenMediation 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 OpenMediation 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.

Snip20201218_1.png

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 OpenMediation SDK in the application for load&show ads. If your application initializes OpenMediation SDK for load&show ads, we default that the current user for the app is 13 years old or above.

OpenMediation’s mediation platform (SDK Version 2.0.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). (We will save your latest settings)

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.

Om.Agent.setAgeRestricted(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.

Om.Agent.setAgeRestricted(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.

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

User Properties Type Limitation Description
Age int 1-99 The user’s age
Supporting SDK Version 2.0.0 and above
Gender String male or female The user’s gender
Supporting SDK Version 2.0.0 and above
IAP float 0-999999.99 The total amount of money that the user has spent on in-app purchases
UserId String unique User unique identifier
Supporting SDK Version 2.1.0 and above
CustomTag(s) key = String
value = String or String[]
  • supports up to 10 custom parameters
  • alphanumeric
  • up to 48 letters
Any additional data you’d like to dispatch to our server
Supporting SDK Version 2.1.0 and above

Set user's age (We will save your latest settings)

Om.Agent.setUserAge(20);

Set user's gender (We will save your latest settings)

Om.Agent.setUserGender("male");

Set IAP

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.

Om.Agent.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.

Om.Agent.setIap(12.30f, "USD");

Set UserId

The application can report a customized user ID through SDK v2.1.1 and higher, and only needs to call the setUserId method to set it before initialization.

Om.Agent.setUserId(string userId); 

Get UserId

Om.Agent.getUserId();

Set Custom Parameters

Applications can report custom parameters through SDK v2.1.1 and above, and only need to call the setCustomTag method to set them before initialization. This parameter will be reflected in the user-level data.

// Set app defined user tags
Om.Agent.setCustomTag(string key, string value);
Om.Agent.setCustomTags(string key, string[] values);
// Return the tags set by the user, return null if not set
Om.Agent.getCustomTags();
// Remove app defined user tag
Om.Agent.removeCustomTag(string key);

 

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

Comments

0 comments

Please sign in to leave a comment.