Re-consent Scenario for AMP Implementations

Organization's who have implemented AMP can utilize Sourcepoint's re-consent workflows when creating Scenarios. The re-consent workflow for AMP is dependent on how your organization has implemented your <amp-consent> component. See below for more information:
Note: If you haven't done so already, be sure to set checkConsentHref in the parent JSON object and not the clientConfig object in the amp-consent component. 
checkConsentHref = ……./amp
If your AMP consent component <amp-consent> has checkConsentHref = ……./amp then your organization should use  Show Message Always.
 <amp-consent id='consent' layout='nodisplay' type='SourcePoint'>
        <script type="application/json">
  {
            "consentRequired": "remote",
            "consentInstanceId": "sourcepoint",
            "checkConsentHref": "https://sp-cdn.example.com/wrapper/tcfv2/v1/amp",
            "promptUISrc": "https://ddhmlhfna6zcj.cloudfront.net/index.html?authId=CLIENT_ID",
            "postPromptUI": "consent-ui",
            "uiConfig": {"overlay":true},
            "clientConfig": {
                "accountId": 22,
                "env": "stage",
                "wrapperAPIOrigin": "https://wrapper-api.sp-stage.net/tcfv2",
                "propertyId": 595,
                "propertyHref": "http://automation.com",
                "scriptUrl": "https://gdpr-tcfv2.sp-prod.net/1.2.11/wrapperMessagingWithoutDetection.js",
                "isTCFV2": true,
                "pmTab": "vendors",
                "privacyManagerId": 5477,
                "stageCampaign": false,
                "mmsDomain": "https://mms.sp-stage.net"
            }
        }
    </script>    <div id="consent-ui">
      <button on="tap:consent.prompt(consent=SourcePoint)">Privacy Settings</button>
    </div>
</amp-consent>
 checkConsentHref = ……/amp-v2
If the amp consent component <amp-consent> has checkConsentHref = ……/amp-v2 then your organization should create a re-consent workflow using TCFv2 No Action step followed by a Show Message Always step.
 <amp-consent id='consent' layout='nodisplay' type='SourcePoint'>
        <script type="application/json">
  {
            "consentRequired": "remote",
            "consentInstanceId": "sourcepoint",
            "checkConsentHref": "https://sp-cdn.example.com/wrapper/tcfv2/v1/amp-v2",
            "promptUISrc": "https://ddhmlhfna6zcj.cloudfront.net/index.html?authId=CLIENT_ID",
            "postPromptUI": "consent-ui",
            "uiConfig": {"overlay":true},
            "clientConfig": {
                "accountId": 22,
                "env": "stage",
                "wrapperAPIOrigin": "https://wrapper-api.sp-stage.net/tcfv2",
                "propertyId": 595,
                "propertyHref": "http://automation.com",
                "scriptUrl": "https://gdpr-tcfv2.sp-prod.net/1.2.11/wrapperMessagingWithoutDetection.js",
                "isTCFV2": true,
                "pmTab": "vendors",
                "privacyManagerId": 5477,
                "stageCampaign": false,
                "mmsDomain": "https://mms.sp-stage.net"
            }
        }
    </script>    <div id="consent-ui">
      <button on="tap:consent.prompt(consent=SourcePoint)">Privacy Settings</button>
    </div>
</amp-consent>
Block Custom Vendor Scripts by Using data-block-on-consent
Next - Consent Management Platform (CMP)
Consent Management Platform (CMP) Overview
Last updated 2 days ago