Consent & re-consent scenario for AMP implementations

When creating scenarios for AMP implementations your organization can set up end-user workflows for consent and re-consent. Scenarios for AMP implementations are very similar to web GDPR & CCPA implementations.

However there is a small difference in (re-)consent scenarios depending on the value for checkConsentHref in the <amp-consent> component.

  Note: Please remember that the Regex logic gate will not work in AMP scenarios.

  Note: Please check the checkConsentHref value in the <amp-consent> component. It will be needed in the following sections.


Where checkConsentHref value ends in '/amp'

If your <amp-consent> component has the checkConsentHref value ending in '/amp' then your organization should use 'Show Message Always' logic gate in the Sourcepoint dashboard's scenario setup.

  Note: If amp is included in your checkConsentHref, you are utilizing a legacy version. While consent & re-consent scenarios will still work we strongly recommend that you update your configuration to amp-v2 described later.

<amp-analytics>
   <script type=application/json>
      {
         "linkers": {
"authId": {
"ids": {
"_a": "CLIENT_ID(AMP-CONSENT)"
},
"enabled": true,
"proxyOnly":false
}
},
"cookies": {
"enabled": true,
"authId": {
"value": "LINKER_PARAM(authId, _a)"
}
} } </script> </amp-analytics> <amp-consent id="consent" layout="nodisplay"> <script type="application/json"> { "consentInstanceId": "Sourcepoint", "consentRequired": "remote", "checkConsentHref": "https://sp-cdn.example.com/wrapper/tcfv2/v1/amp", "promptUISrc": "https://sp-cdn.sp-demo.com/amp/index.html?authId=CLIENT_ID", "mmsDomain": "https://sp-cdn.sp-demo.com", "postPromptUI": "consent-ui", "cookies": { "enabled": true, "AMP-CONSENT": { "value": "LINKER_PARAM(authId, _a)" } }, "clientConfig": { "accountId": 1732, "propertyHref": "https://amp.newscriptdemo.com", "propertyId": 19118, "privacyManagerId": 547514, "isTCFV2": true, "pmTab": "purposes", "stageCampaign": false, "targetingParams": { "color": "red" } } } </script> </amp-consent>
dot_amp.png

Where checkConsentHref value ends in '/amp-v2'

If your <amp-consent> component has the checkConsentHref value ending in '/amp-v2' the setup of your AMP scenario will be the same as web GDPR & CCPA implementations.

Your organization should use the 'TCFv2 No Action' logic gate followed by the 'Show Message Always' logic gate in the Sourcepoint dashboard's scenario setup.

<amp-analytics>
   <script type=application/json>
      {
         "linkers": {
"authId": {
"ids": {
"_a": "CLIENT_ID(AMP-CONSENT)"
},
"enabled": true,
"proxyOnly":false
}
},
"cookies": {
"enabled": true,
"authId": {
"value": "LINKER_PARAM(authId, _a)"
}
} } </script> </amp-analytics> <amp-consent id="consent" layout="nodisplay"> <script type="application/json"> { "consentInstanceId": "Sourcepoint", "consentRequired": "remote", "checkConsentHref": "https://sp-cdn.example.com/wrapper/tcfv2/v1/amp-v2", "promptUISrc": "https://sp-cdn.sp-demo.com/amp/index.html?authId=CLIENT_ID", "mmsDomain": "https://sp-cdn.sp-demo.com", "postPromptUI": "consent-ui", "cookies": { "enabled": true, "AMP-CONSENT": { "value": "LINKER_PARAM(authId, _a)" } }, "clientConfig": { "accountId": 1732, "propertyHref": "https://amp.newscriptdemo.com", "propertyId": 19118, "privacyManagerId": 547514, "isTCFV2": true, "pmTab": "purposes", "stageCampaign": false, "targetingParams": { "color": "red" } } } </script> </amp-consent>
dot_amp_v2.png
Was this article helpful?
0 out of 0 found this helpful