## What MPO is

**Marketplace Performance Outcomes (MPO)** is designed for marketplaces that want to activate and scale **offsite advertising for sellers** through a structured, API-driven workflow. At a high level, MPO gives marketplaces a way to:

- Onboard sellers.
- Control campaign delivery.
- Allocate and manage budgets.
- Monitor performance across sellers and campaigns.

MPO supports two main activation models:

- **Multi-seller** – multiple sellers share the same campaign.
- **Single-seller** – each seller gets a **dedicated ad set/campaign** based on a marketplace-defined template.

These two models are **complementary**, not mutually exclusive:

- **Multi-seller**: pooled activation at scale, especially for long-tail or smaller-budget sellers.
- **Single-seller**: dedicated setup for sellers that need **greater transparency or control**.

* * *

## What makes MPO different

MPO is designed to optimize advertising performance at the **seller level**. Unlike traditional DSP setups, where optimization is typically applied **at campaign level across multiple advertisers**, MPO uses the **seller** as the primary unit of configuration and optimization. In practice:

- Each **seller’s budget** is managed **independently**.
- Budget is spent toward **that seller’s configured objective**.
- Performance is tracked at **seller** and **seller-campaign** level.

This model allows marketplaces to manage many sellers within a shared framework while maintaining **per-seller control and visibility**.

## Why MPO

MPO can be used to:

- Integrate **seller advertising into marketplace workflows**.
- Manage **campaigns, budgets, and sellers programmatically**.
- Access **performance data** across sellers and campaigns.

In short, MPO is designed to support **scalable, API-driven seller advertising** within marketplace environments.

## How MPO works

A typical MPO integration follows this flow:

1. **Identify the advertiser** (your marketplace context).
2. **Create and manage sellers** (via catalog + MPO Sellers endpoints).
3. **Configure seller campaign delivery** (ad sets and templates).
4. **Set and manage budgets** per seller.
5. **Retrieve performance statistics** to optimize and monitor.

Targeting and delivery controls are defined at the **ad set / campaign level**, which determines how campaigns are executed. This structure allows marketplaces to integrate MPO into existing systems while keeping **seller activation and campaign management fully programmatic**.

## Singleseller and multiseller in MPO

MPO supports two complementary activation models:

### Multiseller

- Multiple sellers share one campaign or ad set.
- Simplified structure for **onboarding many sellers quickly**.
- Commonly used for **smaller seller budgets**.

### Singleseller

- **One seller per ad set/campaign**, based on a **shared template**.
- **Dedicated budget per seller**.
- More **granular configuration and reporting**.

### SingleSeller vs MultiSeller MPO campaigns

“Single-Seller” campaigns build on top of the **multi-seller** model where multiple sellers share a single campaign. **When to use each**:

Use **Single-Seller** when:

- Per-seller budget control is required.
- Granular per-seller performance tracking and troubleshooting are needed.
- Specific sellers need dedicated configuration or reporting.

Use **Multi-seller** when:

- Onboarding many sellers quickly is a priority.
- Seller budgets are small or highly variable.
- A pooled setup is sufficient for business goals.

_For more detail, see the public guide:_

_[MPO Single Seller Campaigns](https://developers.criteo.com/marketing-solutions/docs/single-seller-campaigns)._

* * *

## What You Can Do With the MPO API

The MPO API includes endpoints for:

- **Advertisers**
- **Sellers**
- **Seller campaigns**
- **Budgets**
- **Statistics**

These APIs allow marketplaces to:

- Automate **seller advertising workflows**.
- Integrate MPO deeply into **internal systems** (e.g., marketplace UI, data warehouse, reporting).
- Build custom orchestration, monitoring, and optimization logic on top of Criteo delivery.

* * *

## Optimization Strategies

MPO supports multiple optimization strategies, allowing marketplaces to align campaign delivery with different seller goals. Campaigns can be configured to optimize for:

- **Sales / revenue**
- **Conversions**
- **Leads**
- **Traffic / landing visits**
- **Click volume**

These strategies can be selected depending on:

- The seller’s **objective** (performance vs scale).
- The seller’s **stage in the funnel** (prospecting vs retargeting vs always-on).

* * *

## How to Use this Documentation

Use this page as the **entry point** to MPO. Then continue with the documentation that matches your integration and use case:

- **Single-seller documentation**:
  - Concepts and entities for Single-Seller.
  - Single-Seller Quick Start (create first budget and campaign).
  - Managing Single-Seller budgets and `productSet`s.
  - Single-Seller troubleshooting and FAQs.
- **Multi-seller documentation**:
  - Concepts and entities for multi-seller setups.
  - Multi-seller onboarding and campaign management flows.
  - Budgeting and optimization best practices.
- **Statistics**:
  - Available stats endpoints (`/stats/campaigns`, `/stats/sellers`, `/stats/seller-campaigns`).
  - How to choose identifiers (`campaignId`, `sellerId`, `sellerCampaignId`) for different reporting needs.
  - Patterns for monitoring performance and building dashboards.