Instructions for Loading Consent Management Platform (CMP)

To ensure compliance and optimal functionality, it's crucial that your Consent Management Platform (CMP) is configured correctly. Follow these instructions to ensure that the Consent Mode default command and/or the TCF (Transparency and Consent Framework) stub load before any Google tags fire on your website:

- Implement the CMP Script Early in the Head Section: Place the CMP script as one of the first elements within the tag of your website. This ensures the CMP initializes before other scripts, including Google tags.

- Configure Consent Mode Default Command: If you’re using Google’s Consent Mode, ensure that the default command (gtag('consent') or equivalent API) is configured to run immediately after the CMP script loads. This will manage consent signals for Google tags based on user preferences.

- Load the TCF Stub (if applicable): For sites operating under the IAB Europe Transparency and Consent Framework (TCF), include the TCF stub script in the tag. This stub facilitates communication between your CMP and Google tags.

- Delay Google Tags Until Consent is Processed: Ensure Google tags (e.g., Google Analytics, Ads, or Tag Manager) are configured to wait for the CMP’s consent signals. This can be achieved by: Setting up Google Tag Manager to trigger only after receiving consent status or Using Google’s tag settings to defer loading until the CMP signals are available.

- Test and Verify Implementation: After implementation, test your setup to confirm that CMP and consent commands/stubs load before any Google tags. Also test Google tags respect user consent preferences and only fire accordingly.

For further assistance, contact us [email protected]