Currently, On-Device Targeting is only supported across iOS. To enable on-device targeting, follow the instructions below.
Support Center
IMODTargetingService API:
+ +(void)push:(NSString *)hashId;
The InMobi SDK collects hashed email addresses you sent. LiveRamp collects email addresses from advertisers to create Bloom Filters corresponding to advertiser’s target audience segments. Bloom Filters are fetched through InMobi SDK. The SDK further uses them to predict whether the hashed email ID will likely present in the advertiser’s target audience. The SDK identifies a strong match for advertiser deals/campaigns. Advertisers bid across on-device-enabled inventory.
LiveRamp supports a specific hashing protocol and data parameters to enable On-Device Targeting.
| Partner | Supported Hashing Protocol | Required data parameters |
|---|---|---|
| LiveRamp | SHA256 |
Q. What is a Bloom Filter?
A Bloom filter is a space-efficient probabilistic data structure used to test whether an element is present in a data set in the form of 0s and 1s.
Q. Is the Bloom Filter passed into a different field in the bid request?
Bloom Filter isn't passed into the bid request. It is stored on the device itself and will signal the SDK to call for the deal ID if the user belongs to the target audience.
Q. What's the benefit of the Bloom Filter methodology for on-device targeting?
Low storage makes it viable to match the device without impacting the app's performance. A 1 million user email ID data set is merely a 1-2 MB payload (smaller than some of the standard video ads we run today).
By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.