Introduction
With Commerce Video formats, the beacons have three different levels, meaning that each beacon will be linked to either:- An event that relates to the format/placement itself;
- An event that relates to the individual SKUs within the format (if SKUs are available in the format);
- An event that relates to video, via the VAST video player.
Format Level Beacons
Beacon Name | Beacon Description |
|---|---|
| Indicates that the format (video + SKUs if applicable) is rendered on the page, even if not viewable yet. |
| Indicates that the format is viewed by the user (viewability = more than 50% of the format in the user’s viewport for 1 second). _Note: this indicates the viewability of the format. However, video viewability (more than 50% of the format in the user’s viewport for two consecutive seconds) is tracked with OMID capabilities (see the “Additional verification with OMID compatible scripts” section). This beacon isnotused to track video viewability._ |
| Indicates that the format has been clicked by the user on a clickable and redirectable element that is neither the video nor the product tile (example: a CTA, a clickable text around the video…). If there is no any other clickable element than the video or SKUs, you can ignore this beacon. Notes:
|
| Please disregard this beacon. |
| Please disregard this beacon. |
SKU Level Beacons
Beacon Name | Beacon Description |
|---|---|
| Indicates that the product tile is rendered on the page (even if not viewable yet). |
| Indicates that the product tile is viewed by the user (viewed = more than 50% of the product in the user’s viewport for 1 second). |
| This beacon is triggered when a user clicks on an element (image, text) of the product tile that redirects to the product page. |
| This beacon is triggered when the user adds a product to their cart. _If there is no |
| This beacon is triggered when the user adds a product to their wishlist. _If no add-to-Wishlist CTA is available, it can be disregarded. The beacon can be fired multiple times if the user repeatedly clicks the |
VAST XML Level Beacons
Name | Description |
|---|---|
| Indicates that the video is rendered on the page (even if not viewable yet). Not used for billing. |
| Indicates that the video has started and should be triggered when the video enters in 50% of the user’s viewport.This is the beacon used for impression billing and reporting. |
| Must be triggered when 25% of the video has been played. |
| Must be triggered when 50% of the video has been played. |
| Must be triggered when 75% of the video has been played. |
| Must be triggered when 100% of the video has been played. |
| Must be triggered every time the user clicks on the video and gets redirected to the landing page stored in the _Do not trigger this beacon for clicks on the interactive buttons ( |
| Must be triggered every time the user clicks the _This action must not be triggered at the start of the video. It should only be initiated when the user actively mutes the video by clicking the |
| Must be triggered every time the user clicks the |
| Must be triggered every time the user clicks the If the decision is made not to display a pause/resume button in the player, this beacon can be ignored. This beacon should only be triggered by the button click and should not be triggered when the video pauses by itself due to leaving the viewport. If there is no redirection link provided in the VAST XML, a click on the video itself should pause/resume the video and this beacon should be fired. |
| Must be triggered every time the user clicks the If the decision is made not to display a pause/resume button in the player, this beacon can be ignored. This beacon should only be triggered by the button click and should not be triggered when the video autonomously resumes after being paused by leaving the viewport and subsequently returning. If there is no redirection link provided in the VAST XML, a click on the video itself should pause/resume the video and this beacon should be fired. |
videoStart beacon is triggered at ≥50% in view (used for billing). If integrated, the OMID start event requires 100% in view, so it will often fire slightly later than VAST. This is expected behavior and ensures compliance with OM SDK standards. Both beacons may appear in logs for the same impression.