Mesure de la visibilité

Mesure de la visibilité

La notion de visibilité résulte de l’initiative 3MS. L’initiative 3MS portée par l’interprofession du marché américain, l’IAB US, l’ANA (Association of National Advertisers) et le 4A’s (American Association of Advertising Agencies) en 2012 a été motivée par l’établissement de normes et de métriques standard pour la publicité digitale comparables à celles existant pour les médias classiques. L’une des étapes a été d’établir une convention de comptage pour rendre compte de l’occasion de voir la publicité digitale. Il s’agit d’une convention comme « être présent dans la pièce où la télévision est allumée » pour la TV. Des distinctions sont à faire en fonction des environnements (web vs. in-app) et des formats publicitaires. Les définitions issues de l’initiative 3MS et portées par l’IAB US et le MRC qui sont retenues comme les standards du marché sont les suivantes :
  • Pour les formats display : au moins 50% des pixels de la création publicitaire doivent être affichés pendant au moins une seconde consécutive. Lorsque la création est un grand format (large banner), la proportion de la création devant être affichée est ramenée à 30%
  • Pour les formats vidéo : au moins 50% des pixels de la création publicitaire doivent être affichés pendant au moins 2 secondes consécutives. A noter, pour les comparaisons cross-média TV et VOL, le MRC a défini un nouveau standard : pour compter une impression digitale, 100% des pixels de la création doivent être affichés pendant au moins 2 secondes en continu, exclusion du SIVT (trafic invalide sophistiqué)
Le CESP souligne que les grilles d’analyse ci-dessous sur la visibilité sont basées sur la confiance accordée par le CESP à l’égard des informations fournies par les mesureurs.

Pour naviguer dans un tableau :
– sur ordinateur : cliquez sur une de ses cellules et naviguez horizontalement avec les touches de direction du clavier ou utilisez la barre de scroll horizontal qui se situe en bas du tableau.
– sur mobile : nous vous recommandons de passer en format paysage pour un meilleur affichage.
Vous pouvez télécharger la grille que vous souhaitez au format Excel tout en filtrant les mesureurs. Les mesureurs sont répartis dans plusieurs onglets selon si leur solution a été accréditée ou non par le MRC (Media Rating Council).

Environnement web

Solutions accréditées - Display


Updated February 2024
Adloox
adloox
Double Verify
Double Verify
Integral Ad Science
Moat Oracle
1) Can you list the sensors/data points your solution uses to measure display viewability? Adloox does not intend to share this informationJS tag, geometric methodIAS JS tag inserted into the page via an iframe.
IAS uses different methods according to the placement type.
Moat can measure wherever our JS tag is accepted for display measurement
2) Is your solution compliant with OM SDK?YesN/AN/AN/A
3) Is your solution compliant with MRAID?YesN/AN/AN/A
4) Do you measure expandable formats? YesYesYesYes
a) If yes, is your measure based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place; or do you use another method (specify which one)?Viewability is not pixel count but percentage of ad unit in view and duration is ‘continuous 30%+ for 1+ sec’; size of unit is not relevant and Adloox recalibrates active sensor measurement as ad expands and contracts. This would include a duration that encompasses expand/contract events.Polling frequency is 100ms (MRC requirement)The measurement is based on the pixel count of the initial format of the adIAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement.
If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression.
Moat is able to identify the non-expanded and expanded elements. Custom logic may be necessary to measure the unit.
5) Do you measure Page Take-over ads?YesYesYesYes
a) If yes, do you measure each component of the page takeover separately?Yes, Adloox have a specific script for takeover taking into consideration the size of the pageYesYesYes
b) If yes, how do you report page takeover viewability? The takeover is treated as a unit in classic viewability report with a specific macro for segragationDV measures and reports each ad independently for viewability in case of page takeover ads, if the ads have been setup with DV tags to measure independently.As a display unit.Report a figure for each component measured
6) Can you specify the method used to measure slide-in ads (a slide-in ad is an ad which appears by sliding on the screen after a launch event)?Adloox JS monitors the DOM element (the DOM is the way Javascript sees its containing pages' data); Adloox treats this identically to below-the-fold going above-the-fold as the user scrolls the browserDV identifies the ad creative on the page to be measured, and determines viewability based on the time spent in view as the ad slides onto the screen after launch event.IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement.
If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression.
Upon request, Moat can write custom logic to enable measuring the unit
7) Do you have limitation on Safari for cross-domain iframe? Yes,

