Page Comparison

...

• Define and Request only what will be immediately rendered.

  • In some scenarios it might be useful to define and prepare all ad slots which will ever be displayed on page.

  • However, if some ad slots are never rendered these ad requests may reduce the fill % on the page, as well as possible SPO/optimization by buyers which exclude your inventory.

• Keep the number of ad slots to less than 4

  • To improve view-ability and user experience we recommend limiting the number of active ad slots to 4, ensuring to keep them as view-able as possible.

• Timeouts

  • A timeout of at least 1000ms is recommended per bidder unless most of your inventory is on slow mobile connections, in which case increasing the timeout to 3000ms is recommended.

• Define, request, and render ad slots as they near view

  • If you are lazy loading ads on long article pages we recommend defining the new ad slots, making requests, and rendering the ad as the user scrolls through content and nears the ad slot.

  • This benefits the page by minimizing the ad load and reduces resources until such a time they are required.

• Avoid creating new ad slots when you want to refresh ads

  • We recommend using Prebid’s documented refresh functionality.

• Keep it simple

  • Avoid wrapping Prebid functionality in classes, functions, namespaces, etc

  • If you obfuscate Prebid you may introduce additional complexity when needing to troubleshoot

• Add User ID Modules

• 7: Full Screen

  Provide the position of the ad unit if possible, following , using the banner.pos field (Open RTB Spec:

• 1: Above the Fold

• 3: Below the Fold

• 4: Header

• 5: Footer

• 6: Sidebar

Placement Positions)

• For Prebid.js version 6.7.0 and above, Sharethrough supports first party data, as documented in this Prebid Guide.

...