Skip to main content
Supply Side Revenue Report (v2)

Introduction

The revenue report serves as a vital tool for supply account owners, such as retailers, enabling them to understand the origins of their retail media revenue. It offers comprehensive visibility across all advertisers, media platforms, and sales channels, encompassing direct, indirect, and private market avenues. This report delves into crucial aspects, including generated revenue, delivered impressions, clicks, average rates, and overall performance metrics. Through this API only, supply partners gain the ability to construct detailed reports by accessing several metrics and dimensions.
Default settingsWhen a retailer wants to view their default settings (as used in the user interface), we suggest constructing their API request or data call using the same default parameters that the UI uses. The specific default values used by the system are documented in Criteo Help Center.

Endpoints

The report generation uses an asynchronous endpoint that is used to receive the report creation request (using a POST request). Then, using the report id generated, it’s possible to check the report status and to download the output results using the following GET endpoint requests.

Attributes

Metrics and DimensionsFor a complete list of all supported metrics and dimension, check out the Metrics and Dimensions
When utilizing the clickMatchLevel and viewMatchLevel fields, we recommend including the attributionSettings, activityType, and skuRelation. This will assist in gaining a clearer understanding of the click and view events, categorized by their attribution windows and SKU relationships.

Generate Revenue Report

Sample Request

Sample Response


Get status of specific report

Sample Request

Sample Response


Download Output of a Specific Report

Sample Request

Sample Responses

Report broken down by advertiser by JSON format

Responses

ResponseDescription
🔵 200Call executed with success
🔴 400Common Validation Errors:
  • endDate cannot be more than 100 days fromstartDate - Using a date range with more than 100 days apart
  • reportTypeinvalid - calling an unsupported report type will throw a 400 error
  • timeZonemust be a valid timezone - using a time zone value that is not listed in the list tz database time zones
  • format invalid - using an unsupported file format