These tables provide a summary of features available for AMPHTML ads in Ad Manager. Consult the "Ads" section of the AMP roadmap for new innovations.
AMPHTML ads can serve on both AMP pages (via the Ad Manager AMPHTML ad tag) and non-AMP pages (via Google Publisher Tag). This includes both desktop and mobile web environments.
Future versions of AMP may have an expanded list of available features. You can read the newest AMP functionalities in the public AMP runtime release notes.
Rich media ads
There are two types of rich media ads:
- Expressive ads: ads which are more expressive in the default state post-rendering. For example, ads with video, audio, or animations, versus a simple image or text ad. These ads are supported by AMP by default because AMP renders these ads into an iFrame and executes the ads as-is.
- Interactive ads: ads which show a different state of the ad when the user interacts with it. For example, on interaction, an ad that expands to the full screen of the device and allows the user to play a video game within the ad itself. As long as the ad network serving the ad supports the SafeFrame API, interactive ads should have no problem rendering on AMP pages.
AMP pages have specific rules around causing reflow without user interaction. Read more about Google Ad Manager’s SafeFrame API support in AMP pages.
Creative types compatible with AMPHTML
SRA: Single Request Architecture
Make a single request for all ad slots on the AMP page, which allows you to do roadblocking and competitive exclusions. SRA is a feature of the Fast Fetch request method.
Learn more about the AMP Ad tag