Reporting Oracle Data Cloud Third-Party Data Usage

1. Reporting Requirements

Oracle Data Cloud partners are paid on a per-use basis; therefore, each partner must provide us with the data required to allocate revenue back to each data category and to our data providers accurately, efficiently, and in a timely manner. The partner agrees to provide us with a monthly report in a standard format for each integration (AT/BK/CW/DLX) by the 15th day of the following month.

If you plan to use Oracle Data Cloud third-party data in advertising placed on Facebook or Twitter, the reporting requirements are somewhat different. See Reporting Third-Party Data Usage for Facebook or Reporting Third-Party Data Usage for Twitter.

Report Format Requirements

The file must include the following columns in the specified order. For all columns, you must includeblank values if you are not reporting data in them. For example, if you are not reporting the Vendor Segment ID, insert blank values in column 8.

To make reporting data usage easy, download the ODC Rev Rec Reporting 3.1 Template and use it for your reports.

Col #

Entries

Business Division

Required/Optional

Description

1

ActivityDate


Required

The month when impressions occurred (in YYYY-MM format).

2

PartnerID


Required

The Partner ID of the data buyer submitting the report. Contact your account manager for a list of partner IDs.

3

Impressions


Required

Number of impressions for the specified list of campaign, audience, or vendor segment.

4

CPM


Required (except for Rev Share partners)

Cost per thousand (impressions).

5

CategoryIDs

AT

Required

AT Barcode. Example: 325447|

BK

One of columns 5 – 8 is required.

Pipe-separated list of category IDs that were both targeted and used in the audience segment.

DLX

Required

Pipe-separated DLX Segment ID or Fulfillment Code. Example: X1234|A1=True|X56=1|

6

CampaignID


Typically, you provide data in column 5 rather than in these columns.

The ID of a single campaign.

7

AudienceID


The ID of the single audience.

8

VendorSegmentID


The segment ID of the data buyer or audience injection partner. When a client delivers an audience to an audience injection partner, they can supply a vendor segment ID instead of a category ID.

9

CountryID


Required

The ISO 2-letter country code of the country where the data transaction occurred.

10

Device Type


Required

The device type for the impressions. Acceptable values are: m (Mobile), o (Desktop), Tablet, TV, or a (All).

11

AgencyID


Required if you report AgencyName .

The ID of the agency.

12

AgencyName


Required

The name of the agency.

13

AdvertiserID


Required if you report AdvertiserName.

The Client/Channel ID of the advertiser.

14

Advertiser Name


Required

The name of the advertiser purchasing the data.

15

PartnerCampaignID


Required (if available) The campaign ID of the partner.

16

PartnerCampaignName


Required if your reportPartnerCampaignName.

The name of the campaign.

17

Media Cost


Required (if available)

The cost of the media associated with the targeted data.

18

SpendFromCustomer*


Required

The total spend computed and provided by the partner.

19

Product Type


Required

Contact your account manager for information about product types.

20

Pricing Type


Required

 Contact your account manager for information about pricing types.

21

Spend


Admin use only


22

PartnerSegmentName


Required for reports that provide segment name.

The name of the segment provided by the partner. Example: DLX>Retail>Outdoor Gear

23

MediaPartnerName


Required (if available)

The Media Partner or "Buyer" column reported by the partner. Example: Valassis buying data on Google

24 – 32

Flex columns


Optional

Contact your account manager before using these columns.

If there is additional data you want to track, use flex columns. Make sure to place the same data in the same column every month. Example: Partner Business Division.

* Field can be overridden by Admin.

Remember to include a copy of the Raw Report andemail from the partner that your Rev Rec file is based on. This is important to include to tie back revenue.

Adobe Audience Manager report format requirements

The following table lists the reporting requirements for activation of Oracle Audiences on the Adobe Audience Manager platform. The file must include the columns in the specified order. For all columns, you must include blank values if you are not reporting data. For example, if you are not reporting the AgencyName, insert blank values in column 7.

Col # Entries Required/Optional Description
1 Impressions Required Number of impressions for the specified list of campaign, audience, or vendor segment.
2 PartnerID Required The Partner ID of the data buyer submitting the report. Contact your account manager for a list of partner IDs.
3 CPM Required Cost per thousand (impressions).
4 CategoryIDs Required Segment ID
5 CategoryName Required Name of Segment
6 AgencyName If Applicable The name of the agency if applicable
7 Buyer Name Required Contact your account manager for information about pricing types.
8 Spend Required The total spend computed and provided by the partner.
9 Advertiser Name Required The name of the advertiser purchasing the data.
10 ActivityDate Required (Month – Year)
11 Activation Platform Required Platform the data was activated on

Report Naming Requirements

Once you create your monthly file, you need to save it using the following naming convention:

<businessdivision>-<partnerName>-<PartnerID>-yyyy_mm

  • businessdivision: The division associated with the usage. For example: AT, BK, or DLX
  • partnerName. The name associated with your partner seat.
  • partnerID. The unique ID associated with your partner seat.
  • yyyy_mm.The activity date of the report.

For example, if a partner named "YourCompany" with a partner ID of 1234 through DLX systems is reporting their data usage for July activity, the file name would be as follows: DLX-YourCompany-1234-2016-07.

2. Sending your Report to Oracle Data Cloud Finance

Email your report files to Oracle Data Cloud Finance: