By placing a button or link to your Privacy Manager on your property configuration, you allow end-users to manage their consent preferences on an ongoing basis without having to re-encounter your organization's First Layer message.
The postPromptUI
parameter in your <amp-consent>
component defines the page element (UI) that should be displayed to users (e.g. button or link styling).
<amp-consent id='consent' layout='nodisplay' ><script type="application/json">{"consentRequired": "remote","consentInstanceId": "SourcePoint","checkConsentHref": "https://sp-cdn.example.com/wrapper/tcfv2/v1/amp-v2","promptUISrc": "https://sp-cdn.example.com/amp/index.html?authId=CLIENT_ID","postPromptUI": "consent-ui","uiConfig": {"overlay":true},"clientConfig": {"accountId": 222,"mmsDomain": "https://sp-cdn.example.com","propertyHref": "https://amp.property.tcfv2","propertyId": 1234,"privacyManagerId": 987654,"isTCFV2": true,"pmTab": "purposes","stageCampaign": false,"targetingParams": {"color": "red"}}}</script></amp-consent>
The Privacy Manager can be resurfaced by adding the following on
attribute to a link or button on your property:
on="tap:consent.prompt(consent=SourcePoint)"
Examples for links and buttons can be found below:
<a on="tap:consent.prompt(consent=SourcePoint)" target="_self" href="#" id="consent-ui">Privacy Settings</a>
<div id="consent-ui"><button on="tap:consent.prompt(consent=SourcePoint)">Privacy Settings</button></div>
​
​