Skip to main content

​
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

Endpoint

Use case

GET /marketplace-performance-outcomes/stats/campaigns

Template-level aggregation across all sellers

GET /marketplace-performance-outcomes/stats/sellers

Per-seller aggregation across campaigns

GET /marketplace-performance-outcomes/stats/seller-campaigns

Per 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:

Identifier

When to use

campaignId(template)

Filter stats for all sellers under a specific template

sellerId

Filter stats for a specific seller across templates

sellerCampaignId

Filter 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.