Reporting Oracle Data Cloud Third-Party Data Usage for Twitter
If you use Oracle Data Cloud third-party data for advertising on Twitter, your reporting requirements are slightly different from those for other platforms. Your reports need to include the information in the following table instead of the information mentioned in the following document: Reporting Oracle Data Cloud Third-Party Data Usage. Follow the standard instructions aside from that difference.All reports should be emailed to your account manager and to odc_partner_reports_us_grp@oracle.com.
In this topic
Billing Attribution
If an Oracle Data Cloud audience is used in an Ad Group, you are required to provide reporting that accounts for a daily Ad Group view. This ensures that audience usage is properly accounted for when an Oracle Data Cloud audience is used for a portion of the billing month. The percent of media rate of the most expensive Oracle Data Cloud audience in the Ad Group (premium or standard) should be applied to the entire Ad Group spend regardless of audience mix or usage. This logic applies when audiences are used for inclusions or exclusions. There are two audience types, Premium and Standard. Audience usage is billed based on the designated rate. The audiences included in each type are outlined in the following list.
- Premium Audiences: B2B, Claritas/Nielsen, comScore, CPG, MasterCard, Polk Auto, Retail, TransUnion, Visa, all Oracle custom audiences.
- Standard Audiences: BuyerProfile, Consumer Tech, Demos, Finance, Hobbies and Interests, Philanthropy, Politics, Proximity, Seasonal, Subscription Services, Telecommunications and Travel.
Reporting Requirements
| Col # | Entries | Required/Optional | Description |
|---|---|---|---|
| 1 | ActivityDate | Required | The month of reported usage. We recommend tracking usage on a daily basis to ensure accurate spend throughout the month, but monthly spend should be aggregated at the audience level within each ad group. Please use YYYY-MM format. |
| 2 | PartnerID | Required | A client-specific identification number. Contact your Oracle Data Cloud representative to find this value. |
| 3 | Impressions | Required | The number of impressions served for the specified audience. |
| 4 | CountryID | Required | Enter US. Twitter audiences can be used only in US-based campaigns. |
| 5 | Device Type | Required | Enter a. |
| 6 | Account ID | Required | The ID of the Twitter account that belongs to the advertiser. |
| 7 | Advertiser Name | Required | The name of the advertiser utilizing the data. |
| 8 | Campaign ID | Required | The ID of the Twitter campaign. |
| 9 | Campaign Name | Required | The name of the Twitter campaign. |
| 10 | Media Spend | Required | The total gross amount you spend on media in connection with Twitter Ad Groups that include Oracle Data Cloud audiences. This value must be specific to each individual audience. Iif multiple audiences are used in an Ad Group, you must divide the Media Spend equally among all Oracle Data Cloud audiences used in the Ad Group. |
| 11 | Product Type | Required | Enter 1. |
| 12 | Pricing Type | Required | Enter 5. |
| 13 | Data Fee Total | Required | The dollar amount you owe to Oracle Data Cloud for the use of audiences. Calculated by applying Data Fee % to Media Spend. |
| 14 | Audience Name | Required | The name of the audience. Each Oracle Data Cloud audience should be on a separate line, regardless of how it was combined within an Ad Group. The name should start with ODC-S or ODC-P. |
| 15 | Twitter Audience ID | Required | The Twitter ID of the audience. Each Oracle Data Cloud audience should be on a separate line, regardless of how it was combined within an Ad Group. |
| 16 | Ad Group ID | Required | The ID of the Twitter Ad Group. |
| 17 | Data Fee % | Required | The Twitter Digital Audience Fee applied to an Ad Group for use of Oracle Data Cloud audiences. Rates are included in Exhibit 1 of the Twitter Addendum on the Digital Audiences Ordering Document. |