Your hub for revenue and demand reporting
The Reporting Tab is an easy-to-use reporting feature native to the Commerce Grid UI.
Combining demand insights from both first- and third-party demand sources (i.e. Criteo DSPs and non-Criteo DSPs, respectively), the Reporting Tab puts the reports with the highest impact right at your fingertips.
Read on to learn how to pull reports.
1. Choose a date range
Select a reporting range via the dropdown in the top left-hand corner.
Choose a custom reporting time frame by clicking dates on the calendar, or use pre-determined reporting windows via the “Current Period” dropdown (options include “previous week,” “previous month,” “this month,” etc.).
In addition to selecting a reporting date range, users can select a timezone, and a data aggregation, which aggregates the granularity of the data (i.e. hourly, daily, monthly, etc.)
Note: Same-day revenue data is available, however it is delivered on a delay of up to ~7 hours for third-party DSPs, and up to 15 hours for Criteo DSPs.
2. Select a report
Report types are accessed via the dropdown in the top right corner. These filters allow for the isolation of different reports, including various demand, inventory, and user reports.
Below is a table of all available report types:
Report | Description | Use case example | Guardrails |
|---|---|---|---|
Date | Review data metrics by calendar date. |
|
|
Network ID | Reveals revenue reporting at the Network ID level. | Publishers want to understand which of their Networks is driving the most revenue. | Network ID implementation varies by customer. |
Media Type | Access revenue reporting across different media formats (display, video, native, etc.) | Publishers want to understand which media type is driving the most revenue. |
|
Inventory Group | Access revenue reporting at a customer’s different Inventory Group levels. | Publishers want to understand which of their inventory groups is driving the most revenue. | Inventory Group implementation varies by customer. |
Ad Unit ID | Access revenue reporting broken down by the Ad Units they are monetizing with CGrid. | A publisher wants to understand which ad units are driving the highest revenue. | Note: Ad Units are an optional function of the Commerce Grid inventory scheme. Until a publisher has broken out Ad Units within their inventory management schema, only one category “unknown” will show here. Click here for more. |
Publisher Domain | Access revenue reporting at the domain level. | A publisher wants to understand which of their domains is driving the highest revenue. |
|
App Bundle | Access revenue reporting at the app bundle level. | A publisher wants to understand which of their app bundles is driving the highest revenue. |
|
DSP | Access revenue reporting broken down by DSP. | A publisher wants to know which DSPs are driving the highest revenue so that they can create deal packages for that DSP. | As noted in the “Data Visualization” section above, the data viz only displays six options at a time. If a DSP is greyed out, it does NOT mean a pub isn’t receiving traffic from that DSP, it just means it’s not being visualized. |
Inventory Type | Access revenue reporting broken down by the channel through which a user is accessing a publisher’s inventory (i.e. web, app, etc.) | A publisher wants to understand fill rates across web and app traffic for optimization purposes. |
|
Publisher Sub ID | Access revenue reporting at the Publisher Sub ID level. |
|
|
Creative Size | Access revenue reporting broken down by creative size. | A publisher wants to understand which ad sizes are driving the highest revenue. | Publishers who aren’t using Ad Units but want creative size should use this field. If a customer wants non-standard tracking of sizes, they should use Ad Units. |
Browser | Access revenue reporting broken down by the user’s browser | A publisher wants to understand which browsers are driving the highest revenue. |
|
Device Type | Access revenue reporting broken out by user device type | A publisher wants to understand its fill rate across device types for optimization purposes. | Currently device categories include:
|
OS | Access information about a publisher’s traffic based on device operating system. | A publisher wants to understand which OS are delivering the highest number of ad revenue. |
|
Country | Access information about the location of a publisher’s traffic at the country level | A publisher wants to understand which countries its delivering the highest number of impressions in. | Countries are currently presented as 2-digit IBAN country codes. Refer to this chart for a full list of 2-digit country codes. |
3. Understanding the data visualization
A key component of the Reporting Tab, the visualization displays a chart that updates based on the reporting parameters selected.
When toggling through the various report types, the visualizer will allow a user to highlight or unhighlight different pieces of data (see associated screenshot). The visualization also changes based on the date range selected.
The visualization can be hidden by deselecting the “view chart” checkbox.
Note: There is currently a limitation of six lines available for visualization on the chart. Just because a selection is greyed out does NOT mean there is no data for it. To see the visualization for a greyed item, deselect another item before trying to select a greyed-out item.
4. Toggle desired metrics
The data visualization can be presented with different metrics, which can be selected via the dropdown in the upper left, underneath the date range selector.
All available data metrics are also presented in the table below the visualization.
Available metrics:
Metric Name | Description | Guardrails |
|---|---|---|
Requests | The number of ad requests made. | Previously called “Bids” in Reporting Tab. |
Impressions | The number of impressions rendered. |
|
Revenue | The revenue that a publisher has earned. | Revenue data presented in the Reporting Tab does NOT include media adjustments (including fees and “clawbacks”). Publishers should be aware that monthly Payout Statements, which reflect these fees, will look different than the revenue data presented in the Reporting Tab. |
CPM | The average CPM that a publisher has earned. |
|
Participations | The percentage number of ad requests answered divided by the number of ad requests sent. |
|
Win Rate | The percentage number of impressions rendered over the number of ad requests. |
|
5. Downloading reports
Export data by downloading it to a .csv file.
Indicate the desired reporting date range, and report type before selecting the “Download Report” button (all available metrics will be included by default).
Once selected, a .csv file will download and become available for use in a desired spreadsheet editor.
6. Coming Soon: Multicurrency Support
Multicurrency support refers to the ability to convert revenue data into a non-USD currency.
Since its release, revenue data in the Reporting Tab has only been available in USD. As of July 15 2025, reporting data will be available in several currencies (as shown in the table below).
Reporting Tab users will see the currency selector and data prior to the July 15 2025 release date, but should not actively select non-USD currencies for reporting until the July 15 2025 release date as the data may contain significant discrepancies.
Currency |
|---|
United States Dollar ($) |
Canadian Dollar ($) |
Euro (€) |
Great British Pound (£) |
Japanese Yen (¥) |
Korean Won (₩) |
Turkish Lyra (₺) |
7. Commerce Grid Reporting API
The Commerce Grid Reporting API is an API service that allows for access to performance and inventory management data via the Reporting Tab in an automated fashion.
The Commerce Grid Reporting API was designed to replace the legacy PMC API. If you are a u-Slicer user, you should continue to use the u-Slicer Reporting API instead of the Commerce Grid Reporting API.
Designed to be more streamlined and modern than the previous PMC Reporting API, the Commerce Grid Reporting API introduces a fresh structure with its own Request and Response formats to make things cleaner and more consistent moving forward.
Frequently Asked Questions
I was previously working in PMC. Does this reporting solution provide similar functionality?
The Reporting Tab, and data structures therein, were developed similarly to PMC, and designed to deliver the most essential revenue and demand reports, across consolidated (first- and third-party) demand sources. The information presented in the UI, including metrics and data filters, should be extremely familiar to PMC users.
I’m trying to use the Data Visualization in the Reporting Tab, but I see a bunch of greyed-out data. Does this mean that data is irrelevant, or not included?
Currently, there is a maximum of six lines available for visualization. Some reports, such as the DSP report or user Geolocation report may have hundreds of potential data lines. When these types of reports are presented, all but six lines will be greyed out (defaulting to the six top performers in a given report) - this does not mean the greyed-out data is not included. To visualize the greyed-out data deselect one of the currently selected options and select your desired line.
If you’d like to see all data lines at once, use the Data Table below the Visualization, or download the report and view it in Excel.
I'm running deals in Commerce Grid. Is there a way to see data isolated by Deals?
Basic deal performance data is available to publishers in the CGrid UI by navigating to “Demand Deals” in the Trading Tab, and reviewing the metrics (Impressions, Bid Rate, etc.) on the right of the Deals table.
For more advanced Deal Reporting use cases, publishers will be granted access to Deals Reporting in u-Slicer (bsw-adc). Please contact your Commerce Grid service team if you are running deals and need access to this service.
I am an API user. Is there a new CGrid API endpoint?
As of June 2025, the Commerce Grid