Format

Impression

onLoadBeacon

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.

This beacon should only be fired once.

Yes

Format

View

onViewBeacon

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.

This beacon should only be fired once.

Yes

Format

Click

onClickBeacon

URL to be called when the user clicks on the placement itself.

Yes

Format

File download

onFileClickBeacon

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.

Yes

Product

Impression

onLoadBeacon

URL to be called when the individual product tile is loaded onto the page. If leveraging universal beacons , this field will be blank.

This beacon should only be fired once.

Yes

Product

View

onViewBeacon

URL to be called when the individual product tile is viewed according to IAB's viewable ad impression measurement guidelines. At least 50% of the placement must be in the user's viewport for at least 1 uninterrupted second.

This beacon should only be fired once per product.

Yes

Product

Click

productPage
and/or
onClickBeacon

productPage
This element is a URL that will send an OnClickBeacon beacon to Criteo and then redirect the shopper to the item's PDP link (pulled from the product feed).

It is possible to use this as the href value for the sponsored product as a way to track clicks instead of calling the OnClickBeaconURL.

onClickBeacon
URL to be called when the individual product tile is clicked. This refers to any
click interaction with the product tile outside of adding to cart or adding to wishlist (see next two rows).

This beacon should fire on all of the range of clicks; left click, middle click, right click to open in a new tab and keyboard shortcuts that simulate a click.

Both
This beacon should be fired on every click event. Criteo will deduplicate clicks for billing purposes internally.

Yes

Product

Add-to-cart

onBasketChangeBeacon

URL to be called when a product is added to or removed from the basket/cart. You can add the quantity of products as a query string parameter. If no quantity parameter is provided, it defaults to 1.

This beacon should be fired on every add-to-cart click event. Criteo will deduplicate clicks for billing purposes internally.

Yes

Product

Add-to-wishlist

onWishlistBeacon

URL to be called when the product is added to the wishlist/favorites.

This beacon should be fired on every add-to-wishlist click event. Criteo will deduplicate clicks for billing purposes internally.

Yes

Breakpoint adherence

• *1.** Ensure the breakpoints for the banners are correct.
• *2.** For the desktop version, verify the image cropping is as specified.
• *3.** Ensure the banner switches to its mobile version at the appropriate breakpoint.
• *4.** Use mock-ups to verify the correct spacing around the banner.
• *5.** Ensure the "sponsored" badge is displayed correctly for every breakpoint, as shown in the mock-ups provided by Criteo.

Yes

Differing product counts

Ensure that the design for a single product matches the mock-ups and that all parts of the ad unit (SKUs, navigation arrows, navigation dots, buttons, etc.) ahere to the mock-ups when multiple products are returned.

Yes

Mock-up adherence

The design of the mock-ups should be followed, ensuring the following:

• *Background image ratio:** The image resizes proportionally on mobile, maintaining the correct ratio.
• *Backgrounds per product:** Up to 5 different backgrounds per product are displayed.
• *Image cropping:** The image is cropped correctly for different screen resolutions, keeping the safe zone visible.
• *CSS colors:** Extra CSS colors are displayed correctly.
• *Branding and product zones:** The ratio between the branding zone and the product zone follows the mock-ups.
• *Product information:** The layout, price, rating, text orientation, and text centering match the mock-ups.
• *Title:** The font style matches the mock-ups.
• *Text:** Text placement, font family, font size, and colors match the mock-ups.
• *Contour:** A contour around the solution follows the mock-up design.
• *Sponsored text:** The text placement, font family, font size, and color match the mock-ups

Yes

Leveraging regiondata

• *Format:** Ensure that the region IDs in the ad call match what is passed in the product feed
• *Adherence:** Ensure that Criteo is adhering properly to the region in our ad response

Yes, if regiondata has been implemented