Integrate your ad technologies into AMP
If you are an ad technology provider looking to integrate with AMP HTML, please see the guidelines below. To ensure minimum latency and quality, please follow the instructions listed here before submitting a pull request to the AMP open-source project. For general guidance on how to get started with contributing to AMP, please see docs/contributing.md.
Examples : DFP, A9
amp-ad tag to request ads from your ad server.
For example : Amazon A9 server can be invoked by using following syntax:
<amp-ad width="300" height="250" type="a9" data-aax_size="300x250" data-aax_pubname="test123" data-aax_src="302" > </amp-ad>
Note that each of the attributes that follow
https://c.amazon-adsystem.com/aax2/assoc.js URL. The corresponding parameters passed by the AMP ad tag are appended to the URL to return an ad.
For details on how to integrate your ad network with AMP, see Integrating ad networks into AMP.
Supply Side Platform (SSP) or an Ad Exchange
Examples : Rubicon, Criteo OR Appnexus, Ad-Exchange
If you are a sell-side platform that wants to get called directly from a publisher’s webpage, you will need to follow the same directions as listed above for integrating with an Ad Server. Adding your own
type value to the amp-ad tag allows you to distribute your tag directly to the publisher, so they can insert your tags directly into their AMP pages.
More commonly, SSPs work with the publisher to traffick the SSP’s ad tags in their ad server. In this case, ensure that all assets being loaded by your script in the ad server’s creative are being made over HTTPS. There are some restrictions around some ad formats like expandables, so we recommend that you test out the most commonly delivered creative formats with your publishers.
Examples : Essence, Omnicom
Work with your publisher to ensure that the creatives you develop are AMP-compliant. Since all creatives are served into iframes whose size is determined when the ad is called, ensure that your creative doesn't try to modify the size of the iframe.
Ensure that all assets that are part of the creative are requested using HTTPS. Some ad formats are not fully supported at the moment and we recommend testing the creatives in an AMP environment. Some examples are : Rich Media Expandables, Interstitials, Page Level Ads.
Examples : Brightcove, Ooyala
A video player that works in regular HTML pages will not work in AMP and therefore a specific tag must be created that allows the AMP Runtime to load your player. Brightcove has created a custom amp-brightcove tag that allows media and ads to be played in AMP pages.
A Brightcove player can be invoked by the following:
<amp-brightcove data-account="1290862519001" data-video-id="ref:amp-docs-sample" data-player="S1Tt8cgaM" layout="responsive" width="480" height="270" > </amp-brightcove>
For instructions on how to develop an amp tag like Brightcove, see this pull request.
Video Ad Network
Examples : Tremor, Brightroll
If you are a video ad network, please work with your publisher to ensure that:
- All video assets are served over HTTPS
- The publisher’s video player has AMP support
Data Management Platform (DMP)
Examples : KRUX, Bluekai
See how to enhance custom ad configuration.
You can use a similar approach to enrich the ad call by passing in audience segments that you get from the user cookie into the ad call.
Examples : MOAT, Integral Ad Science
Viewability providers typically integrate with publishers via the ad server’s creative wrappers. If that is the case, ensure that the creative wrapper loads all assets over HTTPS.
For e.g. for MOAT, make sure
http://js.moatads.com is switched to
Also, see the approach to using the intersection observer pattern.
Examples : Taboola, Outbrain
amp-embed extension to request the content details. Please see the Taboola example.