Adloox’s cross-domain measurement process includes delivering a JavaScript package along with the ad content to the user and rendering the served ad.
Adloox relies on using the Intersection Observer API on Chrome and the window.requestAnimationFrame function on the Safari and Firefox browsers on the Mac operating system.
NoYes,

Safari has a “Top Hits” feature which pre-loads websites in the background as a user types a URL into the navigation bar. (Example: while a user enters the URL in an address bar to a page 2, impression events load for ads related to page 1 prior to selecting "Enter".) IAS does not support this functionality as the impressions are not reported as viewable since we use PageVisibility API. Ongoing IAS research currently guides that cases like this represent 0.5% of our traffic and we are continuing to monitor this number as a resource for possible future changes to our systems.
No
8) Do you have limitation on Chrome for cross-domain iframe? Yes,

Adloox’s cross-domain measurement process includes delivering a JavaScript package along with the ad content to the user and rendering the served ad.
Adloox relies on using the Intersection Observer API on Chrome and the window.requestAnimationFrame function on the Safari and Firefox browsers on the Mac operating system.
NoNoNo
9) Do you have limitation on Android for cross-domain iframe? Yes,

Adloox isn't able to detect browser focus in cross-origin environment.
Adloox JS works the same and has the same limitations for mobile web (WebViews) as it does for desktop.
NoNoNo
10) Do you have limitation on IOS environments for friendly iframe? NoNoNoNo
11) Do you have limitation on IOS environments for non- iframe? NoNoNoNo
12) Do you have any limitations on Android environments for friendly iframe? No NoNoNo
13) Do you have any limitations on Android environments for non- iframe? NoNoNoNo
14) Does your solution have any other limitations? If yes, could you specify which ones? Yes,

JavaScript is required for Viewability measurement
Yes,

Viewability measurement requires a JavaScript-enabled browser.

Certain browsers and iFrame scenarios may have additional security limitations which prevent the use of geometric methodology. In these cases, viewability may be ascertained using IAB-standard APIs.
Yes,

- JavaScript is required for all methods.
-If IAS’s server domains are listed as ad servers in blocking software, the IAS servers will be blocked.
-Ad integrated in deeply nested
iframes can be hard to measure, especially in old IE versions.
Yes,

Scroll rate is not measurable if the Moat tag loads inside a hostile iframe.
If the user has disabled JavaScript, Moat will not measure the impression.
15) Has your solution been accredited by MRC for display viewability measurement?YesYesYesYes
a) If yes, has your solution been continuously accredited since your first accreditation? YesYesYesYes
b) If no, are you in the process of being accredited by MRC?N/AN/AN/ANot applicable
16) Do you provide custom viewability definitions?Yes,

Adloox can provide custom viewability criterias on top of the MRC/IAB one
Yes,

- the GroupM viewability definition
- the PMX viewability definition
- a user-set custom viewability definition
YesYes
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant)Yes,

All Adloox custom viewability definitions are set to never go under MRC minimum standards for viewability measurement
Yes

All
Yes,

These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds.
Yes,

List of all compliant display metrics:
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
In-View Time > 5 Sec Rate
In-View Time > 10 Sec Rate
In-View Time > 15 Sec Rate
In-View Time > 30 Sec Rate
In-View Time > 1 Min Rate
On-Screen Impressions
On-Screen Rate
On-Screen Measurable Impressions
80% On-Screen for 1 Sec Impressions
80% On-Screen for 1 Sec Rate
Total Ad Dwell Time
Total Active Page Dwell Time
Active Page Dwell Time
In-View Time > 5 Sec Impressions
In-View Time > 10 Sec Impressions
In-View Time > 15 Sec Impressions
In-View Time > 30 Sec Impressions
In-View Time > 1 Min Impressions
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited)Yes (list available in audit materials for MRC)Yes,

