Skip to main content

​
Introduction

This guide provides a consolidated reference to the reporting endpoints, permissions, and data behaviors. It’s designed to operate as a practical guide for understanding how SSP and DSP reporting works, how to align API results with the UI, and how to navigate rate limits, data latency, and reporting discrepancies. You can use it as a companion resource when building or troubleshooting your Retail Media API integrations.
Reporting EndpointsYou can find out more on our reporting endpoints in the following sections:

​
Reporting Suite & Permissions

​
SSP (Retailer permission)

The SSP Reporting suite provides retailer-level analytics to help understand the sources of Retail Media revenue. Access to the following report types requires API consent for a Supply/Retailer account:

​
Revenue Report

Provides retailer-level visibility into monetization revenue and its sources across advertisers, platforms, and sales channels.

​
Fill Rate Report

Shows how much of your inventory is filled with ads across placements, page types, and platforms to help identify opportunities to grow demand and revenue.

​
DSP (Brand/Seller permission)

The DSP Reporting suite provides analytics across Brand or Seller accounts, scoped by account, campaign, or line item. Access to the following endpoints requires API consent for a Demand Brand/Seller account.

​
Performance Report

Flexible performance reporting — impressions, clicks, spend, attribution, video, and more — at any account, campaign, or line-item scope. See Performance Report.

​
Real-Time Performance Report

Synchronous, near real-time performance data (impressions, clicks, spend) with a 7-day lookback, for live monitoring and alerting. See Real-Time Performance Report.

​
Missed Opportunities Report

Budget cap-out and missed-delivery diagnostics for line items that exhausted their budget or missed eligible auctions. See Missed Opportunities Report.

​
Attributed Transactions Report

Transaction-level log of every purchase attributed to a campaign. See Attributed Transactions Report.
DSP reporting has no reportType field or preset report shapes — every endpoint above is metrics-and-dimensions based, and you always specify metrics[] and dimensions[] explicitly. If you’re moving from the legacy reportType-based endpoints, see the migration guide.

​
Flexible Reporting (SSP)

SSP reporting endpoints still support reportType — pre-packaged report shapes with a limited, fixed set of metrics and dimensions. Instead of using one of the report types, omit reportType from the request and use metrics and dimensions to customize the data returned.
See Metrics and Dimensions (SSP) for the full list of available metrics and dimensions.
Please omit product-level metrics for Sponsorships and Onsite Display campaigns when selecting metrics and dimensions, whether on DSP’s dimensions[] arrays or SSP flexible reporting. These metric-dimension combinations are not supported for these campaign types and may return incomplete or misleading results.
  • Keyword reporting can misalign with the UI due to filtering logic used to support platform performance. UI exports do not rely on this logic and align with API data. Only applies to search pages.
  • Categories are standardized across brands and retailers, which may differ from retailer-specific categories.

​
Comparing Sources (API vs UI)

When comparing API reporting to the Criteo platform (UI), consider the following details when aligning settings.

​
API vs UI Default Settings Overview

Field

UI Default

API Default

clickAttributionWindow

SSP Revenue: Onsite 14D

Sponsored Products 30D

DSP report: campaign attribution settings

Campaign attribution settings

viewAttributionWindow

SSP Revenue: Onsite 14D

Sponsored Products 1D

DSP report: campaign attribution settings

Campaign attribution settings

clickMatchLevel

SSP Revenue:sameCategory

DSP report: campaign attribution settings

Campaign attribution settings

viewMatchLevel

SSP Revenue: OnsitesameCategorySponsored ProductssameSku;

DSP report: campaign attribution settings

Campaign attribution settings

timeZone

Account default

UTC

startDate/endDate

Last 7 days

Required

salesChannel

Campaigns Tab: online only;

Analytics Tab: online + offline

Online + offline

​
Attribution

  • set the API viewAttributionWindow + clickAttributionWindow to match the campaign settings
or
  • omit both from the API query and the API will default to campaign settings for both the DSP and SSP reports
or
  • Align to the SSP Revenue report attribution settings above (UI defaults can differ from campaign-level settings).

​
Timezone

  • The UI uses the account timezone. In the API, set timeZone to the account’s IANA timezone.
  • If you omit timeZone, the API defaults to UTC (not the account timezone).

​
Sales Channel / Offline Sales

  • The UI Campaigns tab excludes offline sales; the Analytics tab includes offline sales (and can be filtered).
  • If the API request omits salesChannel, it includes both online + offline sales by default.
  • For parity/completeness, prefer the UI Analytics view.

​
Metrics + Dimensions

  • Ensure both UI and API use the same metrics and breakdowns (dimensions).
  • On DSP endpoints, specify metrics[] and dimensions[] directly to match the UI breakdown. On SSP endpoints, use an API reportType or omit it and specify metrics/dimensions directly.

​
Data Availability, Retention & Limits

​
Data Availability

Metrics may have several hours of latency and different types of activity and attribution data become available at different times after the event or sale. Maximum delay values are not guaranteed, and the times below reflect the 95th and 50th percentile latency.
Different types of activity and attribution data become available at different times after the event or sale:
  • Onsite activity data is typically available within 6–8 hours of the event.
  • Offsite activity data is typically available within 24 hours of the event.
  • Initial attribution data is available within 7–9 hours of the sale.
  • Final attribution data is processed and posted within 74 hours after the sale.
  • Please note that potential minor updates can occur up to 120 hours before finalization
Please note that data is processed and batched hourly, so same-day data may be partially available.
Please note data may be slightly misaligned for fresher periods because sources vary across reports (SSP API, DSP API, UI Analytics modules). Data should align on finalization.

​
Retention

Reporting data is retained for a rolling 3-year period.

​
Caching Logic

  • Reporting responses may be cached to balance availability and performance.
  • Reports with an end date of today or yesterday are cached for 1 hour.
  • Reports with an end date older than yesterday are cached for 24 hours.
  • The exact cache expiration time is provided in the expiresAt field of the /status response.
  • Reports support a maximum window of 100 days per request across DSP reporting endpoints, regardless of whether you scope by account, campaign, or line item.
  • Use bulk calls to pass up to 50 IDs at a time when pulling data across a large number of Campaigns or Line Items.
  • Report size is capped at 100k rows
  • Hitting this limit will truncate data and produce incomplete results. Narrow the parameters by requesting fewer Campaigns or Line Items in report filters, shortening the date range, or adjusting the report dimensions until the result set falls within the limit.
  • If you encounter a 429 Too Many Requests error, implement exponential backoff logic to pause and retry requests after a delay, giving the API time to reset the application’s limit before attempting again. More details on rate limits on this page and in the table below.

OAuth Method

Rate limit

Rate limit applies at level

Client Credentials

250 callsper minute for default endpoints

40 callsper minute for reporting endpoints

Application level

Authorization Code

10 callsper minute

Account


​
What’s next