ads/vendors/openx.md
<amp-ad> tags require the width, height, and type="openx" parameters.Display an OpenX Ad Unit.
Required:
data-auid - The ad unit ID to displaydata-host - SSL-enabled OpenX delivery domainOptional:
json - Additional json options.
customVars - please refer to the documentation.<amp-ad
width="728"
height="90"
type="openx"
data-host="domain.openx.net"
data-auid="12345"
json='{"dfp":{"targeting":{"sport":["rugby","cricket"]},"categoryExclusions":["health"],"tagForChildDirectedTreatment":1},"openx":{"customVars":{"marco":"polo","fates":["clothos","lachesis","atropos"]}}}'
>
</amp-ad>
OpenX header bidding. Parameters noted in the DoubleClick amp-ad documentation can be forwarded to DoubleClick by the following rules:
data-dfp-{name} will be converted to data-{name} and passed to DoubleClickRequired:
data-host - SSL-enabled OpenX delivery domaindata-nc - Network code '-' sitenamedata-auid - Open X Ad unit id to displaydata-dfp-slot - The DoubleClick slotOptional:
json - Additional json options.
customVars - please refer to the documentation. Also note that OpenX bidder limits these keys by the allowlisted keys set on your publisher settings.<amp-ad
width="728"
height="90"
type="openx"
data-host="domain.openx.net"
data-auid="12345"
data-nc="56789-MySite"
data-dfp-slot="/12345/dfp_zone"
json='{"dfp":{"targeting":{"sport":["rugby","cricket"]},"categoryExclusions":["health"],"tagForChildDirectedTreatment":1},"openx":{"customVars":{"marco":"polo","fates":["clothos","lachesis","atropos"]}}}'
>
</amp-ad>
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 slotOptional:
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>