(1) All user-set custom Display Viewable Impressions in Desktop and Mobile Web Environments

(2) PMX viewability definition
NoYes,

List of all accredited display metrics:
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
In-View Time > 5 Sec Rate
In-View Time > 10 Sec Rate
In-View Time > 15 Sec Rate
In-View Time > 30 Sec Rate
In-View Time > 1 Min Rate
On-Screen Impressions
On-Screen Rate
On-Screen Measurable Impressions
80% On-Screen for 1 Sec Impressions
80% On-Screen for 1 Sec Rate
Total Ad Dwell Time
Total Active Page Dwell Time
Active Page Dwell Time
In-View Time > 5 Sec Impressions
In-View Time > 10 Sec Impressions
In-View Time > 15 Sec Impressions
In-View Time > 30 Sec Impressions
In-View Time > 1 Min Impressions
17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? YesYesYesYes
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps?N/AN/AN/A

Solutions accréditées - Vidéo


Updated February 2024
Adloox
adloox
Double Verify
Double Verify
Integral Ad Science
Moat Oracle
18) Is your solution compliant with all VAST version? YesYesYesYes
a) If no, can you specify which ones your solution supports?N/AN/AN/ANot applicable
b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? YesYesYesYes
19) Is your solution compliant with OM SDK?N/AN/AN/AN/A
20) Is your solution compliant with MRAID?N/AN/AN/AN/A
21) Can you list the sensors/data points your solution uses to measure video viewability? Adloox does not intend to share this informationIndustry-standard APIs such as intersection observer and VPAID, as well as geometric and resource-based data points
JavaScript-based technology that uses both geometric and browser optimization measurement approaches to determine viewability.
VPAID or web video SDK implementation.
Moat VPAID tag
22) Do you detect the presence of audio? YesYesYesYes
23) Do you have any limitations on Safari for cross-domain iframe? Yes,

Adloox isn't able to detect browser focus in cross-origin environment
NoYes,

Deeply nested iframes may produce measurement limitations.
No
24) Do you have any limitations on Chrome for cross-domain iframe?Yes,

Adloox isn't able to detect browser focus in cross-origin environment
NoNoNo
25) Do you have any limitations on Android for cross-domain iframe? Yes,

Adloox isn't able to detect browser focus in cross-origin environment
NoNoNo
26) Do you have any limitations on IOS environments for friendly iframe? NoNoNoNo
27) Do you have any limitations on IOS environments for non- iframe? NoNoNoNo
28) Do you have any limitations on Android environments for friendly iframe? NoNoNoNo
29) Do you have any limitations on Android environments for non- iframe? NoNoNoNo
30) Does your solution have any other limitations? If yes, could you specify which ones?Yes,

JavaScript is required for Viewability measurement
Yes

Tagging - requires use of either DV Video Omnitag or DV integration with video platform (i.e. Innovid, Sizmek)
Inventory - measurement capable on either VPAID or VAST inventory that is using OMID
Yes

- JavaScript is required for all methods.
- If IAS’s server domains are listed as ad servers in blocking software, the IAS servers will be blocked.
- Ad integrated in deeply nested iframes can be hard to measure, especially in old IE versions.
Yes,

Scroll rate is not measurable if the Moat tag loads inside a hostile iframe.
If the user has disabled JavaScript, Moat will not measure the impression
31) Has your solution been accredited by MRC for video viewability measurement? YesYesYesYes
a) If yes, has your solution been continuously accredited since your first accreditation? NoYesYesYes
b) If no, are you in the process of being accredited by MRC?N/AN/AN/ANot applicable
32) Do you provide custom viewability definitions?Yes,

Adloox can provide custom viewability defnition on top of the MRC/IAB one
Yes,

- the GroupM viewability definition
- the PMX viewability definition
- a user-set custom viewability definition
YesYes
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant)Yes
All
Yes
All
Yes ,
These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds.
Yes,

