This document provides guidance on how to integrate the Sourcepoint CMP (Consent Management Platform) with your AMP (Accelerated Mobile Pages) inventory. To perform this integration you should have some level of technical knowledge, be able to update your Sourcepoint configuration to add AMP Properties, and access to update the AMP website code.
The process for setting messages, scenarios, partitions and campaigns is the same as the process for setting up any consent messaging campaign. However, the process for setting up properties, vendor lists and privacy manager may differ.
The process for setting up an AMP property is generally the same as the process for setting up a property for any other messaging campaign. It is recommended that you set up an alternate property to deliver messages on AMP pages. This will allow you to set up separate vendor lists for AMP pages. Examples of an AMP property name for the site www.example.com would be www.amp.example.com and amp.example.com.
For more information on how to create a new property, please visit the "How to Add A Property" article.
Messages for AMP are created using the Sourcepoint's new Message Builder 2 product. For more information on creating a message using Message Builder 2, please visit the "How to Create a Message Version" in version 2 of the messaging section.
The steps for setting up a scenario, partition and campaign are the same as the steps for creating messages, scenarios and campaigns for any messaging campaign. Please see the sections listed below for more information.
There is only one minor difference in setting up a vendor list for AMP pages. For AMP pages, you should not create any consent or reject actions in vendor lists.
After you have created a property in the Sourcepoint user interface, you can integrate the Sourcepoint CMP into your AMP website by using the amp-consent component, and inserting the proper attributes in the amp-consent component tags. The example code below will display a demo message on a test page. To configure the code to show a message from your account, you would change the parameters listed to correspond to your account set up.
accountId - this corresponds to the account ID in the Sourcepoint UI.
siteName - this attribute is the same as the property name set up in the "Setting Up An AMP Property" above in this document.
siteId - this attribute is optional and corresponds to the ID of the property being used.
privacyManagerId - this attribute corresponds to the ID of the privacy manager used for this site. You can find a privacy manager's ID by selecting the privacy manager in the Sourcepoint UI and grabbing the ID from the URL. In the screenshot below the ID for the privacy manager is
targetingParams - this is optional, but if you want to provide additional key-value pair targeting variables to customize language or create a more relevant user experience they would be listed here. In the example below, the key would be "foo" and the value would be "bar".
postPromptUI - this is the reference to on-page element that will display after a user has provided consent. When this element appears a user can click on it to change their consent preferences.
<amp-consent id='consent' layout='nodisplay' type='SourcePoint'>
<button on="tap:consent.prompt(consent=SourcePoint)">Privacy Settings</button>
The IAB consent string is collected and passed into AMP pages; however, all vendors are either consented to or rejected. At this time, AMP pages do not support granular opt-in/opt-out for individual vendors and purposes. You should check with your vendors to confirm that they have updated their support for the IAB framework.
Non-IAB vendors are handled by adding the
data-on-block-consent attribute to any tag. Below is an example of a tag for Google Analytics.
The postPrompt UI is the button a user can click on the resurface a privacy manager after the user has made a consent choice. The UI is constructed from available AMP HTML elements directly on the page. After the user has interacted with the consent message, the postPromptUI will be displayed. The elements for the postPrompt UI need to placed within the the <amp-consent> component.
Prior to launching the campaign to the general public, you can create a campaign in a stage environment to test the consent experience on a production site. To do this, you set the
"stageCampaign": true . This allows you to test the user experience in a production environment without exposing the campaign to the general public.