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

# Overview

## Before Starting

The following information is important to know regarding Demand Side Analytics.

### Asynchronous Workflow

Reports are requested and retrieved using **asynchronous endpoints**.

### Report Date Range

The report date range supports a maximum window of **100 days**, with data retained for up to **3 years**.

### Report Row Limits

Reports are limited to **10 million rows**. If a report reaches this limit, the data may be incomplete due to truncation. To avoid this, consider reviewing the following parameters for bulk requests:

* Number of campaign or line item IDs
* Start and end date range
* Report type

### Report Attribution

* Report attribution windows and time-zones are fully configurable.
* Data is processed and batched **hourly**. Same-day data may be partially available.
* While reports with an end date of today or yesterday are cached for 1 hour, reports with an end date older than yesterday are cached for **24 hours.**
* The exact expiration time is provided in the `expiresAt` field of the /status response.

### Rate Limits

You can find more details about rate limits on [this page](/retail-media/docs/rate-limits).

<table>
  <thead>
    <tr>
      <th>
        <p>
          OAuth Method
        </p>
      </th>

      <th>
        <p>
          Rate limit
        </p>
      </th>

      <th>
        <p>
          Rate limit applies at level
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          <a href="/retail-media/docs/oauth-app-client-credentials">Client Credentials</a>
        </p>
      </td>

      <td>
        <p>
          <b>
            250 calls
          </b>

          per minute for default endpoints
        </p>

        <p>
          <b>
            40 calls
          </b>

          per minute for reporting endpoints
        </p>
      </td>

      <td>
        <p>
          Application level
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          <a href="/retail-media/docs/oauth-app-authorization-code">Authorization Code</a>
        </p>
      </td>

      <td>
        <p>
          <b>
            10 calls
          </b>

          per minute
        </p>
      </td>

      <td>
        <p>
          Account
        </p>
      </td>
    </tr>
  </tbody>
</table>

### Data Latency

Please refer to [our troubleshooting guide](/retail-media/docs/api-troubleshooting-guide#/is-the-issue-that-my-data-is-late) for more data latency details.

<Info>
  Different types of activity and attribution data become available at different times after the event or sale:

  * **Onsite activity data** is typically available within **6–8 hours** of the event.
  * **Offsite activity data** is typically available within **24 hours** of the event.
  * **Initial attribution data** is available within **7–9 hours** of the sale.
  * **Final attribution data** is processed and posted within **74 hours** after the sale.
  * Please note that potential minor updates can occur up to **120 hours** before finalization
</Info>

<Note>
  Learn more about our Attribution Rules in the [Commerce Max Help Center](https://help.retailmedia.criteo.com/kb/guide/en/about-attribution-sZH1iCyq5L/Steps/1034909).
</Note>