In-stream Video Ads FAQ


Please refer to the "In-Stream Video Requirements" section of the Design Guidelines for Audience Network Ads.

  • The video player must support the VPAID 2.0 spec. The Audience Network VPAID will fire the appropriate tracking metrics so you will not need to fire these events.

  • The video player must pass the full page URL in the ad-request. Also, the full-page url must be retrievable by the Audience Network VPAID or through IAB SafeFrame (publishers loading Audience Network in cross domain frames are required to implement SafeFrame) and must be consistent with the page URL specified as part of the request.

  • Cookies must be enabled.

  • Ensure your domains have been added and approved in the Audience Network UI.

  • Verify the In-stream Video VAST tag's 'pageurl' run-time parameter value is set to a macro that returns the Referring URL from the authorized domain.

  • Ensure Cookies are enabled from the browser. Note: Browser cookies can get corrupted and may cause a problem with the VAST response. Delete your browser cookies and cache to resolve the issue.

  • Ensure you have logged into Facebook from the browser (including mobile web when on a mobile device)

Each Video Player and Ad Server have their own macro to return the referring URL value. Please consult with your player development team or third party ad partner to determine the correct macro to use.

Yes. You can create multiple placements, each with its own VAST tag to implement.

From a VAST context, there is no passback as you would see in display. Instead, when there is no ad to serve, the In-stream Video VAST tag will return an empty response. When this occurs, the video player or ad server can select a different ad source.

Yes. We recommend that you create new placements for the mid-rolls to track their performance separately.

No. Audience Network targets 3rd party video players only.

No. The In-stream Video VAST tag is designed to run from the client's device.

Yes. The following tag will always return an Audience Network test video ad:


  • Ensure your inventory conforms to the In-Stream Video Requirements in the Design Guidelines for Audience Network Ads. Deviations from the requirements will result in the inability of Audience Network to respond with an ad.
  • Target video inventory that maximizes View Rates (10 second video view rate).
  • Implement In-stream Video on videos that have an intent to watch. For example, click-to-play inventory provides an intent to watch and may result in longer viewability.
  • Use frequency caps to limit the number of ad requests and impressions delivered to the same person.

If you have click-to-play inventory, one reason for this discrepancy may be that your video player is loading the In-stream Video VAST tag at page or player load (as opposed to loading the VAST tag when the user presses Play).

If the VAST tag returns an ad (Filled Request), then the impression will not be delivered until the user presses Play. If the user does not do this (e.g., closes the browser, navigates to a different page), then the ad request was filled, but the impression was lost thus causing the difference between these two metrics.


From the Performance section of the Audience Network dashboard, the publisher is able to report on: Requests, Filled Requests, Impressions, Clicks, Video Views, Fill Rate, CTR, View Rate, eCPM and Est. Revenue.

An Impression is recorded when the video ad starts playing and at least one pixel is in view.

A Video View represents 10 seconds of cumulative playing time for the video with at least 50% viewability.

The Audience Network VPAID will fire the appropriate tracking metrics so you will not need to fire these events.