## Introduction

In this page you will find all the metrics and dimensions that are currently support with the [Revenue Report](https://developers.criteo.com/retail-media/docs/revenue-report-ssp). Please note that many of the metrics and dimensions listed here are currently supported only through the API.

---

## Dimensions

| Dimensions | Description |
| --- | --- |
| `date` | The date of when reported activity took place occurred |
| `hour` | The hour of the day when rendered ad received an event |
| `parentAccount` | The associated account that is connected to the supply or demand account |
| `accountId` | The computed and unique identifier of the supply or demand account |
| `accountName` | The supply or demand account name |
| `accountTypeName` | The account type of the reported activity. Options will include:<br>- `Demand`\- for revenue generated from an indirect sold or private market demand account.<br>- `Supply`\- revenue was generated from direct sold campaigns |
| `advertiserType` | The advertiser account type where the ad activity originated from. Options includes:<br>- `retailer`\- ad activity sold directly in the supply account<br>- `brand`\- ad activity sold to a demand brand account in the Criteo network or through private market<br>- `seller`\- ad activity sold to a demand seller account in the Criteo network or through private market |
| `campaignId` | The computed unique campaign identifier of the demand or supply account that generated the activity |
| `campaignName` | The campaign name of the demand or supply account that generated the activity |
| `campaignTypeName` | The campaign type available. Available options are`Open Auction`or`Preferred Deals` |
| `campaignStartDate` | The start date set for the campaign |
| `campaignEndDate` | The end date set for campaign |
| `lineItemId` | The computed unique identifier of a line-item |
| `lineItemName` | The line-item name provided by the advertiser |
| `lineItemStartDate` | The start date set for the line-item |
| `lineItemEndDate` | The end date set for the line-item |
| `lineItemStatus` | The status of the line-item associated with the selected dimension, such as the date or hour indicating of when the event took place. |
| `retailerId` | The retailer ID that is associated with the report activities . This will be the same`id`provided in the API call |
| `retailerName` | The retailer name that is associated to the report activity. |
| `brandId` | The brand ID provided by the retailer brand ID associated with the advertised SKU |
| `brandName` | The retailer brand name associated with the advertised SKU |
| `placementId` | The id of the placement where the ad creative was displayed. |
| `placementName` | The name of the placement where the ad creative was displayed. |
| `pageTypeName` | The page type where the ad was rendered |
| `environment` | The environment where the ad was rendered on. Options will include web, mobile and app |
| `soldBy` | The source of where activities originated from. Options will include`Direct Sold`,`Indirect Sold`or`Private Market` |
| `buyType` | The campaign buying strategy. Options will include`auction`,`preferredDeals`, or`sponsorship` |
| `salesChannel` | Sales channel the attributed purchase was made through.<br>Available options are:<br>`online`<br>- for sales attributed to an ad that was served and purchased online or in-app<br>`offline`<br>- for sales to an ad that was served online but purchase in store |
| `attributionSettings` | The lookback click and view attribution window of the requested report. The attribution window is based on the parameters selected in the report API request. The`attributedSettings`field will be based on the lookback windows provided in the API call.<br>**Post-Click (C) lookback window**<br>none, 7, 14, 30 days<br>**Post-view (V) lookback window**<br>none, 1, 7, 14, 30 days |
| `activityType` | The type of ad engagement the sale was attributed to. Available options will include`imp`for impressions or`click`for clicks |
| `keyword` | Keyword or phrase used to land on the search page where an ad creative rendered. |
| `skuRelation` | Attribution rule used to match the impression or click to a sale. Available options are:`Same SKU`,`Same Parent SKU`,`Same Category`,`Same Brand`or`Same Seller` |
| `advProductId` | Advertised product ID; this references the same product ID of the retailer Catalogs |
| `advProductName` | Advertised product name |
| `advProductGtin` | Advertised product GTIN |
| `advProductMpn` | Advertised product MPN |
| `pageCategory` | The retailer defined category of the page where ads are rendered |
| `retailerCategoryId` | The retailer category provides the type of product the SKU belongs to. This fields provides the id of that product type |
| `retailerCategoryName` | The name of that product type |
| `taxonomyBreadcrumb` | The category breadcrumb of the product using retailer product taxonomies (L1, L2 L3 etc.). This is for analysis where SKUs are present in the displays |
| `taxonomy1Id`<br>`taxonomy2Id`<br>`taxonomy3Id`<br>`taxonomy4Id`<br>`taxonomy5Id`<br>`taxonomy6Id`<br>`taxonomy7Id` | The ID SKU’s taxonomy. The revenue report provides the option to select level 1 through level 7.<br>ℹ️ **Note**: SKUs will normally have at least the primary sku taxonomy (L1). All following levels are considered additional taxonomies. If a SKU does not have an additional taxonomy level, the report will default to`unknown` |
| `taxonomy1Name`<br>`taxonomy2Name`<br>`taxonomy3Name`<br>`taxonomy4Name`<br>`taxonomy5Name`<br>`taxonomy6Name`<br>`taxonomy7Name` | The name SKU’s taxonomy. If a SKU does not have an additional taxonomy level, the report will default to`unknown` |
| `targetedKeywordType` | The conquesting ad strategy used with the keywords. Output values of this dimension includes:<br>`Conquesting`– Search terms the line item uses to target competitors’ branded keywords.<br>`Branded`– Search terms the line item uses to target its own branded keywords.<br>`Generic`– Search terms that are neutral or non-branded, targeted by the line item.<br>`Unknown`– Search term and SKU pairs that don’t have a defined conquesting type. These are typically keywords used before a conquesting strategy was implemented. |

---

### Metrics

| Dimensions | Description |
| --- | --- |
| `numberOfCampaigns` | the total count of campaigns associated with the selected report dimension. |
| `numberOfLineItems` | The total count of line-items associated with the selected report dimension. |
| `numberOfSkus` | The total count of skus associated with the selected report dimension. |
| `skuPrice` | The total price of each SKU unit.<br>- _Note_\*: It is recommended to utilize metrics such as`advProductId`,`advProductGtin`, and`advProductMpn`to access individual SKU prices. However, when considering other dimensions at the line-item, campaign, or account level, the sum of all SKU prices will be calculated. |
| `pageViews` | The count of unique ad calls on a retailer network. Use this metric when referencing to dimensions that relates to itself to receive a more comprehensive data. Using dimensions such as`pageTypeName`,`placementId`or`placementName`will provide you data to understand the performance of this metric. |
| `impressions` | An impression represents each time an ad renders on a page, regardless of clicks or views.<br>An impression for a Sponsored Product ad is when the sponsored SKU renders on the page (the product being the ad).<br>An impression for a Commerce Display ad is when the entire banner (creative + product) renders on the page.<br>An impression for a Display banner ad is when the creative banner renders on the page. |
| `productClicks` | Total count of the click events that occur when a user clicks a product in a placement |
| `placementClicks` | Total count of the click events that occur when a user clicks a placement |
| `clicks` | The total count of all click events<br>- _Formula_\*: `placementClicks`<br> \<br> \<br> \<br> `productClicks` |
| `sales` | The total attributed revenue from product sales |
| `units` | The total attributed product units sold |
| `assistedSales` | Sales revenue attributed to a click or impression of all the ads that appeared on a page within the chosen attribution window (specified at the campaign level) but were not determined to be the`attributedSales`(the last ad before the customer purchased). |
| `assistedUnits` | The number of events that occurred that helped generated a sale. Assisted units are excluded from`attributedUnits`. This means its not counted in the attributed units calculation |
| `openAuctionRevenue`( _deprecated_) | The total amount of sponsored products revenue generated on the set date, not including sponsorships. |
| `preferredDealsRevenue`( _deprecated_) | The total amount of onsite display revenue generated on the set date, not including sponsorships. |
| `sponsoredProductRevenue` | The total amount of sponsored products revenue generated on the set date, not including sponsorships. |
| `onsiteDisplayRevenue` | The total amount of onsite display revenue generated on the set date, not including sponsorships. |
| `revenue` | The total revenue generated on the set date. The`revenue`metric take the total revenue generated across preferred deals or auction campaigns for that period and is computed the same way as the`openAuctionRevenue`and`preferredDealsRevenue`. |
| `transactions` | The total amount of attributed orders/transactions |
| `ctr` | The percentage of shoppers who clicked an ad rendered on a page.<br>Product and Product Category Report Types<br>- _Formula_\*: `clicks`/`productImpressions`<br>All other report types<br>- _Formula_\*: `clicks`/`placementImpressions`<br>- _Note_\*: there are two types of impressions that can be measured to know the success of your ads:`placementImpressions`and`productImpressions`. Preferred deals have placement impressions, while open auction uses product impressions. For more info: [Product & Placement Impression](https://help.retailmedia.criteo.com/kb/guide/en/product-placement-impressions-Yg9vyLMSMS/Steps/2492962) Help Center article |
| `cr` | The number of conversion generated by the visitors to the retailer site.<br>- _Formula_\*: number of conversions /`clicks`\* 100 |
| `cpc` | Average cost-per-click calculated by dividing openAuctionRevenue / clicks or preferredDealsRevenue / clicks |
| `cpm` | Average cost per mille calculated by diving`preferredDealsRevenue`/`impressions`<br>- 1000 |
| `roas` | Return-on-ad-spend (ROAS), calculated by dividing`sales`/`openAuctionRevenue`or`sales`/`preferredDealsRevenue` |
| `workingMedia` | The total spend paid by the brand |
| `netRevenue` | The total revenue from brand spend for the retailer |
| `uniqueVisitors` | The number of distinct shoppers exposed to an ad within the reporting period. Each shopper is counted once using the retailer cookie ID.<br>`uniqueVisitors`is an estimate, minor 1% discrepancies can occur.<br>Criteo uses retailer cookie IDs to identify users across sessions on the same device. Each ID can last up to a year, provided the user does not clear their cookies. |
| `frequency` | An average representing how often an impression has been shown to the same user |

The `uniqueVisitors` metric may show discrepancies compared to UI values when querying long time ranges. Due to API limitations, reports can only be retrieved for a **maximum of 100 days per request**. To analyze longer periods, multiple requests must be performed and aggregated client-side.While this approach works for additive metrics (e.g. impressions), it may lead to **double counting** for user-based metrics such as `uniqueVisitors` or `reach`, since the same user can appear in multiple reporting windows. As a result, summing `uniqueVisitors` across multiple requests may produce higher values than those displayed in the UI, where user deduplication is applied across the full time range.

---

### Video Metrics

| Key-Values | Data Type | Description |
| --- | --- | --- |
| `videoViews` | `string` | The number of times at least 50% of the video ad appeared for at least 2 seconds (MRC standard). |
| `videoStarts` | `string` | The number of times one of your video ads started playing. |
| `videosPlayedTo25` | `string` | The number of times one of your videos played to at least 25% of its duration. |
| `videosPlayedTo50` | `string` | The number of times one of your videos played to at least 50% of its duration. |
| `videosPlayedTo75` | `string` | The number of times one of your videos played to at least 75% of its duration. |
| `videosPlayedTo100` | `string` | The number of times one of your videos played to 100% of its duration. |
| `videoPlayingRate` | `string` | The average played percentage of a started video.<br>Formula: Sum of Quartiles x 0.25 / (4 x Video starts) |
| `videoCompletionRate` | `string` | The percentage of started videos that played for their entire duration.<br>Formula: Number of videos that played to completion / Total number of videos started \* 100 |
| `videoStartingRate` | `string` | The percentage of videos printed that started playing.<br>Formula: Video Starts / Placement Impressions |
| `videoMuted` | `string` | The number of times users clicked the “mute” button on your video. |
| `videoUnmuted` | `string` | The number of times users clicked the “unmute” button on your video. |
| `videoResumed` | `string` | The number of times users activated the resume control after the creative had been stopped and paused. |
| `videoPaused` | `string` | The number of times users activated the pause control on the video. |
| `videoViewability` | `string` | The percentage of video ads that were considered viewable. At least 50% of the ad’s pixels must be visible on the screen for at least two continuous seconds (MRC standard). Requires OMID support.<br>Formula: Viewable Impressions / Placement Impressions

---