Response Elements
All formats share the same API response structure, which is described below:Status
Type: string
Values: OK(for successful responses) or an error type.
In case of an error, an array will be added to the response with the list of applicable error message(s), such as: Missing required parameter x
Placements
Type: array of placement objects
Each placement name is used as a key, like for example: viewCategory_API_desktop-Video.
The value of each key is an array of ads. Each ad has the below properties:
-
format: indicates which format is returned. -
products: is a list of SKUs that are included in the ad format, along with additional metadata about each SKU (image, product URL, parent SKU ID, etc.)
-
products_order: some real time product substitutions are allowed based on availability of SKUs:
products: an array of product IDs. The order of products returned by Criteo should match the order of SKUs displayed on the site, unless a SKU is unavailable or out of stock.isMandatory: If true, the overall ad unit should notbe displayed if this product is not available. If false, the ad can be shown, but the button/product tile should be removed from the unit.
Rendering
rendering: format-specific properties to use when rendering the ad, including image assets, colors, and custom labels.
TagVideoVAST field described below.
TAGVideoVAST
-
**
TagVideoVAST**orXmlVideoVAST:TagVideoVAST(by default) : a URL to load a VAST XML via a video player that supports VAST;XmlVideoVAST(if retailer opt-out of doing an extra API call to retrieve the VAST definition): The VAST XML to provide a video player that supports the VAST standard.
-
OnViewBeacon,OnLoadBeacon,OnClickBeacon, etc.: the beacons to trigger/fire back to Criteo when specific actions take place. See the section for further information.
VAST XML Example
Closed Caption Files in VAST XML
When Closed Captioning is enabled, the VAST XML response will include aClosedCaptionFiles element nested inside each MediaFile element within the MediaFiles section.
Each ClosedCaptionFiles container holds one or more ClosedCaptionFile entries, representing closed captions in different languages and formats (currently, text/vtt is supported). These are not video assets themselves and must not be interpreted as part of the video src.
Example
Product Beacons
Placement / Format Beacon
Placement and format beacons will typically be right under theTagVideoVAST:
Rendering Fields
Below is an example of rendering fields in the API response:Field | Description |
|---|---|
| Do not use this field.It is reserved for Criteo purposes only. All video-related information, assets and tracking must be used from the VAST XML only. |
| Do not use these fields.It is reserved for Criteo purposes only. The optional redirection link to a landing page if the user clicks on the video player is available in the VAST definition (cf. |
| Text to display in an alt_text div attribute forWCAGcompliancy purposes. |
| Free text field to display a legal message upon user hover. This field is optional for the advertiser to complete. |
| Do not use these fields.It is reserved for Criteo purposes only. |