- Need to know
- New in 5.0
- Passing Keywords
- Passing Location
- Frequency Capping ID
- Best Practices
Need to know
As of the 5.0 SDK release, MoPub provides a field for publisher to send personal data. Publisher Partners must send any demographic or interest-based targeting data in the fields designated for such data, as described below. Publisher Partners must not include any personal data, including demographic or interest-based targeting data, in any fields intended for contextual targeting (i.e., targeting based on the content of the app). Additionally, publishers should not send MoPub any keywords that are against the MoPub Privacy Policies.
New in 5.0
Personal data passing: The MoPub SDK now exposes an additional keyword API (
userDataKeywords) for publishers to send personal data. Publisher Partners must send any demographic or interest-based targeting data (
m_age:24) in this field.
Non-personal data passing: Contextual keywords can continue to be passed via the
Pass the keywords from your app to MoPub as a comma-separated list in the ad view. Each keyword should be formatted as a key/value pair (e.g.
m_age:24). Any characters can be used except
Banners and interstitials
MPAdView *adView = [[MPAdView alloc] initWithAdUnitId:@"AD_UNIT_ID" size:MOPUB_BANNER_SIZE]; adView.delegate = self; adView.keywords = @"CONTEXTUAL_KEYWORDS"; adView.userDataKeywords = @"USER_DATA_KEYWORDS"; [adView loadAd];
[MPRewardedVideo loadRewardedVideoAdWithAdUnitID:self.info.ID keywords:@"CONTEXTUAL_KEYWORDS" userDataKeywords:@"USER_DATA_KEYWORDS" location:nil customerId:@"CUSTOMER_ID" mediationSettings:@];
MPNativeAdRequestTargeting *targeting = [[MPNativeAdRequestTargeting alloc] init]; targeting.keywords = @"CONTEXTUAL_KEYWORDS"; targeting.userDataKeywords = @"USER_DATA_KEYWORDS"; ["YOUR_AD_PLACER" loadAdsForAdUnitID:self.adInfo.ID targeting:targeting]
The MoPub Marketplace and certain ad networks can use your user’s location to send more targeted ads. If your app already has location permissions (based on you obtaining appropriate consent from the end user), the MoPub SDK will automatically attempt to acquire location data for ad requests.
You can use
MoPub.h to opt out of this functionality. The MoPub SDK will never prompt the user for permission if location permissions are not currently granted.
You can also choose to pass the location yourself by passing any
MPAdView which will forward what you supply to the location property down to the underlying ad network.
Using the same key value pairs, target campaigns using the keyword targeting function in the Advanced Targeting dropdown. To target multiple keywords, use
m_gender:m AND m_age:25). If you want to use the
OR clause, separate the keywords by a new line.
Frequency Capping ID
In SDK versions 4.9+, MoPub automatically passes a rotating identifier for devices using iOS10 or later and have elected to limit ad tracking. This identifier is used solely to continue to provide MoPub-internal frequency capping, while respecting the change in Apple’s IDFA practices. If you wish to disable this feature, follow the instructions below.
You can use
MoPub.h to opt out of this functionality.
When in doubt, you can always call
[[MoPub sharedInstance] canCollectPersonalInfo] to determine if you should be processing any personal data. If you are using MoPub mediation, adapters have already been modified to let the mediated SDKs know whether they, too, can collect and process users’ personal data.
Last updated March 04, 2019
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2019 MoPub (a division of Twitter, Inc.)