List of all compliant video metrics:
2 Sec In-View Impressions
2 Sec Video In-View Rate
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
% of Video Played In-View
Audible On 1st Quartile Rate
Audible On 2nd Quartile Rate
Audible On 3rd Quartile Rate
Audible On Complete Rate
Visible On 1st Quartile Rate
Visible On 2nd Quartile Rate
Visible On 3rd Quartile Rate
Visible On Completion Rate
Audible and Visible at 1st Quartile Rate
Audible and Visible at 2nd Quartile Rate
Audible and Visible at 3rd Quartile Rate
Audible and Visible on Complete Rate
Audible and Fully On-Screen for Half of Duration Impressions
Audible and Fully On-Screen for Half of Duration Rate
3 Sec In-View Impressions
5 Sec In-View Impressions
On-Screen Measurable Impressions
On-Screen Impressions
On-Screen Rate
3 Sec Video In-View Rate
5 Sec Video In-View Rate
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
3 Sec Fully On-Screen Impressions
3 Sec Fully On-Screen Rate
In-View Time
2 Sec In-View and Reached Completion Impressions
2 Sec In-View and Reached Completion Rate
Audible On 1st Quartile Sum
Audible On 2nd Quartile Sum
Audible On 3rd Quartile Sum
Audible On Complete Sum
Visible On 1st Quartile Sum
Visible On 2nd Quartile Sum
Visible On 3rd Quartile Sum
Visible On Completion Sum
Audible and Visible on Start Sum
Audible and Visible on Start Rate
Audible and Visible at 1st Quartile Sum
Audible and Visible at 2nd Quartile Sum
Audible and Visible at 3rd Quartile Sum
Audible and Visible on Complete Sum
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited)NoYes,

(1) Client set definitions (display and video)
(2) PMX viewability definition (display and video)
(3) GroupM viewability definition (display and video)
NoYes,

List of all accredited video metrics:
2 Sec In-View Impressions
2 Sec Video In-View Rate
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
% of Video Played In-View
Audible On 1st Quartile Rate
Audible On 2nd Quartile Rate
Audible On 3rd Quartile Rate
Audible On Complete Rate
Visible On 1st Quartile Rate
Visible On 2nd Quartile Rate
Visible On 3rd Quartile Rate
Visible On Completion Rate
Audible and Visible at 1st Quartile Rate
Audible and Visible at 2nd Quartile Rate
Audible and Visible at 3rd Quartile Rate
Audible and Visible on Complete Rate
Audible and Fully On-Screen for Half of Duration Impressions
Audible and Fully On-Screen for Half of Duration Rate
3 Sec In-View Impressions
5 Sec In-View Impressions
On-Screen Measurable Impressions
On-Screen Impressions
On-Screen Rate
3 Sec Video In-View Rate
5 Sec Video In-View Rate
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
3 Sec Fully On-Screen Impressions
3 Sec Fully On-Screen Rate
In-View Time
2 Sec In-View and Reached Completion Impressions
2 Sec In-View and Reached Completion Rate
Audible On 1st Quartile Sum
Audible On 2nd Quartile Sum
Audible On 3rd Quartile Sum
Audible On Complete Sum
Visible On 1st Quartile Sum
Visible On 2nd Quartile Sum
Visible On 3rd Quartile Sum
Visible On Completion Sum
Audible and Visible on Start Sum
Audible and Visible on Start Rate
Audible and Visible at 1st Quartile Sum
Audible and Visible at 2nd Quartile Sum
Audible and Visible at 3rd Quartile Sum
Audible and Visible on Complete Sum
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate
33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? YesYesYesYes
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps?N/AN/AN/A

Environnement in-app

Solutions accréditées - Display


Updated February 2024
Adloox
adloox
Double Verify
Double Verify
Integral Ad Science
Moat Oracle
1) Can you list the sensors/data points your solution uses to measure display viewability? Adloox does not intend to share this informationOM SDK or MRAIDOM SDK, AVID SDK, or MRAIDJS tag, with OMSDK
2) Is your solution compliant with OM SDK?YesYesYesYes
3) Is your solution compliant with MRAID?YesYesYesYes

