Consent Pro V2 - Use alongside "Google site tools for Webflow" plugin

Consent Pro
1

We are exploring the new Consent Pro V2 plugin and have a question regarding the install when using Google Tag Manager. In your documentation you state that we should not use any <noscript> tags when trying to be compliant with GDPR laws.

How can we achieve this when using the trending Webflow app “Google site tools for Webflow“? It seems like the app installs the scripts for us but does not give us a direct option to block the <noscript> tag. Is Consent Pro V2 still able to block that or should we step back from using this app and install Google Tag Manager the “old“ way?

2

Hey @vierless_julian :flexed_biceps:

You’re absolutely right to be thinking about this. The <noscript> tag issue with third-party Webflow apps is an important compliance consideration.

Here’s the core problem: The <noscript> tag from GTM runs even when JavaScript is disabled, which means it can potentially collect user data without consent — this undermines the purpose of Consent Pro and GDPR compliance. That’s why Consent Pro V2 documentation specifically states that the noscript tag must be removed for proper compliance.

The tricky part with the “Google Site Tools for Webflow” app is that it likely injects the noscript tag automatically (as Webflow apps often do), which means you may not be able to simply remove just the noscript portion from Site Settings > Custom Code like you would with a manual GTM installation.

Before we recommend a path forward, could you let us know what Google services you’re currently using through the “Google Site Tools for Webflow” app? (e.g., just GTM, or also Analytics, Ads, Search Console, etc.) This will help determine the best approach for your setup :folded_hands:

Our recommended approach:

Remove the “Google Site Tools for Webflow” app and implement GTM manually following the Consent Pro V2 GTM setup guide. This gives you full control over which GTM tags you install (without the noscript) and is the documented setup path for Consent Pro V2.

The manual setup includes:

  1. Adding only the <script> portion of GTM to your Custom Code (omitting the noscript)
  2. Importing the Consent Pro GTM template
  3. Configuring consent triggers so tags only fire after user consent

Alternative option (if removing the app isn’t viable):

Check if the “Google Site Tools for Webflow” app has a setting to disable the noscript tag injection. Some apps offer granular control — worth checking before making bigger changes.

Bottom line: Consent Pro V2 can’t block noscript tags because they execute independently of JavaScript. Your best bet is the manual GTM setup, which is well-documented and gives you complete compliance control.

Happy to walk you through the manual setup steps if you decide to go that route!

3

Thank you very much for the detailed response!

We connected all the Google options they offered trough the app. But we will move to manual installation instead now.