Accepting Mobile Advertising IDs in your Media Platform
The Oracle CX Advertising platform (formally know as the Oracle Data Cloud platform) can deliver categories (groups of users with the same attributes) into your platform that are associated with a users' mobile advertising IDs (MAIDs), which are also referred to as "device IDs" when derived from mobile apps).
Accepting mobile IDs enables you to offer marketers and advertisers the ability to target mobile app users based on their online behavior. The Oracle CX Advertising platform can deliver user data via server data transfer (SDT) that is associated with identifier for advertisers (IDFA) and Google Advertising IDs (ADID).
Delivery Partners Receiving EU Data. To receive data for user profiles located in the European Union (EU), you must have signed Oracle's General Data Protection Regulation (GDPR) Right to Use agreement. Contact your Oracle Account Representative to obtain and sign the agreement.
To accept mobile IDs in your platform:
- Contact your account manager or customer success manager to set up mobile ID-based delivery.
- Specify the mobile IDs and hashes you accept in your platform.
- Process user data.
- Report data usage.
Configuring delivery of mobile ad ID-based data
To start receiving mobile ad ID-based categories, contact your Oracle CX Advertising account manager or customer success manager to request a new SDT endpoint.
Specifying accepted mobile IDs
You need to notify Oracle CX Advertising about which mobile IDs you accept. The platform then includes only the IDs that you have specified in your SDT data. The platform can send you user data that is associated with the following mobile IDs:
| Key | Mobile ID type |
|---|---|
| adid | Google Advertising ID |
| adidmd5 | Google Advertising ID (MD5) |
| adidsha1 | Google Advertising ID (SHA-1) |
| androididmd5 | Android ID (MD5) |
| androididsha1 | Android ID (SHA-1) |
| idfa | Identifier for advertising (IDFA) |
| idfamd5 | IDFA (MD5) |
| idfasha1 | IDFA (SHA-1) |
Processing user data
You must be able to process the categories and mobile IDs in the user data sent to you via SDT. The following examples demonstrates the user data you can receive via SDT real-time (JSON format) or SDT batch (delimited format):
If you are receiving multiple mobile ad ID types, your SDT data will include an empty mobile ID field for users that do not have that mobile ID type as shown in the following example:
Mobile IDs in SDT real-time data
{
"DeliveryTime": "Fri Jan 17 17:42:35 CST 2017",
"DestinationId": 17284,
"PixelCount": 1,
"Pixels": [{
"IDFA": "AEBE52E7-03EE-455A-B3C4-E57283966239",
"CampaignId": 117162,
"CategoryId": "678298",
"PartnerUuid": "none",
"PixelId": 137438,
"PixelUrl": "https://stags.bluekai.com/site/39966",
"Rank": 33,
"Timestamp": "Fri Jan 17 17:42:34 CST 2017",
"UtcSeconds": 1484696555
}]
}
Mobile IDs in batch SDT data
AEBE52E7-03EE-455A-B3C4-E57283966239 1398380671,210217:22583:1690,210223:22583:1690,210224:22583:1690,210229:22583:1,210233:22583:1690
38400000-8cf0-11bd-b23e-10b96e40000d 1398380671,234989:22583:1690,234993:22583:1690,234984:22583:1690,234985:22583:1,234986:225
AudienceOn reporting
You must report the data usage according to the requirements listed in Reporting ODC 3rd-party data usage. You must include the Campaign ID column (column 6) in your data usage report to specify the campaign targeting the categories listed in the Category IDs column (column 5). Reporting your data usage is required so that Oracle CX Advertising platform can allocate revenue back to the platform’s data providers accurately, efficiently, and in a timely manner.
AudienceON reporting