If you want to serve ads via your Ad Server then there is no need to use the adapter when using Smart Tags. These can simply be served via your Ad Server in the normal fashion. You simply need to ensure that you are using secure tags (https).
The Rubicon Project adapter supports Smart Tags and FastLane directly on the page.
The FastLane (Single Slot) runs FastLane at the slot level and then calls DFP passing in the additional targeting data.
<amp-ad width=320 height=50
type="rubicon"
data-method="smartTag"
data-account="14062"
data-site="70608"
data-zone="335918"
data-size="43">
</amp-ad>
<amp-ad width="320" height="50"
type="rubicon"
data-method="smartTag"
data-account="14062"
data-site="70608"
data-zone="335918"
data-size="43"
data-kw="amp"
json='{"visitor":{"age":"18-24","gender":"male"},"inventory":{"section":"amp"}}'>
</amp-ad>
<amp-ad width=320 height=50
type="rubicon"
data-method="fastLane"
data-slot="/5300653/amp_test"
data-account="14062"
data-pos="atf">
</amp-ad>
<amp-ad width="320" height="50"
type="rubicon"
data-method="fastLane"
data-slot="/5300653/amp_test"
data-account="14062"
data-pos="atf"
data-kw="amp"
json='{"targeting":{"kw":"amp-test","age":"18-24","gender":"male","section":"amp"},"visitor":{"age":"18-24","gender":"male"},"inventory":{"section":"amp"}}'>
</amp-ad>
For semantics of configuration, please contact your Rubicon Account Director @ Rubicon Project
By default the ad size is based on the width
and height
attributes of the amp-ad
tag.
data-method
data-account
data-site
data-zone
data-size
data-method
data-slot
data-account
data-pos
Supported via json
attribute (DFP parameters):
targeting
categoryExclusions
tagForChildDirectedTreatment
cookieOptions
For the most up-to-date list of Doubleclick supported parameters and usage please refer to Doubleclick reference guide here.
data-kw
json
- for visitor and inventory data