Site validation and reporting

Video SSP implements automatic site validation technology for all market opportunities auctioned in the Video SSP Marketplace.

We also offer this technology to organizations managing their own network or private marketplace on the Video SSP platform. Additionally, we offer managing organizations of a network or private marketplace the ability to override automatic site validation and choose to match against the site reported by a partner who is trusted. The setting is called "Page URL Override" found in the Inventory Source or Marketplace Connection workflow of our console. When a partner's Inventory Source or Marketplace Connection is set to "Page URL Override", we qualify the ad request using the publisher reported domain (regardless of the domain detected) using Video SSP technology, and we record the reported domain in our Media key in reporting.

Note: The publisher reported domain is derived from the URL passed into the pageUrl parameter of any Video SSP ad tag.

Otherwise, the default setting for site verification is "Automatic". Similar to the Video SSP Marketplace, when a partner's Inventory Source or Marketplace Connection is set to "Automatic", we always qualify the ad request against the domain detected using Video SSP technology, regardless of the publisher reported domain, and we record the detected domain in our Media key in reporting.

Let's consider a few scenarios. In the table below, we are assuming that Site A is a whitelisted domain within the Inventory Source or Marketplace Connection. Site B is not whitelisted:

Site

verification

method

Publisher

reported

site

Video SSP

detected site

Validation

passed?

Media key

in reporting

Explanation

Automatic

Site A

Site B

No

Site B

Site validation is automatic, so we qualify against detected domain (Site B). Site A is the whitelisted site, so validation fails. However, we still report Site B because that is the detected domain. Even though the reported domain matches the whitelist, we disregard it.

Automatic

Site A

Site A

Yes

Site A

Site validation is automatic, so we qualify against the detected domain (Site A). Site A is the whitelisted site, so validation passes. We report Site A because that is the detected domain.

Automatic

Site B

Site B

No

Site B

Site validation is automatic, so we qualify against the detected domain (Site B). Site A is the whitelisted site, so validation fails. However, we still report Site B because that is the detected domain.

Automatic

Site B

Site A

Yes

Site A

Site validation is automatic, so we qualify against detected domain (Site A). Site A is the whitelisted site, so validation passes. We report Site A because that is the detected domain. Even though the reported domain suggests an inconsistency, we disregard it.

Page URL Override*

Site A

Site B

Yes

Site A

Site validation is override, so we qualify against the reported domain (Site A). Site A is the whitelisted site, so validation passes. We report Site A because that is the reported domain. Even though the detected domain suggests an inconsistency, we disregard it.

Page URL Override*

Site A

Site A

Yes

Site A

Site validation is override, so we qualify against the reported domain (Site A). Site A is the whitelisted site, so validation passes. We report Site A because that is the reported domain.

Page URL Override*

Site B

Site B

Yes

Site B

Site validation is override, so we qualify against the reported domain (Site B). Site A is the whitelisted site, so validation fails. We report Site B because that is the reported domain.

Page URL Override*

Site B

Site A

No

Site B

Site validation is override, so we qualify against the reported domain (Site B). Site A is the whitelisted site, so validation fails. However, we still report Site B because that is the detected domain. Even though the detected domain matches the whitelist, we disregard it.

* Applies to network or private marketplace only.

 

Site validation methods

There are three automatic site validation methods employed by Video SSP. ("Automatic" means simply that Video SSP's technology is deployed to detect and validate the embedding site.)

  • VPAID-enabled VAST tag - for VPAID-enabled tags, Video SSP's VPAID unit automatically detects the embedding site and passes it to our ad server. As long as the player supports VPAID, the detection process is seamless.
  • VAST only (non-VPAID) tag - for VAST only tags, we do not have the ability to deploy VPAID. This means that Video SSP requires the publisher to include a piece of JavaScript code on their page. More on this script can be found here. The script is responsible for detecting the embedding site and passing it to our ad server.
  • Video SSP AdPlayer - for publisher platform customers, our AdPlayer automatically detects the site and passes it to our ad server.

 

 

Have more questions? Submit a request