We’ve launched a new feature called “Render on Idle” now available for publishers using the DoubleClick AMP ad tag, and any ad network choosing to implement Fast Fetch can also take advantage of it. With Render on Idle, ads load 12 viewports from the user’s scroll position (as opposed to 3) when the browser is idle, no other page content is being retrieved or rendered. This delivers better ad performance by loading ads earlier in the page lifecycle.
In early tests with publishers using DoubleClick AMP ad tags, we’ve seen a 13% increase in impressions per page (giving Fast Fetch an overall +18% increase compared to Delayed Fetch) and 0.5% increase in clicks and viewable queries from this feature.
If you’re an ad network:
Consider migrating from Delayed Fetch to Fast Fetch to receive these benefits. See instructions here.
If you’re a publisher:
Most publishers won’t have to do anything and will automatically reap the benefits of using a Fast Fetch-enabled ad tag. However; there are a few exceptions that cause the AMP runtime to automatically fall back to delayed Fetch. The table below lists these exceptions and the mitigations that allow a publisher to take advantage of Fast Fetch. Note that Delayed Fetch will not be supported after 3/29/2018; please see this GitHub issue for more information.
In summary, if you are using remote.html for any reason, switch to using Real-Time Config (Instructions).
If you are using ‘useSameDomainRenderingUntilDeprecated’ in amp-ad, then remove this attribute your tags and instead, use the SafeFrame API, which is now exposed to ads on AMP pages (Help Center Article).
As always, we look forward to your feedback or questions.
Posted by Keith Wright, Technical Lead, AMP Project