Getting Statistics

Overview

Single-Seller performance is exposed via the same MPO stats APIs used for multi-seller campaigns. The key difference is using the right combination of identifiers to get data at the correct granularity.

Available stats endpoints

EndpointUse case
GET /marketplace-performance-outcomes/stats/campaignsTemplate-level aggregation across all sellers
GET /marketplace-performance-outcomes/stats/sellersPer-seller aggregation across campaigns
GET /marketplace-performance-outcomes/stats/seller-campaignsPer seller-campaign (most granular)

You can find full endpoint details in the
Marketplace Performance Outcomes – Stats Reference.

Choosing the right identifiers

Use the appropriate combination of identifiers depending on the granularity you need:

IdentifierWhen to use
campaignId (template)Filter stats for all sellers under a specific template
sellerIdFilter stats for a specific seller across templates
sellerCampaignIdFilter stats for a specific seller on a specific template (most precise)

Monitoring after onboarding

After creating a seller's first budget and once the Single-Seller campaign is provisioned:

  • Allow for the asynchronous provisioning delay before expecting impressions.
  • Query GET /marketplace-performance-outcomes/stats/seller-campaigns with:
    • sellerId = the onboarded seller
    • campaignId = the template campaign ID
  • Monitor impression volume and spend; if a productSet is configured, a whitelist with many invalid or inactive IDs may result in under-delivery.