Transfering Site & Consent Pro

Finsweet Components
1

Description

Hello! I have a question. I have setup Consent Pro on my client’s Webflow project. I have just transfered the project now, and on Monday, we are adding Analytics and Google Tag Manager scripts. I want to go back into the Consent Pro app and make sure that these codes are only activated upon the Analytics checkbox being active, or if they accept all.

It doesn’t seem to be the case, that I can go in and easily do that. I seem to have to re-configure the entire component and re-style everything, if I just want to convert some header codes to work with consent options.

Site URL

Required:

Steps to Reproduce

  1. Open Consent Pro App
  2. Try and see where all Site Settings codes are, and where Consent Pro converts them.

Expected Behavior

That I can just re-open the Consent Pro app and make edits to my current component, and that the setting is easily carried through. Especially with custom code being added for tracking, and then going back into the app, and easily doing the conversion for the code.

Actual Behavior

I have to open the Consent Pro app and re-configure my entire Cookie popup. Then I have to restyle all of it, every time I need to edit a setting.

Video/Screenshots

Required: Please provide a short screen recording showing the issue

image
image1745×1062 105 KB

You see, I have Cookie Consent on my site, but when I open the Consent Pro app (I am logged in there), it’s not finding it.

Additional Context

  • Browser: Chrome
  • Device: Desktop

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

2

Hey @andrewe97!

This commonly happens after transferring projects between Webflow accounts - the Consent Pro app sometimes loses track of component instances even though they’re still functioning on your site. We’ve helped several users with this exact issue! :flexed_biceps:

Here’s how to fix it:

Step 1: Complete App Reconnection

  1. Open your Webflow Designer
  2. Remove the Consent Pro app completely from your Apps panel
  3. Publish your site (with the app removed)
  4. Hard refresh your browser (Ctrl + Shift + R or Cmd + Shift + R)
  5. Re-install the Consent Pro app
  6. Publish your site again

Step 2: Force Re-authentication
When you launch the app again, it should:

  • Ask you to publish while the app is open (this is normal!)
  • Scan your site and detect the existing component
  • Allow you to modify Analytics/GTM script configuration without rebuilding

For Your Analytics/GTM Scripts:
Once the app recognizes your component, you can configure your tracking scripts by:

  1. Adding fs-consent-categories="analytics" to your GTM/Analytics script tags
  2. Using type="fs-consent" on the script tags
  3. Setting up consent-based triggers in GTM if needed

If the reconnection doesn’t work, you can manually configure scripts without the app by adding the proper consent attributes directly to your script tags in Site Settings → Custom Code.

The good news is your existing styling and component structure will remain intact - this is purely an app connection issue, not a component problem! :thinking:

Let me know how it goes!

3

Thank you so much Finn! I will bookmark this thread for later! :slight_smile:

Just to make sure, I remove the Consent Pro app from Site Settings, or can that be done in the Apps panel as well?

And, if the client logs in rather than me, will it still recognise the existing Cookie Consent popup?

Lastly, if you have the time, as I know it’s Friday, could you paste me an example of the scripts with these tags? Especially for Google Analytics and Google Tag Manager.

Thank you so much!
Andrew

4

Hi @andrewe97

You can remove the Consent Pro from the Apps Panel
& yes if the client logs in, they will still recognise the Consent Pro that you will have setup

Had you already added in the Google Analytics and Google Tag Manager?

Here are the consent pro docs

image
image1908×882 120 KB

5

An sample Google Analytics snippet looks like so

<script src="https://www.googletagmanager.com/gtag/js?id=G-XXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXX');
</script>

A sample Google Tag Manager snippet looks like so

<script>
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;
j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;
f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXX');
</script>
6

Hi Finn,

Sadly this hard restart isn’t working. I uninstalled the app, published the site, refreshed with Ctrl + Shift + R and reinstalled the app. It is still not recognising the current Cookie Consent on the site. Just thought I’d let you know, so that you and your team can check it out.

Thank you

7

Hi andrewe97!

You do not need to recreate or restyle your Consent Pro banner to attach Google Analytics or GTM to consent categories. Consent Pro separates UI (banner design) from script control logic.

Here’s how it actually works and how to fix your workflow:

Open Consent Pro, Go to Scripts / Integrations tab. Inside the app you should see:
Scripts, Integrations, & Categories

This is where tracking logic lives, not inside the visual builder.

Add Google Analytics / GTM Using Script Manager. Instead of placing GA/GTM in Webflow Site Settings:

Preferred method:
Consent Pro App → Scripts → Add Script

Example:

Google Analytics
Name: Google Analytics
Category: Analytics
Load type: After consent
Paste GA script here

Google Tag Manager
Name: GTM
Category: Analytics
Load type: After consent
Paste GTM script here

Consent Pro will automatically:
Block it by default
Load it ONLY when Analytics is accepted
Load it when “Accept all” is clicked

Remove Existing Tracking From Webflow Settings
If you already added scripts here:
Webflow → Site Settings → Custom Code

You should, remove GA/GTM from Header/Footer, let Consent Pro manage them
Otherwise, scripts will fire BEFORE consent & Consent Pro cannot intercept them

Why It Feels Like It Resets
This happens when you click Create again
That button creates a New component instance, Resets UI styles, Replaces attributes

You should:
Only press Create once and then after that, edit Scripts + Categories only
Your banner already exists in the Navigator: Cookie Consent. Do NOT recreate it.

Verify Categories Are Enabled
Open, Consent Pro → Categories

Make sure:
Analytics is Enabled
Marketing is Enabled (if using ads)
Necessary is Locked

These categories control which scripts can fire.
Test Correct Behavior
After publishing, open site in incognito, reject all, check DevTools then Network tab

You should see, No GA requests & No GTM fired
Then, accept Analytics, refresh

Now GA & GTM loads

Note that because you transferred the site, sometimes Consent Pro loses script mapping due to:
Workspace ownership change
Domain change
Duplicate project ID

If scripts tab looks empty:
Click on Resync Project (top right menu), this reloads existing config without touching UI.

So essentially, you don’t need to rebuild popup, restyle banner or recreate component
You only need to, add scripts via Consent Pro Scripts tab, assign category as Analytics and then remove scripts from Webflow Site Settings