However there are some limitations with MRAID format which depends on the app. developper choices.
4) Do you measure expandable formats? YesYesYesYes
a) If yes, is your measure based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place; or do you use another method (specify which one)?Viewability is not pixel count but percentage of ad unit in view and duration is ‘continuous 30%+ for 1+ sec’; size of unit is not relevant and Adloox recalibrates active sensor measurement as ad expands and contracts. This would include a duration that encompasses expand/contract events. Polling frequency is 100ms (MRC requirement)The measurement is based on both the pixel count of the initial format of the ad for the duration and the pixel count of the expanded ad.IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement.
If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression.
Moat is able to identify the non-expanded and expanded elements. Custom logic may be necessary to measure the unit.
5) Do you measure Page Take-over ads?YesYesYesYes
a) If yes, do you measure each component of the page takeover separately?YesYesYesYes
b) If yes, how do you report page takeover viewability? The takeover is treated as a unit in classic viewability report with a specific macro for segragationDV measures and reports each ad independently for viewability in case of page takeover ads, if the ads have been setup with DV tags to measure independently.As a display unit.Report a figure for each component measured
6) Can you specify the method used to measure slide-in ads (a slide-in ad is an ad which appears by sliding on the screen after a launch event)?Adloox JS monitors the DOM element (the DOM is the way Javascript sees its containing pages' data); Adloox treats this identically to below-the-fold going above-the-fold as the user scrolls the browserDV identifies the ad creative on the page to be measured, and determines viewability based on the time spent in view as the ad slides onto the screen after launch event.IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement.
If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression.
Upon request, Moat can write custom logic to enable measuring the unit
7) Do you have limitation on Safari for cross-domain iframe? N/AN/AN/AN/A
8) Do you have limitation on Chrome for cross-domain iframe? N/AN/AN/AN/A
9) Do you have limitation on Android for cross-domain iframe? N/AN/AN/AN/A
10) Do you have limitation on IOS environments for friendly iframe? NoYes,
OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,
OM SDK required
11) Do you have limitation on IOS environments for non- iframe? NoYes,
OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,
OM SDK required
12) Do you have any limitations on Android environments for friendly iframe? NoYes,
OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,
OM SDK required
13) Do you have any limitations on Android environments for non- iframe? NoYes,
OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,
OM SDK required
14) Does your solution have any other limitations? If yes, could you specify which ones? Yes,

JavaScript is required for Viewability measurement
OM SDK is required for Viewability measurement
NoNoYes,

Limitations depend on the partner or the environment being measured. Moat is partner agnostic and can measure wherever our tag is accepted.
15) Has your solution been accredited by MRC for display viewability measurement?YesYesYesYes
a) If yes, has your solution been continuously accredited since your first accreditation? N/AYesYesYes
b) If no, are you in the process of being accredited by MRC?N/AN/AN/ANot applicable
16) Do you provide custom viewability definitions?Yes,

Adloox can provide custom viewability criterias on top of the MRC/IAB one
Yes,

- the GroupM viewability definition
- the PMX viewability definition
- a user-set custom viewability definition
YesYes
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant)Yes,

All Adloox custom viewability definitions are set to never go under MRC minimum standards for viewability measurement
Yes

All
Yes,

These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds.
Yes,

List of all compliant display metrics:
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
In-View Time > 5 Sec Rate
In-View Time > 10 Sec Rate
In-View Time > 15 Sec Rate
In-View Time > 30 Sec Rate
In-View Time > 1 Min Rate
On-Screen Impressions
On-Screen Rate
On-Screen Measurable Impressions
80% On-Screen for 1 Sec Impressions
80% On-Screen for 1 Sec Rate
Total Ad Dwell Time
Total Active Page Dwell Time
Active Page Dwell Time
In-View Time > 5 Sec Impressions
In-View Time > 10 Sec Impressions
In-View Time > 15 Sec Impressions
In-View Time > 30 Sec Impressions
In-View Time > 1 Min Impressions
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited)Yes (list available in audit materials for MRC)NoNoYes,

