> ## Documentation Index
> Fetch the complete documentation index at: https://developers.criteo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

<table>
  <thead>
    <tr>
      <th>
        <p>
          Endpoint
        </p>
      </th>

      <th>
        <p>
          Use case
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          <code>
            GET /marketplace-performance-outcomes/stats/campaigns
          </code>
        </p>
      </td>

      <td>
        <p>
          Template-level aggregation across all sellers
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <code>
            GET /marketplace-performance-outcomes/stats/sellers
          </code>
        </p>
      </td>

      <td>
        <p>
          Per-seller aggregation across campaigns
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <code>
            GET /marketplace-performance-outcomes/stats/seller-campaigns
          </code>
        </p>
      </td>

      <td>
        <p>
          Per seller-campaign (most granular)
        </p>
      </td>
    </tr>
  </tbody>
</table>

You can find full endpoint details in the\
[Marketplace Performance Outcomes – Stats Reference](/marketing-solutions/reference/campaign/get-marketplace-advertisers).

### Choosing the right identifiers

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

<table>
  <thead>
    <tr>
      <th>
        <p>
          Identifier
        </p>
      </th>

      <th>
        <p>
          When to use
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          <code>
            campaignId
          </code>

          (template)
        </p>
      </td>

      <td>
        <p>
          Filter stats for all sellers under a specific template
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <code>
            sellerId
          </code>
        </p>
      </td>

      <td>
        <p>
          Filter stats for a specific seller across templates
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <code>
            sellerCampaignId
          </code>
        </p>
      </td>

      <td>
        <p>
          Filter stats for a specific seller on a specific template (most precise)
        </p>
      </td>
    </tr>
  </tbody>
</table>

### 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**.