Demand Reporting

In this article, you will learn what reports are available to demand partners and how they can be delivered.

Available Reports

Discrepancy Data

The discrepancy data report aims to assist in identifying discrepancies in impressions, wins, or revenue. The data is broken into traffic segments by publisher, platform, and creative type.

Field	Description
date	The UTC day.
demand_source	The Nimbus keyword for the demand source.
publisher	The Nimbus keyword for the publisher.
placement	The placement ID—sent as tagid in the RTB bid request.
app_platform	android, iphone, or ctv
creative_type	static, video, or native
impressions	The number of successful impressions for the traffic segments.
wins	The number of auctions won for the traffic segment.
revenue	The publisher revenue for the traffic segment.

discrepancy_data_2023-01-01.csv

"date","demand_source","publisher","placement","app_platform","creative_type","impressions","wins","revenue"
"2023-01-01","some_demand","some_publisher","some_publisher_static_android","android","static","12345","23456","42.42"
"2023-01-01","some_demand","some_publisher","some_publisher_static_iphone","iphone","static","12345","23456","42.42"
"2023-01-01","some_demand","some_publisher","some_publisher_video_android","android","video","12345","23456","42.42"
"2023-01-01","some_demand","some_publisher","some_publisher_video_iphone","iphone","video","12345","23456","42.42"

CRID Data

The CRID data report aims to assist in debugging discrepancies in impressions, wins, or revenue. The data is broken into traffic segments by the publisher and creative ID.

date	The UTC day.
demand_source	The Nimbus keyword for the demand source.
publisher	The Nimbus keyword for the publisher.
crid	The creative ID—sent as crid in the RTB bid response.
impressions	The number of successful impressions for the traffic segments.
wins	The number of auctions won for the traffic segment.
revenue	The publisher revenue for the traffic segment.

crid_data_2023-01-01.csv

"date","demand_source","publisher","crid","impressions","wins","revenue"
"2023-01-01","some_demand","some_publisher","crid_12345","42","55","0.12"

Delivery

AWS S3

Reports can be delivered to an S3 bucket daily. Each day's data is separated into a single file.

from_nimbus/discrepancy_data_2023-01-01.csv
from_nimbus/discrepancy_data_2023-01-02.csv
from_nimbus/discrepancy_data_2023-01-03.csv
from_nimbus/crid_data_2023-01-01.csv
from_nimbus/crid_data_2023-01-02.csv
from_nimbus/crid_data_2023-01-03.csv

Reports are generated for a rolling 3-day window, meaning previously delivered reports may be “trued up”.

The S3 bucket can be Nimbus or partner-owned. Please work with the Nimbus team to determine the best option and configure access.