Starting 1 April, 2024, new video publisher policies will apply to all video inventory monetized by Ad Manager, AdMob and AdSense publishers. The intentions of these updates are to better align our policies with changing industry standards and buyer expectations, and to simplify our policies so that our requirements are more clear to publishers and advertisers. In the interim period, the existing Ad Manager video publisher policies and AdSense video publisher policies will still apply, and we wanted to provide a summary of key differences between the existing and upcoming policies:
- Accurate inventory description:
- Our existing policy indicating that publishers must "use metadata and declarations to accurately describe inventory" will continue to hold. However, we want to stress the importance of publishers passing two signals important for programmatic video buyers: For Ad Manager publishers, this is the
vpmute
field and the newplcmt
field that supports this year’s IAB OpenRTB video update. - Publishers should accurately send the full set of video ad tag parameters, including description URLs and ad placement size, to improve discovery and transparency for buyers and to improve monetization.
- Aligning with the latest IAB OpenRTB video.plcmt definitions removes the need to clarify examples that should not be considered in-stream.
- Our existing policy indicating that publishers must "use metadata and declarations to accurately describe inventory" will continue to hold. However, we want to stress the importance of publishers passing two signals important for programmatic video buyers: For Ad Manager publishers, this is the
- Supported implementations:
- In addition to IMA SDK, the new policy language also specifies the generally available Programmatic Access Library (PAL SDK) as an option for "In-stream" or "Accompanying Content" video placements.
- For placements outside of a video player, publishers must use GPT or GMA SDK to monetize "Interstitial" or "Standalone" video placements.
- Protecting advertiser value:
- There's continued emphasis on ensuring video content or controls aren't obstructed or non-functional.
- We’ve updated the video policies to specify that audio ads must not be requested or served into muted video placements.
- We removed requirements around standard aspect ratios and minimum ad sizes, as buyers can appropriately identify and target the inventory they want based on placement size signals.
- User respect:
- We’re clarifying our policies on autoplay behavior:
- Only one video placement can autoplay with sound at any time, and only one "In-stream" or "Accompanying Content" placement can autoplay in view at any time.
- Autoplaying placements can only start playback when 50% of the ad unit is visible.
- We removed mentions of sum duration of video ads, as there is already an existing policy around more ads than publisher content.
- The new policies introduce conditions for "sticky" video ads, emphasizing the need for a dismiss option. Per an earlier policy update, "Interstitial" and "Standalone" placements can now be anchored in sticky units via GPT SDK. Any "In-stream" and "Accompanying Content" placement still must first render in the body of the page before transitioning to a sticky placement.
- We’re clarifying our policies on autoplay behavior:
It’s important to note that general Google Publisher Policies still apply. While these policies outline the minimum guidelines to monetize video inventory, different video implementations and signals may result in varying levels of monetization from different buyers. For example, standard aspect ratios (4:3 or 16:9 for horizontal videos; 3:4, 4:5, or 9:16 for vertical videos; or 1:1 for square videos) and audible placements generally result in higher monetization. We advise partners to experiment to find the setup that works best for them. Overall, with these new policies, we believe we’re taking a step forward in increasing transparency to buyers, upholding our high standards for inventory health, and optimizing the value we bring to our publishers.