Attributed Transactions Report

This endpoint enables Retail Media DSP partners to retrieve a transaction-level log of every purchase event attributed to their campaigns. Each row represents a single attributed transaction and captures the product advertised, the product purchased, the attribution rule applied, and the time elapsed between ad delivery and purchase.

This is not a performance report. Aggregated metrics — impressions, clicks, spend, attributed sales totals — are not available here. Use POST /reports/performance for those.

Primary audience: Data scientists and analysts auditing attribution methodology, understanding cross-sell and halo effects, or analyzing purchase behavior at the transaction level. Not a day-to-day campaign monitoring workflow. The endpoint supports asynchronous report generation. Submit a request, poll for status, and download the output when ready.

Request

POST /2026-07/retail-media/reports/attributed-transactions

Required fields

startDate, endDate, filters, dimensions, and metrics are all required. filters must contain exactly one scope filter (filters.accountIds[], filters.campaignIds[], or filters.lineItemIds[]).

Field	Type	Description
`startDate`	string	Start of the reporting period. ISO 8601 date (`YYYY-MM-DD`). Based on ad delivery date (`advertisedDate`).
`endDate`	string	End of the reporting period. ISO 8601 date (`YYYY-MM-DD`). Must be ≥ `startDate`.
`filters`	object	Required. Must contain exactly one of the scope filters below.
`filters.accountIds[]`	array of strings	Scope to all line items under this account. Mutually exclusive with `campaignIds` and `lineItemIds`.
`filters.campaignIds[]`	array of strings	Scope to all line items under this campaign. Mutually exclusive with `accountIds` and `lineItemIds`.
`filters.lineItemIds[]`	array of strings	Scope to this line item. Mutually exclusive with `accountIds` and `campaignIds`.
`dimensions`	array of strings	Output columns to return. See Dimensions below.
`metrics`	array of strings	Measure columns to return. See Metrics below.

Optional fields

Field	Type	Default	Description
`timezone`	string	`UTC`	Timezone for date fields. IANA format (e.g. `America/New_York`).
`format`	string	`json-compact`	Output format: `json`, `json-compact`, `json-newline`, or `csv`.
`clickAttributionWindow`	string	—	Attribution window for click-based conversions: `none`, `7D`, `14D`, or `30D`.
`viewAttributionWindow`	string	—	Attribution window for view-based conversions: `none`, `1D`, `7D`, `14D`, or `30D`.
`clickMatchLevel`	string	—	Match level for click attribution: `sameSku`, `sameCategory`, `sameBrand`, or `campaign`.
`viewMatchLevel`	string	—	Match level for view attribution: `sameSku`, `sameCategory`, `sameBrand`, or `campaign`.
`filters.mediaTypes[]`	array of strings	—	Filter by media type.

Example request

POST /2026-07/retail-media/reports/attributed-transactions
Authorization: Bearer {token}
Content-Type: application/json

{
  "data": {
    "type": "AsyncAttributedTransactionsReport",
    "attributes": {
      "startDate": "2026-05-01",
      "endDate": "2026-05-07",
      "filters": {
        "campaignIds": ["123456"]
      },
      "dimensions": ["advertisedDate", "advertisedProductName", "purchasedProductName", "advertisedToPurchasedProductRelationship"],
      "metrics": ["attributedSales", "attributedUnits"]
    }
  }
}

Response

A successful request returns 200 OK with a reportId. Poll for status until status is success or failure:

GET /2026-07/retail-media/reports/{reportId}/status
Authorization: Bearer {token}

Download the output when status is success:

GET /2026-07/retail-media/reports/{reportId}/output
Authorization: Bearer {token}

Each row in the report output represents one attributed purchase event.

Metrics

Select measures using the metrics[] array. metrics is required.

Metric	Description
`attributedSales`	Revenue attributed to this transaction in the account’s reporting currency.
`attributedUnits`	Units sold in this attributed transaction.

Dimensions

Select output columns using the dimensions[] array. dimensions is required. The advertised product (advertised*) and purchased product (purchased*) fields together give the bilateral view described below.

Fields marked Retailer catalog only are available only for retailers that provide a product catalog to Criteo. For retailers without a catalog, they are not populated.

