The AMP implementation for CCPA and GDPR TCFv2, though similar to web implementations, has particular requirements. In this article, we will cover these guidelines to help your organization with your AMP implementation.
AMP properties need to be created separately from any regular webpage implementation. An example of a property name could be
amp.visitdenmark.com. AMP implementation imposes restrictions on vendor lists and this necessitates that AMP properties have their own separate names and vendor list.
Click here for more information about creating properties.
There are restrictions when creating separate vendor lists for AMP properties:
The consent string for AMP implementations has a limit of 1200 characters. This restricts the number of vendors in the vendor list to no more than 200 vendors.
The consent type sent to AMP vendors is binary -
Rejected. The consent type will be
Rejected if the end-user rejects one or more vendors. The vendor would need to check the consent string themselves to see if they were rejected.
Click here for more information about creating vendor lists.
Compliance rules & guidelines that govern web implementations also apply to AMP. However, AMP implementations 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
Click here for more information on creating messages.
AMP scenarios are created the same way as web implementations. Click here for more information on creating messages.
However, due to restrictions in the consent type described here, the following end-user actions is 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
"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.
Your organization can create AMP partitions in the same way as web implementations with no restrictions. Click here for more information on creating messages.
Your organization can create AMP campaigns in the same way as web implementations with no restrictions. Click here for more information on creating messages.