List of all accredited display metrics:
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
In-View Time > 5 Sec Rate
In-View Time > 10 Sec Rate
In-View Time > 15 Sec Rate
In-View Time > 30 Sec Rate
In-View Time > 1 Min Rate
On-Screen Impressions
On-Screen Rate
On-Screen Measurable Impressions
80% On-Screen for 1 Sec Impressions
80% On-Screen for 1 Sec Rate
Total Ad Dwell Time
Total Active Page Dwell Time
Active Page Dwell Time
In-View Time > 5 Sec Impressions
In-View Time > 10 Sec Impressions
In-View Time > 15 Sec Impressions
In-View Time > 30 Sec Impressions
In-View Time > 1 Min Impressions
17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? YesYesYesYes
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps?YesYes

DV has certification processes in place for MRAID and OM SDK enabled partners. For SDK, DV integrates the partner's ad SDK in our testbed app to undergo a series of manual and automated tests that determine the accuracy of the implementation by comparing its results with the expected results.
Furthermore, DV performs volume tests with our partners to ensure that the impression counts are aligned and critical benchmarks in measurement and viewability are met. In cases where DV sees a discrepancy, we recommend our partners to implement changes and validate them before confirming them as certified.
YesYes,

In addition to the certification performed by IAB Tech Lab for OM SDK implementations, Moat performs QA on OM SDK apps before considering these apps measurable.

Solutions accréditées - Vidéo


Updated February 2024
Adloox
adloox
Double Verify
Double Verify
Integral Ad Science
Moat Oracle
18) Is your solution compliant with all VAST version? YesYesYesYes
a) If no, can you specify which ones your solution supports?N/AN/AN/ANot applicable
b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? YesYesNoYes
19) Is your solution compliant with OM SDK?YesYesYesYes
20) Is your solution compliant with MRAID?YesYesYesYes

However there are some limitations with MRAID format which depens on the app. developer choices.
21) Can you list the sensors/data points your solution uses to measure video viewability? Adloox does not intend to share this informationIndustry-standard APIs such as VPAID, MRAID and OM SDK OMID API.
AVID SDK, OM SDKOM SDK
22) Do you detect the presence of audio? YesYesYesYes
23) Do you have any limitations on Safari for cross-domain iframe? N/AN/A
24) Do you have any limitations on Chrome for cross-domain iframe?N/AN/A
25) Do you have any limitations on Android for cross-domain iframe? N/AN/AN/A
26) Do you have any limitations on IOS environments for friendly iframe? Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK required
27) Do you have any limitations on IOS environments for non- iframe? Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK required
28) Do you have any limitations on Android environments for friendly iframe? Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK required
29) Do you have any limitations on Android environments for non- iframe? Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK or MRAID is required
Yes,

OM SDK, proprietary SDK or MRAID is required
Yes,

OM SDK required
30) Does your solution have any other limitations? If yes, could you specify which ones?Yes,

JavaScript is required for Viewability measurement
NoNoYes,

Limitations depend on the partner or the environment being measured. Moat is partner agnostic and can measure wherever our tag is accepted.
31) Has your solution been accredited by MRC for video viewability measurement? YesYesYesYes
a) If yes, has your solution been continuously accredited since your first accreditation? YesYesYes
b) If no, are you in the process of being accredited by MRC?N/AN/AN/ANot applicable
32) Do you provide custom viewability definitions?Yes,

Adloox can provide custom viewability defnition on top of the MRC/IAB one
Yes,

custom viewability definitions such as GroupM, PMX, or a client defined definition are possible when inventory supports OMID/OMSDK
YesYes
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant)Yes
All
Yes
All
Yes,
These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds.
Yes,

