Add a consent revocation link to your app or site

Consent revocation is the process by which users in the EEA (European Economic Area), the UK, and Switzerland who consented to personalized ads can revoke that consent. You must provide a link in your site or app's menu that allows users who want to revoke consent to do so, then present the consent message to those users again.

Consent revocation function for apps

Visit the developer documentation to learn more:

• Android
• iOS

Consent revocation function for sites

Use Privacy & Messaging JavaScript API to display a revocation link on a site. Use the following function to call the revocation flow: googlefc.callbackQueue.push(googlefc.showRevocationMessage)

Consent revocation function for AMP ^(Beta) 

Complete the following steps to call the revocation flow:

1. Place the following consent revocation code before the "clientConfig" attribute within the <amp-consent> tag in your site's HTML code: "postPromptUI": "fcConsentRevocation"

   Code sample

   <amp-consent id="googlefc" layout="nodisplay" type="googlefc">
     <script type="application/json">
       {
   "postPromptUI": "fcConsentRevocation",
          "clientConfig": {
            "publisherIdentifier": "[unique publisher ID]"
          }
       }
     </script>
   </amp-consent>
2. Place the consent revocation link code after the closing </amp-consent> tag in your site's HTML code to call the revocation flow:

   Code sample

   <div id="fcConsentRevocation">
   <button on="tap:googlefc.prompt(consent=googlefc, expireCache=true)">Manage

      Privacy Options</button>
</div>

The code within the fcConsentRevocation <div> tag is fully customizable. After you've implemented the code, you can adjust it as needed, but any changes to the code must adhere to the following guidelines:

• You must include the button with the special syntax.
• The <div> ID must match the postPromptUI value in the <amp-consent> HTML code.

  Example

  <div id="fcConsentRevocation"> should match "postPromptUI": "fcConsentRevocation"

• The <amp-consent> ID must match the tap value in the button HTML code.

  Example

  <amp-consent id="googlefc" [...] > should match <button on="tap:googlefc.prompt [...]" >