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

# Introduction

> Sharing your catalog with Criteo is the first step for a succesful integration

<Frame caption="Catalog integration process">
  <img src="https://mintcdn.com/criteo-e1682996/fr3QURzyzf6m9Hkn/images/retailer-integration/docs/318ae8bc4b01269895f3b87091e5fe2ce2d2b9093ee2e22a5392d1f6882e38a9-API_Integration_Workflow_-_Step_1_-_Catalog.png?fit=max&auto=format&n=fr3QURzyzf6m9Hkn&q=85&s=187d9b669651053fce6604b8bc367d6d" alt="Catalog integration process" width="2986" height="984" data-path="images/retailer-integration/docs/318ae8bc4b01269895f3b87091e5fe2ce2d2b9093ee2e22a5392d1f6882e38a9-API_Integration_Workflow_-_Step_1_-_Catalog.png" />
</Frame>

# Feeds vs. Product Importer API

Both **feeds** and the **Product Importer API** serve as tools for delivering product information and generating product datasets, but they are tailored to distinct requirements and use cases.

> 👍 Feed vs. Product Dataset
>
> * The feed is the raw input file provided by the client, while the product dataset is the organized and processed output created by Criteo for use in campaigns.
> * Feeds require ingestion and transformation to create product datasets that are ready for operational use.

Below is a detailed comparison:

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

      <th>
        <p>
          Feeds
        </p>
      </th>

      <th>
        <p>
          Product Importer API
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          <b>
            Data Format
          </b>
        </p>
      </td>

      <td>
        <p>
          XML, CSV, JSON
        </p>
      </td>

      <td>
        <p>
          JSON
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <b>
            Ingestion Speed
          </b>
        </p>
      </td>

      <td>
        <p>
          Slower, due to file processing
        </p>
      </td>

      <td>
        <p>
          Faster, enabling almost real-time updates
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <b>
            Automation
          </b>
        </p>
      </td>

      <td>
        <p>
          Requires manual uploads or scheduling
        </p>
      </td>

      <td>
        <p>
          Fully automated via API endpoints
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <b>
            Flexibility
          </b>
        </p>
      </td>

      <td>
        <p>
          Limited
        </p>
      </td>

      <td>
        <p>
          High, with granular update capabilities
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <b>
            Use Case
          </b>
        </p>
      </td>

      <td>
        <p>
          Suitable for small catalogs or periodic updates
        </p>
      </td>

      <td>
        <p>
          Designed for large catalogs and updates
        </p>
      </td>
    </tr>
  </tbody>
</table>

<Info>
  **Which to choose?**

  The **Product Importer API** is perfect for clients with extensive inventories (over one million products) who require faster data ingestion and more control over product updates. In contrast, **feeds** are better suited for simpler scenarios (smaller product counts, one ingestion per day) or when API integration isn't possible.

  Head this way for the [Feed upload guide](/retailer-integration/docs/product-upload-guide), or this way for the [Product Importer API guide](/retailer-integration/docs/product-importer-guide).
</Info>

<Info>
  If you need assistance to choose between feeds and/or the Product Importer API, please contact your Criteo representative.
</Info>

***

# Feed Definitions

## Feed

A feed is the raw data file provided by a client, typically in formats like XML, CSV, or JSON. It contains product inventory information such as product IDs, names, prices, availability, and other attributes. Feeds are unstructured or semi-structured and serve as the input for platforms to ingest, transform, and process product data.

## Product Dataset

A product dataset is the processed and structured collection of product information derived from the feed. It includes comprehensive product attributes such as IDs, descriptions, prices, availability, and additional metadata. The dataset is optimized to support Retail Media campaigns, ensuring accurate, consistent, and up-to-date product information for ad targeting, delivery, and reporting.

## Product Importer API

The Product Importer API is a RESTful API that enables the upload, update, and management of product datasets on the Criteo platform. It ensures that critical product details, such as IDs, prices, availability, and other attributes, remain accurate and synchronized, supporting the optimization and performance of retail media campaigns.

***

<br />

<br />

## What's next

* [Feed upload guide](/retailer-integration/docs/product-upload-guide)
* [Product feed parameters](/retailer-integration/docs/product-feed-parameters)
* [Product feed examples](/retailer-integration/docs/product-feed-examples)
* [Product Importer API Guide](/retailer-integration/docs/product-importer-guide)
* [Dataset parameters](/retailer-integration/docs/dataset-parameters)
* [Product Dataset Examples](/retailer-integration/docs/product-dataset-examples)