Custom Partner Integrations
This page lists custom integrations between Audience Manager and data partners.
Oracle Data Cloud
Audience Manager ingests cookie and mobile ID data from the Oracle Data Cloud for Audience Marketplace via inbound data files. The custom integration specifications described below refer only to inbound data files that contain mobile IDs (IDFA and Android Device IDs).
Inbound Data Files received from the Oracle Data Cloud differ from the standard inbound file name syntax described in Amazon S3 Name and File Size Requirements for Inbound Data Files and from the standard inbound file content syntax described in Inbound Data File Contents: Syntax, Invalid Characters, Variables, and Examples .
The elements highlighted below are required, in addition to the standard implementation fields for inbound data files. For descriptions of all other standard fields and file name elements, see File Name Syntax and File Content Syntax in the two pages linked above.
ODC file names are structured as:
ftp_dpm_ odc _DPID[_DPID_TARGET_DATA_OWNER]_TIMESTAMP(.sync|.overwrite)[.SPLIT_NUMBER][.gz]
The odc file name element identifies the file as being imported from the Oracle Data Cloud and instructs the Audience Manager inbound file validator to process it as such.
Fields in the ODC inbound data file must appear in the order shown below:
< ID type ><TAB><user ID><TAB><trait ID>,<trait ID>,<trait ID>,...
The ID type can be:
- Android Device ID
Do not send IDFA and Android Device IDs in the same inbound data file.
Sample ODC inbound file
Download the sample file . This file qualifies several IDFAs for the trait ID 38838. You can open this file in a standard text editor or code editor.