diTii.com Digital News Hub

Sign up with your email address to be the first to know about latest news and more.

I agree to have my personal information transfered to MailChimp (more information)

Apr032018

Google Enabling Publishers Add User Consent Component on AMP Pages

Google is currently developing a new component for its open source Accelerated Mobile Pages (AMP) Project, that will provide web publishers easy tools to implement their preferred user controls as well as support for varied legal complicance requirements, like the forthcoming General Data Protection Regulation (GDPR).

AMP Project is working to give publishers and tech vendors tools to implement their preferred user controls and to support their varied individual compliance requirements on their AMP pages.

The new feature to be launhed soon can be integrated into AMP pages, so publishers can more easily implement what they deem necessary for their websites, like “notice, choice and consent flows.”

More specifically, it’ll offer publishers an ability to show choices in user interface notices via “accept” and “reject” semantics, and configuration of AMP element behaviors in response to users’ choices.

In addition, over 100 vendor-provided capabilities ranging from analytics to ad tech to video players and other kinds of content embeds are supported by AMP.

In a couple of weeks, to help publishers Google will publish documentation and examples for implementation of the new component. Meanwhile, publishers are encouraged to engage their vendor with AMP Project to ensure they integrate with new user control features.

“Approaches to implementing user controls and achieving compliance with laws, such as GDPR, will vary by publisher,” said Google.

Therefore, for more details everyone must check out the AMP Project GitHub.

Update 04/19: Google annoucned the initial availability of tools enabling publishers to build user controls in AMP pages today introduced a new <amp-consent> component.

This new component enables three main things:

Determining if a user should be asked to interact with the control by specifying a remote URL to ping in order for user to make a choice. Once the control is set up, a UI container completely configurable can be use to capture user’s choice within the page.

Capturing User’s Decision

Publisher can designate a button corresponding to currently supported either an “accept” or “reject” action and remember it during the current page llifecycle and future page loads. In addition, a “dismiss” action which will result in neither state can be set as well.

Modifying Element Behavior

Once a user has made a choice, a simple HTML attribute can be use to block AMP elements from loading if a user setting is in negative or undetermined state. This can be use to only load ads or analytics when a user consent is given.

Additionally, elements can be further customized for more sophisticated behaviors depending on user’s setting by the vendor.

Further, Google said it will add more features to <amp-consent> over time. Check out some already planned ideas on GitHub.

For getting started with implementation and configring am-consent, check out this documentation.

Share This Story, Choose Your Platform!

Get Latest News

Subscribe to Digital News Hub

Get our daily newsletter about the latest news in the industry.
First Name
Last Name
Email address
Secure and Spam free...