List of all compliant video metrics:
2 Sec In-View Impressions
2 Sec Video In-View Rate
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
% of Video Played In-View
Audible On 1st Quartile Rate
Audible On 2nd Quartile Rate
Audible On 3rd Quartile Rate
Audible On Complete Rate
Visible On 1st Quartile Rate
Visible On 2nd Quartile Rate
Visible On 3rd Quartile Rate
Visible On Completion Rate
Audible and Visible at 1st Quartile Rate
Audible and Visible at 2nd Quartile Rate
Audible and Visible at 3rd Quartile Rate
Audible and Visible on Complete Rate
Audible and Fully On-Screen for Half of Duration Impressions
Audible and Fully On-Screen for Half of Duration Rate
3 Sec In-View Impressions
5 Sec In-View Impressions
On-Screen Measurable Impressions
On-Screen Impressions
On-Screen Rate
3 Sec Video In-View Rate
5 Sec Video In-View Rate
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
3 Sec Fully On-Screen Impressions
3 Sec Fully On-Screen Rate
In-View Time
2 Sec In-View and Reached Completion Impressions
2 Sec In-View and Reached Completion Rate
Audible On 1st Quartile Sum
Audible On 2nd Quartile Sum
Audible On 3rd Quartile Sum
Audible On Complete Sum
Visible On 1st Quartile Sum
Visible On 2nd Quartile Sum
Visible On 3rd Quartile Sum
Visible On Completion Sum
Audible and Visible on Start Sum
Audible and Visible on Start Rate
Audible and Visible at 1st Quartile Sum
Audible and Visible at 2nd Quartile Sum
Audible and Visible at 3rd Quartile Sum
Audible and Visible on Complete Sum
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited)NoYes,

(1) Client set definitions (display and video)
(2) PMX viewability definition (display and video)
(3) GroupM viewability definition (display and video)
NoYes,

List of all accredited video metrics:
2 Sec In-View Impressions
2 Sec Video In-View Rate
Fully On-Screen Measurable Impressions
Fully On-Screen Impressions (No Time Minimum)
Fully On-Screen Rate (No Time Minimum)
% of Video Played In-View
Audible On 1st Quartile Rate
Audible On 2nd Quartile Rate
Audible On 3rd Quartile Rate
Audible On Complete Rate
Visible On 1st Quartile Rate
Visible On 2nd Quartile Rate
Visible On 3rd Quartile Rate
Visible On Completion Rate
Audible and Visible at 1st Quartile Rate
Audible and Visible at 2nd Quartile Rate
Audible and Visible at 3rd Quartile Rate
Audible and Visible on Complete Rate
Audible and Fully On-Screen for Half of Duration Impressions
Audible and Fully On-Screen for Half of Duration Rate
3 Sec In-View Impressions
5 Sec In-View Impressions
On-Screen Measurable Impressions
On-Screen Impressions
On-Screen Rate
3 Sec Video In-View Rate
5 Sec Video In-View Rate
1 Sec Fully On-Screen Impressions
1 Sec Fully On-Screen Rate
3 Sec Fully On-Screen Impressions
3 Sec Fully On-Screen Rate
In-View Time
2 Sec In-View and Reached Completion Impressions
2 Sec In-View and Reached Completion Rate
Audible On 1st Quartile Sum
Audible On 2nd Quartile Sum
Audible On 3rd Quartile Sum
Audible On Complete Sum
Visible On 1st Quartile Sum
Visible On 2nd Quartile Sum
Visible On 3rd Quartile Sum
Visible On Completion Sum
Audible and Visible on Start Sum
Audible and Visible on Start Rate
Audible and Visible at 1st Quartile Sum
Audible and Visible at 2nd Quartile Sum
Audible and Visible at 3rd Quartile Sum
Audible and Visible on Complete Sum
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions
Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate
33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? YesYesYesYes
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps?YesYes

DV has certification processes in place for MRAID and OM SDK enabled partners. For SDK, DV integrates the partner's ad SDK in our testbed app to undergo a series of manual and automated tests that determine the accuracy of the implementation by comparing its results with the expected results.
Furthermore, DV performs volume tests with our partners to ensure that the impression counts are aligned and critical benchmarks in measurement and viewability are met. In cases where DV sees a discrepancy, we recommend our partners to implement changes and validate them before confirming them as certified.
YesYes,

In addition to the certification performed by IAB Tech Lab for OM SDK implementations, Moat performs QA on OM SDK apps before considering these apps measurable.