AMP Cookie Consent

  • Updated

The principle of AMP is to lighten the pages by structuring the HTML in a common and predefined way. The AMP project is led by Google and functions via a CDN (content delivery network). The AMP project is open-source.

AMP pages can only include very limited amounts of JavaScript and much of the page is often cached by intermediaries in order to further accelerate delivery to mobile devices which often have limited bandwidth. AMP pages are intended to be static non-interactive documents.

Because of these limitations imposed by the AMP standard, the Osano Consent Manager will not execute on AMP pages. Good news though, the same restrictions that prevent the Osano CMP from functioning on AMP pages also prevent most if not all javascript widgets/embeds which would then set cookies.

You can learn more about the AMP project here or the restrictions on JavaScript within AMP pages here

So what should you do for disclosures on AMP pages? Our recommendation is to place a simple text disclosure at the TOP of the document explaining your data privacy practices and linking to your privacy policy. As well, Osano recommends that you ensure that absolutely no advertisers are loaded on AMP pages.