...
Under the hood, MobileFuse accepts raw phone/email but raw data is never sent to MobileFuse servers. Instead, we utilize the LiveRamp ATS API from the device to obtain a LiveRamp ID once we’ve received the email or phone number along with consent. We ensure that the OS level tracking is respected (eg. Do Not Track, ATTS) and if those are opt-out then we completely disable this feature. Then when an email or phone number is supplied, we send over the consent strings (eg. US Privacy, TCF) along with hashed versions of the PII to the LiveRamp API endpoint and they also validate that proper consent has been obtained.
[placeholder for how to call static methods]The actual calls to pass the data are as simple as:
Android (Java)
Code Block | ||
---|---|---|
| ||
MobileFuseUserTargeting.setEmail("user@email.com");
MobileFuseUserTargeting.setPhoneNumber("+1 (555) 555-5555"); |
Android (Kotlin)
Code Block | ||
---|---|---|
| ||
MobileFuseTargetingData.email = "user@email.com"
MobileFuseTargetingData.phoneNumber = "+1 (555) 555-5555" |
iOS (Objective-C)
Code Block | ||
---|---|---|
| ||
[MobileFuseTargetingData setEmail: @"user@email.com"];
[MobileFuseTargetingData setPhoneNumber: @"+1 (555) 555-5555"]; |
For publishers integrated directly with MFX (via OpenRTB)
When passing data to MFX, SSPs should provide LiveRamp envelopes or UID 2.0 tokens that they have already obtained with the user’s consent (through a process similar to the steps outlined above). These alternative IDs should be passed via the user.ext.eids
array field. Note that only sources liveramp.com
(RampID Envelope) and uidapi.com
(UID 2.0 Token) are supported at this time. For example:
...