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

# Display Panel

> Here is a breakdown of the requirements for your Display Panel placement to pass both technical and design QA

# Beaconing

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

      <th>
        <p>
          Name
        </p>
      </th>

      <th>
        <p>
          Response field
        </p>
      </th>

      <th>
        <p>
          Explanation
        </p>
      </th>

      <th>
        <p>
          Mandatory
        </p>
      </th>
    </tr>
  </thead>

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

      <td>
        <p>
          Impression
        </p>
      </td>

      <td>
        <p>
          <code>
            onLoadBeacon
          </code>
        </p>
      </td>

      <td>
        <p>
          URL to be called when the whole placement is loaded onto the page. For display ads, the placement is considered "loaded" when the entire unit is rendered.
        </p>

        <p>
          This beacon should only be fired once.
        </p>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          Format
        </p>
      </td>

      <td>
        <p>
          View
        </p>
      </td>

      <td>
        <p>
          <code>
            onViewBeacon
          </code>
        </p>
      </td>

      <td>
        <p>
          URL to be called when the placement is viewed according to IAB's viewable ad impression measurement guidelines. At least 50% of the unit must be in the user's viewport for at least 1 uninterrupted second.
        </p>

        <p>
          This beacon should only be fired once.
        </p>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          Format
        </p>
      </td>

      <td>
        <p>
          Click
        </p>
      </td>

      <td>
        <p>
          <code>
            onClickBeacon
          </code>
        </p>
      </td>

      <td>
        <p>
          URL to be called when the user clicks on the placement itself.
        </p>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          Format
        </p>
      </td>

      <td>
        <p>
          File download
        </p>
      </td>

      <td>
        <p>
          <code>
            onFileClickBeacon
          </code>
        </p>
      </td>

      <td>
        <p>
          URL to be called when a click is made by the user on a CTA button, or from the creative image of the format, which leads to a file download.
        </p>
      </td>

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

# Ad design

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

      <th>
        <p>
          Explanation
        </p>
      </th>

      <th>
        <p>
          Mandatory
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          Breakpoint adherence
        </p>
      </td>

      <td>
        <ul>
          <li>
            <b>
              1.
            </b>

            Ensure the breakpoints for the banners are correct.
          </li>

          <li>
            <b>
              2.
            </b>

            For the desktop version, verify the image cropping is as specified.
          </li>

          <li>
            <b>
              3.
            </b>

            Ensure the banner switches to its mobile version at the appropriate breakpoint.
          </li>

          <li>
            <b>
              4.
            </b>

            Use mock-ups to verify the correct spacing around the banner.
          </li>

          <li>
            <b>
              5.
            </b>

            Ensure the "sponsored" badge is displayed correctly for every breakpoint, as shown in the mock-ups provided by Criteo.
          </li>
        </ul>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          Mock-up adherence
        </p>
      </td>

      <td>
        <p>
          The design of the mock-ups should be followed, ensuring the following:
        </p>

        <ul>
          <li>
            <b>
              Background image:
            </b>

            The image ratio is correct and resizes proportionally.
          </li>

          <li>
            <b>
              Cropping:
            </b>

            The image is cropped correctly for different screen resolutions, with the safe zone remaining visible.
          </li>

          <li>
            <b>
              Product information:
            </b>

            The layout, price, rating, text orientation, and text centering align with the mock-ups.
          </li>

          <li>
            <b>
              Sponsored text:
            </b>

            The text placement, font family, font size, and color should match the mock-ups.
          </li>
        </ul>
      </td>

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

# API features

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

      <th>
        <p>
          Explanation
        </p>
      </th>

      <th>
        <p>
          Mandatory
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          Leveraging regiondata
        </p>
      </td>

      <td>
        <ul>
          <li>
            <b>
              Format:
            </b>

            Ensure that the region IDs in the ad call match what is passed in the product feed
          </li>

          <li>
            <b>
              Adherence:
            </b>

            Ensure that Criteo is adhering properly to the region in our ad response
          </li>
        </ul>
      </td>

      <td>
        <p>
          Yes, if regiondata has been implemented
        </p>
      </td>
    </tr>
  </tbody>
</table>

# Click options

***Note that only one of these options will be available per format***

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

      <th>
        <p>
          Check
        </p>
      </th>

      <th>
        <p>
          Mandatory
        </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <p>
          No redirection
        </p>
      </td>

      <td>
        <p>
          Nothing happens
        </p>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          Redirection URL
        </p>
      </td>

      <td>
        <p>
          The user gets redirected to the URL provided in the ad response
        </p>
      </td>

      <td>
        <p>
          Yes
        </p>
      </td>
    </tr>

    <tr>
      <td>
        <p>
          File download
        </p>
      </td>

      <td>
        <p>
          The user downloads the file provided
        </p>
      </td>

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