LiveRamp's Wholesale Mobile Match Data Feed
LiveRamp can provide you with a batch transfer or feed of mobile match data from our large network of publishers, linking mobile device IDs (IDFA/AAID) to hashed email addresses (MD5, SHA-1, and SHA-256). This can power a range of use cases, including CRM onboarding, offline, and cross-device attribution.
Set Up Mobile Match Data Deliveries
We typically deliver files to SFTP and S3 daily, but we also have a Python script that can be used to download files on any schedule, as well as a real-time HTTPS stream. For more information, see "LiveRamp's Wholesale Delivery Methods".
LiveRamp also needs the following information:
The hash types you want to receive (available hash types are MD5, SHA-1, and SHA-256).
The countries you want to receive data from (e.g., U.S. only).
The desired delivery cadence (typically daily).
The desired data recency (typically 12-18 months for match data, since mobile advertising IDs and emails are long-lived).
Whether you want our default level of linkages (maximum scale) or a custom level. For more information, see "Volume Levers for Wholesale Data".
Column | Column Required? | Definition | Example |
|---|---|---|---|
Mobile Device ID | Yes | The mobile device ID (mobile advertising ID) of the device. | 69A2109A-0134-4EEC-B4AF-65855133B008 |
ID Type | Yes | Mobile Device ID Type - Apple Identifier for Advertising (“IDFA”) or Google Android Advertising ID (“AAID”). | IDFA |
User Agent | No | User Agent string of the device. | "iPhone 6; iPhone OS 9.2" |
IP Address | Yes | IP address of the device. NoteLiveRamp highly recommends sending only IPv4 IP addresses. You can send IPv6 IP addresses, but in most cases, we will not be able to match them. | 70.212.10.74 |
Timestamp | Yes | Unix Timestamp (seconds since Unix epoch) of when the user was active/logged in. | 1455172609 |
MD5 Hash | No | Email address using MD5 hashing. | a010407ea27f6a9ccc70e5d149a7818f |
SHA-1 Hash | No | Email address using SHA-1 hashing | 3b31875f46abd81fb6c003d7a84492f6ef1b2d5e |
SHA-256 Hash | No | Email address using SHA-256 hashing. | 7f0098da19b0f540dbcde477f969fec3e4d8b40f6d1686c6b24d4c2aaea48fea |
Opted-Out | No | “1” indicates that the user has explicitly opted out (otherwise the value should be “0”). If “1”, all fields except Mobile Device ID and ID Type should be empty. | 0 |
Note
Required columns are always populated.
Note
Before hashing, all emails are lowercased and any whitespace is removed.
A set of populated rows might look like this:
AEBE52E7-03EE-455A-B3C4-E57283966239|IDFA|"Mozilla/5.0 (iPhone; CPU iPhone OS7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53" | 208.185.26.20|1441137534|3cb7232fcc48743000cb86d0d5022bd9|||0
AEBE52E7-03EE-455A-B3C4-E57283966239|IDFA|"Mozilla/5.0 (iPhone; CPU iPhone OS7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53" | 208.185.26.20|1441137534||790d12777b2a83253a14c748a1b1cb09b3a91cca||0
AEBE52E7-03EE-455A-B3C4-E57283966239|IDFA|"Mozilla/5.0 (iPhone; CPU iPhone OS7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53" | 208.185.26.20|1441137534|||899d3387a5c5a7555d51d2f0a0b7b50e397fe481fd9a58fafb389b7dc94e11f6|0