Dimension	Description
`advertisedDate`	Date the ad was delivered (`YYYY-MM-DD`).
`advertisedHour`	Hour the ad was delivered (0–23).
`advertisedEngagement`	Type of engagement that triggered attribution: `imp` (impression) or `click`.
`attributionWindow`	Lookback window applied to this transaction. Format: `C{days}V{days}` (e.g. `C14V07`).
`daysDifference`	Days between ad delivery and the attributed purchase.
`advertisedToPurchasedProductRelationship`	Attribution rule that connected the ad to the purchase: `same sku`, `same parent sku`, `same taxonomy`, `same brand`, `same seller`.
`advertisedProductId`	ID of the product that was advertised. References the Catalogs product ID.
`advertisedProductName`	Name of the advertised product.
`advertisedProductCategory`	Category of the advertised product. Standardized categories. Retailer catalog only.
`advertisedProductGtin`	GTIN/EAN/UPC of the advertised product, if available.
`advertisedProductMpn`	Manufacturer Part Number of the advertised product, if available.
`purchasedDate`	Date the attributed purchase occurred.
`purchasedHour`	Hour the attributed purchase occurred (0–23).
`purchasedProductId`	ID of the product that was purchased.
`purchasedProductName`	Name of the purchased product.
`purchasedProductCategory`	Category of the purchased product. Standardized categories. Retailer catalog only.
`purchasedProductGtin`	GTIN/EAN/UPC of the purchased product, if available.
`purchasedProductMpn`	Manufacturer Part Number of the purchased product, if available.
`salesChannel`	Channel through which the purchase was made: `online` or `offline`.
`campaignId`	Campaign ID.
`campaignName`	Campaign name.
`lineItemId`	Line item ID.
`lineItemName`	Line item name.
`retailerId`	Retailer ID where the line item served.
`retailerName`	Retailer name where the line item served.
`pageType`	Type of retailer page where the ad rendered: `home`, `search`, `productDetail`, `category`, `confirmation`, `checkout`, `merchandising`, `deals`.
`keyword`	Keyword on the search page where the ad rendered, if applicable.
`activitySellerId`	ID of the seller responsible for the advertising event.
`activitySellerName`	Name of the seller responsible for the advertising event.
`saleSellerId`	ID of the seller responsible for the sale.
`saleSellerName`	Name of the seller responsible for the sale.

Understanding the advertised vs. purchased product fields

The advertised product (advertisedProduct*) and purchased product (purchasedProduct*) are often the same — but not always. When the attribution rule is same brand, same taxonomy, or same seller, the ad may have driven a purchase of a related product rather than the exact item advertised. Example: An ad for a camping jacket is served. The shopper purchases a different jacket from the same brand. The row will show:

advertisedProductId: the advertised jacket
purchasedProductId: the purchased jacket
advertisedToPurchasedProductRelationship: same brand

This bilateral product structure makes this endpoint useful for cross-sell and halo analysis — you can see exactly which advertised products drove purchases of which other products, and under which attribution rule.

Migrating from `reportType: attributedTransactions`

Replace your existing call on /reports/campaigns or /reports/line-items with a call to this endpoint. Endpoint change:

POST /reports/campaigns   →   POST /reports/attributed-transactions
POST /reports/line-items  →   POST /reports/attributed-transactions

Request shape changes:

Replace the top-level accountId / campaignId / lineItemId fields with a filters object containing accountIds[], campaignIds[], or lineItemIds[] arrays (exactly one scope filter).
Add required dimensions[] and metrics[] arrays to select output columns — the fields listed above are no longer a fixed response schema; you choose which to return.
startDate and endDate are required (date-only YYYY-MM-DD).
Remove reportType: attributedTransactions — it is not accepted on this endpoint.

Field renames: the adv-prefixed fields are now spelled out as advertised* (e.g. advProductId → advertisedProductId, advDate → advertisedDate, advEngagement → advertisedEngagement, advToPurchasedProductRelationship → advertisedToPurchasedProductRelationship). pageTypeName is now pageType.

Introduction

Getting Started

API Troubleshooting

Concepts

Resources

Guides for Retail Media API

Attributed Transactions Report

Request

Required fields

Optional fields

Example request

Response

Metrics

Dimensions

Understanding the advertised vs. purchased product fields

Migrating from `reportType: attributedTransactions`

​Request

​Required fields

​Optional fields

​Example request

​Response

​Metrics

​Dimensions

​Understanding the advertised vs. purchased product fields

​Migrating from reportType: attributedTransactions

Request

Required fields

Optional fields

Example request

Response

Metrics

Dimensions

Understanding the advertised vs. purchased product fields

Migrating from `reportType: attributedTransactions`