Introduction to advertising on AMP
The AMP Project's goals are to do what's best for the user by helping to deliver fast web pages. Advertising on AMP embraces those same goals by supporting ads that are fast, safe, compelling and effective for users. How does that get done?
Delivering ads to AMP pages is not much different than serving traditional ads on HTML pages:
<amp-ad>tag to their AMP page for a particular ad network. To learn the details, see the Monetizing your AMP page with ads guide.
When the user loads an AMP page, the
<amp-ad>tag sends an ad request to the ad network. To return an ad to the AMP page, ad networks build an
amp-adimplementation. To learn the details, see the Integrating ad networks into AMP guide.
Ad networks supply creatives built by advertisers. Advertisers can build creatives using traditional HTML, or in the new format, AMPHTML.
Supported ad networks
AMP supports a large number of ad servers and networks.
AMP supports both traditional ads, and the faster, more secure AMPHTML ads. Regardless of how they are built, ads on AMP pages are like any external resource and must play within the same constraints placed on all resources in AMP. To learn more about ad requirements in AMP, see this guide.
Faster ads with AMPHTML ads
AMPHTML ads are a faster, lighter and more secure way to advertise on the web. Although AMP pages support traditional HTML ads, these ads can be slow to load. To make ads themselves as fast as the rest of the AMP page, you can build ads in AMPHTML. AMPHTML ads are only delivered after being validated, ensuring that the ads are free of malware. Most of all, these ads can be delivered anywhere on the web, not just on AMP pages.
Learn more about AMPHTML ads in the AMPHTML ads guide.
Visit these resources to get started with ads in AMP: