<amp-ad
width="300"
height="250"
type="adocean"
data-ao-id="ado-bIVMPpCJPX0.5tjQbNyrWpnws_dbbTJ1fUnGjLeSqJ3.K7"
data-ao-emitter="myao.adocean.pl"
data-block-on-consent
>
</amp-ad>
<amp-ad
width="300"
height="250"
type="adocean"
data-ao-emitter="myao.adocean.pl"
data-ao-master="FDyQKk0qN2a9SxwCMal6Eove..r_lvBE3pPfr_Ier9..f7"
data-ao-id="adoceanmyaonhqnqukjtt"
data-ao-keys="key1,key2,key3"
data-block-on-consent
>
</amp-ad>
<amp-ad
width="300"
height="250"
type="adocean"
data-ao-emitter="myao.adocean.pl"
data-ao-master="FDyQKk0qN2a9SxwCMal6Eove..r_lvBE3pPfr_Ier9..f7"
data-ao-id="adoceanmyaokiheeseoko"
data-ao-keys="key1,key2,key3"
data-block-on-consent
>
</amp-ad>
Do not define different values for slaves within one master for paramerters: data-ao-keys, data-ao-vars and data-block-on-consent. Otherwise, the behavior will be non-deterministic.
For details on the configuration semantics, see AdOcean documentation.
data-ao-id
- Ad unit unique iddata-ao-emitter
- Ad server hostname
data-ao-mode
- sync|buffered - processing modedata-ao-preview
- true|false - whether livepreview is enableddata-ao-keys
- additional configuration, see adserver documentation, do not define different values for slaves within one masterdata-ao-vars
- additional configuration, see adserver documentation, do not define different values for slaves within one masterdata-ao-clusters
- additional configuration, see adserver documentationdata-ao-master
- unique id of master placement
When user consent is required. AdOcean ad approaches user consent in the following ways:
CONSENT_POLICY_STATE.SUFFICIENT
: Serve a personalized ad to the user.CONSENT_POLICY_STATE.INSUFFICIENT
: Serve a non-personalized ad to the user.CONSENT_POLICY_STATE.UNKNOWN_NOT_REQUIRED
: Serve a personalized ad to the user.CONSENT_POLICY_STATE.UNKNOWN
: Serve a non-personalized ad to the user.