Skip to content

Latest commit

 

History

History
88 lines (62 loc) · 2.43 KB

openx.md

File metadata and controls

88 lines (62 loc) · 2.43 KB

OpenX

Examples

  • All OpenX tags require the width, height, and type="openx" parameters.
  • Secure tags (HTTPS) are required for AMP.

OpenX Ad Server

Display an OpenX Ad Unit.

Required:

  • data-auid - The ad unit ID to display
  • data-host - SSL-enabled OpenX delivery domain
<amp-ad width="728" height="90"
      type="openx"
      data-auid="12345"
      data-host="domain.openx.net">
</amp-ad>

OpenX Bidder

OpenX header bidding. Parameters noted in the Doubleclick amp-ad documentation can be forwarded to Doubleclick by the following rules:

  1. Parameters like data-dfp-{name} will be converted to data-{name} and passed to Doubleclick
  2. Everything under the json "dfp" key will be passed to Doubleclick

Required:

  • data-host - SSL-enabled OpenX delivery domain
  • data-nc - Network code '-' sitename
  • data-dfp-slot - The Doubleclick slot

Optional:

  • json - Additional json options. Only the "dfp" is currently respected.
<amp-ad width="728" height="90"
      type="openx"
      data-host="domain.openx.net"
      data-nc="56789-MySite"
      data-dfp-slot="/12345/dfp_zone"
      json='{"dfp":{"targeting":{"sport":["rugby","cricket"]},"categoryExclusions":["health"],"tagForChildDirectedTreatment":1}}'>
</amp-ad>

Doubleclick Fallback

If no OpenX parameters are detected, the tag falls back to a proxy for the Doubleclick ad type. The same rules for parameter conversion apply here as for bidder.

Required:

  • data-dfp-slot - The Doubleclick slot

Optional:

  • json - Additional json options. Only the "dfp" is currently respected.
<amp-ad width="728" height="90"
      type="openx"
      data-dfp-slot="12345/dfp_zone"
      json='{"dfp":{"targeting":{"sport":["rugby","cricket"]},"categoryExclusions":["health"],"tagForChildDirectedTreatment":1}}'>
</amp-ad>