2. Implement GDPR for AMP

After you have finished the configuration of Privacy Manager GDPR for AMP it’s time for implementation.

Implementation

Privacy Manager can be configured via Console and changed after implementation. Geo detection and the Privacy Manager Button are configured as part of the script and will require an update of your implementation.

Step 1 - Configure the Script

Download the GDPR for AMP script from the admin section in the configuration.

Block Content When Privacy Manager is Shown

By default the page content before consent is blocked by Privacy Manager when the notice is shown. If you want to disable the “content blocking", you can remove the overlay attribute from your configuration.

Privacy Manager Button

After the user has given consent or closed the consent notice, as per TCF policy you must give them easy access to their choices. The Privacy Manager Button can be used to resurface the Privacy Manager. The styling configuration for the Privacy Manager Button is included in the Configuration Script and reflects the settings from the editor. Note that any changes made in the editor after the scripts was implemented will not be shown.

If you wish to apply custom styling to the means of resurfacing the Privacy Manager, you can do so by editing the content inside the div id="post-consent-ui"

Format

GDPR for AMP is embedded by AMP in an iframe that appears at the bottom of the page with a defined height, we currently support and force notice.position to bottom in the configuration object. On some older devices and and OS versions the notice will be displayed as a modal in the center of the page.

Step 2 - Define Geo Targeting

If you are a company based outside of the EU and only want to require the consent in EU, you can configure Privacy Manager to only load in EU. It is possible to selectively load GDPR for AMP in specific countries using the amp-geo component. Note that you will need to update the script in your AMP page in order for any changes to reflect on your site. Check out "Geo Detection on AMP" for a step by step description on how to enable geo targeting.

Step 3 - Add Privacy for AMP to your site

Add the amp-consent script to your AMP page. Check the AMP documentation for more details on how to implement.

Step 4 - AMP Consent Blocking

In order to avoid potential errors from AMP validator it is advisable to add <meta name="amp-consent-blocking" content=""> in the top of your page. This meta tag will allow blocking a set of tags for the entire page. For example <meta name="amp-consent-blocking" content="amp-ad"> will block all the amp-ad tags on the page.

For more detailed information on amp-consent setting up blocking behaviour, please review the related articles.

The root page Blocking Logic for GDPR for AMP could not be found in space LiveRamp Privacy Manager.