Revenue Reporting for Mediation Partners

The following instructions apply to buyers looking to mediate to ONE by AOL: Mobile.

Reporting Requirements

Demand Partners integrating to ONE by AOL: Mobile for mediation must provide us with revenue reporting for publishers. This revenue reporting data is used for three primary purposes:

  1. Consolidated Revenue Reporting: ONE by AOL: Mobile provides daily, consolidated revenue reporting to publisher clients. This allows publishers to access reporting metrics across all demand sources from a single interface.
  2. Optimization Algorithm Input: ONE by AOL: Mobile provides publishers with optimization across demand partners. One of the inputs into our optimization algorithm is the eCPM of an ad source for a particular publisher. In order for this algorithm to be effective, we require accurate and timely revenue reporting.
  3. Reconciliation Reporting­: Discrepancies in the numbers reported by AOL and an ad source are more quickly investigated when both sources appear in one platform.

Accessibility

Reporting data must be available in one of two ways listed below and API integrations are highly preferred:

  • an HTTP API (Web Service)
  • an automated email report

Data Elements

The following data elements are requested in reporting:

Data Attribute Required? Description
Ad Space / Site ID Required The most granular ID (not name) for the site/zone/spot/etc. This ID should be the same ID used in ad requests.
Date Required The date the activity occurred, expressed in GMT
Requests Recommended Total number of requests made for an ad
Impressions Required Number of filled impressions
Clicks Required Number of clicks
Net Revenue Required Net Revenue to ONE by AOL: Mobile
Fill Rate Optional Requests/Impressions
CTR Optional Click-through rate (Clicks/Impressions)
eCPM Optional Effective CPM ((Net Revenue/Impressions) * 1000)
RPM Optional Revenue per Thousand ((Net Revenue/Requests) * 1000)

Data Grouping Reports must be available by day, per site/zone.

Data Format Data must be available in JSON, XML, or CSV.

Report Frequency Reports must be available daily at a minimum. ONE by AOL: Mobile will retrieve or process reports prior to 5am ET of the following day. No limits may be placed on the number of requests sent to reporting APIs.

Reporting Examples

JSON

//adspace ID (or site ID, etc) specified on inbound request
{
   "data":[
      {
		"requests":72861,
		"impressions":20210,
		"clicks":90,
		"revenue":5.418,
		"date":"2011-09-10"
      },
      ...   ]
}

XML

<response>
	<publisher>
		<id> ... </id>
		<adspace>
			<id> ... </id>
			<statistics>
				<date>2011-09-16</date>
				<requests>1234567</requests>
				<impressions>1135376 </impressions>
				<clicks>9834</clicks>
				<revenue>2345.67</revenue>
			</statistics>
		</adspace>
		<adspace ...> <!-- if multiple ad spaces --> </adspace>
	</publisher>
	<publisher ...> <!-- repeat for each publisher... --> </publisher>
</response> 

CSV

AdSpace ID,Date,Requests,Impressions,Clicks,Revenue
abc123,2011-09-10,103847,38746,372,2654.89
...
xyz789,2011-09-15,204887,27635,372,1543.78

Checklist for Demand Partner Reporting

checkbox_blank.png HTTP API (strongly preferred) or automated daily emails with CSV attachment
checkbox_blank.png Date, Impressions, Clicks, Net Revenue fields available
checkbox_blank.png Reports available per site/zone, per day
checkbox_blank.png Data available in JSON, XML, or CSV formats
checkbox_blank.png Data is updated at least daily
checkbox_blank.png Previous day’s data available before 5am ET (10am GMT)
Have more questions? Submit a request