The AMP configuration for U.S. Privacy and/or GDPR TCF, though similar to web implementations, has particular requirements. In this article, we provide guidelines to help your organization configure your property, vendor list, messages, etc... for an AMP implementation.
- AMP property guidelines
- AMP vendor list guidelines
- AMP first layer and privacy manager guidelines
- AMP scenario guidelines
- AMP partition guidelines
- AMP campaign guidelines
|AMP configuration steps|
For implementation instructions, please follow the links below:
- AMP implementation (GDPR TCF)
- AMP implementation (U.S. Privacy)
- AMP implementation (GDPR TCF and U.S. Privacy)
- Configure sub-domain with CNAME DNS record (AMP)
- Re-consent scenario for AMP implementations
- Restrict consent collection to region (AMP)
- Display Privacy Manager (AMP)
- Block custom vendor scripts by using data-block-on-consent
AMP property guidelines
AMP properties need to be created separately from any regular webpage properties. An example of a property name could be
amp.visitdenmark.com. Since any AMP implementation imposes restrictions on vendor lists, this necessitates that AMP properties have their own separate names and vendor list.
AMP vendor list guidelines
Sourcepoint strongly recommends that your organization creates a separate vendor list solely for your AMP properties. Please regard the following restrictions when creating separate vendor lists for AMP properties:
- The consent type sent to AMP vendors is binary -
Rejected. The consent type will be
Rejectedif the end-user rejects one or more vendors. The vendor would need to check the consent string themselves to see if they were rejected.
AMP first layer message and privacy manager guidelines
Compliance rules & guidelines that govern messages for messages also apply to AMP messages. However, AMP messages have these additional stipulations:
- The first layer message must be a bottom notice.
- The first layer message should occupy between 30% and 60% of the screen.
- The end-user needs to be able to scroll behind the first layer message.
AMP scenario guidelines
When configuring a scenario for your AMP property, keep in mind that the following end-user actions are not sent to the client or vendor:
- Consented to all
- Not Consented to all
- Rejected to all
- Consented to any
- Rejected to any
- Not Rejected to any
The Sourcepoint CMP sends the status Accepted or Rejected together with the consent string to the Google AMP client and vendors. The Google AMP client and vendors decide what to do upon receiving this response.
AMP partition guidelines
Your organization can configure AMP partitions without additional restrictions. Click here for more information on creating partitions.
AMP campaign guidelines
Your organization can create AMP campaigns without additional restrictions. Click here for more information on creating campaigns.