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

# Choosing Your Consent Flow

> Understand which API consent setup applies to your use case before you start integrating.

## Overview

There are two ways to set up consent in the Criteo Retail Media API. The right choice depends on your use case. Picking the wrong flow requires redoing your integration, so confirm your setup before you start.

## Which Flow Should I Use?

|                              | Standard Consent Flow (Portal)                                                    | Private Market Programmatic Consent Flow                                                                                                                                                         |
| ---------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Which flow should I use?** | You are a brand, agency, or tech partner accessing a Criteo advertiser account    | You are a retailer operating a Retail Media Private Market in Criteo and managing demand accounts (brands or sellers) under your supply account                                                  |
| **How consent is granted**   | The advertiser clicks a consent URL and approves access through the Criteo portal | One-time manual consent for the Admin app via the portal, then consent for each demand account is granted programmatically by the Admin app — no portal interaction required per brand or seller |
| **Apps required**            | One app (Authorization Code or Client Credentials)                                | Two apps: an Admin app (Client Credentials) and a Business app (Authorization Code)                                                                                                              |
| **Who controls access**      | The advertiser or agency granting access                                          | The retailer                                                                                                                                                                                     |
| **Typical use case**         | A brand or agency manages their own campaigns via API                             | A retailer onboards brands or sellers onto their private market and grants consent to each demand account on their behalf                                                                        |

## Which One Am I?

**Use the Standard Consent Flow if:**

* You are a brand, agency, or tech partner accessing a Criteo advertiser account that belongs to someone else
* Consent is granted by the advertiser themselves, not by you

**Use the Private Market Programmatic Consent Flow if:**

* You are a retailer operating a Retail Media Private Market in Criteo
* You create and manage demand accounts (brands or sellers) under your supply account
* You want to grant consent to those demand accounts programmatically, without asking each brand or seller to log into the Criteo portal

<Warning>
  If you are a retailer operating a private market, do not use the Standard Consent Flow. It requires each brand or seller to manually approve access through the Criteo portal, which does not match the programmatic model used in private markets.
</Warning>

## Next Steps

* **Standard Consent Flow** — Follow the [Consent URL Generation](/retail-media/v2027.01-rc/docs/consent-url-generation) and [Authorization Requests](/retail-media/v2027.01-rc/docs/authorization-requests) guides.
* **Private Market Programmatic Consent Flow** — Follow the [Private Market Programmatic Consent Granting](/retail-media/v2027.01-rc/docs/private-market-programmatic-consent-granting) guide.