Leveraging RampID and UID2

Passing emails and phone numbers to MobileFuse will improve monetization while adhering to privacy standards. MobileFuse has partnered with LiveRamp and is utilizing the LiveRamp Authenticated Traffic Solution API to ensure the process is privacy-first and utilizes authenticated private information only.

For more information about LiveRamp’s Authenticated Traffic Solution visit here.

Currently, the only supported paths to leverage RampID and UID2 are via:

• The MobileFuse SDK
• ATS Mobile SDK directly
• If you are leveraging Nimbus, InMobi, or Pubmatic to connect to MobileFuse
  *Currently Pubmatic OpenWrap and TAM do not support passing envelopes.

For more on LiveRamp supported paths click here.

How to pass data

The method for passing user emails or phone numbers depends on the integration method you are using. Regardless of which methods you use, MobileFuse servers only ever interact with anonymized LiveRamp envelope and not with emails or phone numbers directly. We only accept LiveRamp envelopes if the user is not opted-out of tracking.

Regardless of how you choose to leverage LiveRamp, you will need to:

• Update your privacy policy to adhere to LiveRamp’s terms and conditions which can be found here.
• Sign an agreement with LiveRamp. You can reach out to them directly at [email protected] or have your MobileFuse account manager make an introduction on your behalf.

In order to support UID2 via TheTradeDesk

Request access to UID2 from TheTradeDesk here. Once complete, confirm with your MobileFuse account manager.

For publishers utilizing the MobileFuse SDK

Passing phone numbers or emails

You can pass emails or phone numbers directly into the SDK. The SDK will never transmit these emails directly to MobileFuse or include them in the bid stream. When an email address or phone number is passed to the SDK, they will be hashed and passed to the LiveRamp ATS API in order to generate an encrypted and anonymized LiveRamp envelope. This is then passed in the bidstream when privacy flags allow tracking.

Use the following methods to pass an email or phone number to the SDK:

MobileFuseTargetingData.setEmail("[email protected]");
MobileFuseTargetingData.setPhoneNumber("+1 (555) 555-5555");

MobileFuseTargetingData.email = "[email protected]"
MobileFuseTargetingData.phoneNumber = "+1 (555) 555-5555"

[MobileFuseTargetingData setEmail: @"[email protected]"];
[MobileFuseTargetingData setPhoneNumber: @"+1 (555) 555-5555"];

📘

Info: Phone numbers

LiveRamp ATS only accepts US phone numbers. The SDK will automatically sanitize the phone number by removing spaces, prefixes and brackets, so the format is flexible. All of the following will work:

• "+1 (555) 555-1234"
• "(555) 555-1234"
• "5555551234"

Passing in a LiveRamp Envelope directly

If you already have a relationship with LiveRamp and you want to pass the envelope in directly, you can use the following method:

MobileFuseTargetingData.setLiveRampEnvelope("AqOjwcJnunA7be0m8wCMHPXgG1VpMNCLIKu07cQfxn...");

MobileFuseTargetingData.setLiveRampEnvelope("AqOjwcJnunA7be0m8wCMHPXgG1VpMNCLIKu07cQfxn...")

[MobileFuseTargetingData setLiveRampEnvelope: @"AqOjwcJnunA7be0m8wCMHPXgG1VpMNCLIKu07cQfxn..."];

Retrieving the generated LiveRamp Envelope SDK 1.5.0+

You can also retrieve the LiveRamp envelope using the following methods, this may be useful for passing the LiveRamp envelope to other display managers:

String myLiveRampEnvelope = MobileFuseTargetingData.getLiveRampEnvelope();

val myLiveRampEnvelope: String? = MobileFuseTargetingData.getLiveRampEnvelope()

NSString *myLiveRampEnvelope = [MobileFuseTargetingData getLiveRampEnvelope];

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:

{
    "user": {
        "ext": {
            "eids": [{
                "source": "liveramp.com",
                "uids": [{
                    "id": "AvAPLiE-oU_cYmbXgyM0YCOXEnRg489A51pX2uvjoZx5f8V_1yzB_nkAQ5wICpnk2s_Iw1MvC0DL2sqkbzbtJSbEy9IWp5AYnJcL"
                }]
            }, {
                "source": "uidapi.com",
                "uids": [{
                    "id": "AgAAAAPHpn5cHG8VyP6CAuHh5AMemVXXXxMdVzjhmdRl0nt8cglqmMRWTmKap05HIeNpLvEaAERX2mLp0RVSJz0M48igDHx53dsrnaenCAG/VDTJcAkHFLIplzOFjYASu0wtXsJ3IBNAWjSABjs7xmEXq73B16HRZAeCCBBKGBdvhp0rww=="
                }]
            }]
        }
    }
}