AMP Pages, Stories, and AMPHTML ads


AMPHTML ads are a better way of building, delivering, and measuring ads that are faster, lighter, and more secure. AMPHTML ads are ads built using AMPHTML and use many of the smart components that make AMP pages fast (such as <amp-analytics>).

These ads are only delivered after being validated, ensuring that they’re free of malware. Best of all, these ads can be delivered anywhere on the web, not just on AMP pages. AMPHTML ads achieves the goal of making ads themselves as fast as the rest of the AMP page.

AMPHTML ads can serve on both AMP pages and non-AMP pages. This includes both desktop and mobile web environments. Learn more about AMPHTML ads on non-AMP pages.

There is no frontend visual indication to users that an ad being served is built in AMPHTML versus another type of ad.

Reservations with AMPHTML ads

To deliver AMPHTML ads on non-AMP pages no special integration is required.

We don't recommend using the <amp-analytics> tag with AMPHTML ads for click tracking purposes, because the JavaScript for this tag may not have loaded by the time a click occurs, resulting in undercounting of clicks.

AMPHTML ads on non-AMP pages

AMPHTML ads can serve on both AMP pages (via the Ad Manager AMPHTML ad tag) and non-AMP pages (via the Google Publisher Tag).

On non-AMP pages, AMPHTML ads serve into a friendly iframe, further improving ad latency and performance. If you would like to move AMPHTML ads into a cross-domain SafeFrame, you can do so by calling setForceSafeFrame() (page level or slot level) with GPT.

AMPHTML as a demand source

AMPHTML ads may appear in any ad slot where a bidder may supply a plain HTML creative.

When the demand comes from Google via Ad Exchange or Google Ads, Ad Manager will automatically serve AMPHTML ads over non-AMPHTML ads when we know:

  • The AMPHTML ad will function correctly.
  • Serving the AMPHTML ad benefits your web performance.
  • Serving the AMPHTML ad benefits your users.

Ad Manager serves AMPHTML ads over regular ads on both AMP and non-AMP pages (via Google Publisher Tag).

Was this helpful?

How can we improve it?
Clear search
Close search
Google apps
Main menu