Implementation Guidelines (AMP)
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.
Click here for more information on how to implement the Sourcepoint CMP for AMP properties.

AMP property guidelines

Note: Sourcepoint's multi-campaign feature is currently unavailable for AMP properties. Please utilize Campaign (Legacy) for AMP properties.
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.

AMP vendor list guidelines

Sourcepoint strongly recommends that your organization creates a separate vendor list solely for your AMP properties.
There are restrictions when creating separate vendor lists for AMP properties:
  • The consent type sent to AMP vendors is binary - Accepted or 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.
  • Custom javascript for vendor consent and reject actions are not allowed in the vendor list. This will break the implementation.
Click here for more information about creating vendor lists.

AMP first layer message and privacy manager guidelines

Sourcepoint strongly recommends that your organization creates separate first layer messages and privacy managers solely for your AMP properties.
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 scenario guidelines

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 "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 create AMP partitions in the same way as web implementations with no restrictions. Click here for more information on creating messages.

AMP campaign guidelines

Your organization can create AMP campaigns in the same way as web implementations with no restrictions. Click here for more information on creating messages.
Last modified 1mo ago