Issues with leftover Google Font from Consentbit and setting up Webflow scripts in Finsweet Consent Pro

Design help Custom code
1

Hi, I am working on making my website GDPR-compliant. Initially, I installed the Cookie Consent Tool from Consentbit, but it did not work as expected and seemed quite buggy. Therefore, I removed it and switched to Cookie Consent Pro from Finsweet, which appears to be much more stable.

In the Consentbit tool, I had to select a font for the cookie banner and chose Montserrat. This font was being loaded through Google Fonts, which is not GDPR-compliant. However, even after uninstalling the app, the font is still being loaded and appears in the DOM.

image

I am quite sure this is a leftover from Consentbit, since Montserrat was only used in the cookie banner. I cannot find it anywhere else — neither in custom code blocks nor in the page settings under custom code.

Question 1:
How can I completely remove this leftover font or script from Consentbit?

Question 2:
How can I properly set up scripts that are managed by Webflow in Finsweet Consent Pro?
For example, I am using the Facebook Pixel added through Webflow’s page settings, so I do not have direct access to the <script> tag. Consent Pro requires adding parameters to that tag. How can I do this when the script is added via Webflow settings?

The same applies to Webflow Analytics, which I also have installed.

Thank you in advance for your help.

Here is my site Read-Only: Webflow - ROOM BOOM

2 Likes
2

This is what I mean by the Facebook Pixel. I’m getting the following message in Consent Pro:

image
image723×271 31.4 KB

I don’t have access to this script, since the pixel is integrated through the page settings.

A possible workaround would be to copy the mentioned script, edit it, and paste it into the custom code section. After that, I could disable the implementation in the page settings.

But is that really the correct approach? I hope not.

2 Likes
3

Hello @Mirko_H, so somebody with access to the site settings has to update the code from Consent Pro, the Facebook Pixel script has to be on the site settings custom code section because it is used on all the pages, right? and so in order to Consent Pro to work properly you have to update the FP script with the new parameters and replace the original script with what Consent Pro gives you. You can reference this tutorial https://www.youtube.com/watch?v=G6WITcW9B_4.

As for the font from ConsentBit, there is probably a class that is using the font, so check all the classes that were used with the ConsentBit and delete them from the styles panel.

Screenshot 2025-11-12 at 12.45.20 PM
Screenshot 2025-11-12 at 12.45.20 PM572×1108 94.2 KB

I hope this helps.

2 Likes
4

Hi @pablo_Cortes, thank you very much for trying to help me out with this.
Regarding the pixel, I definetly can use the custom code section in the site settings to get the pixel running. I hoped, that I don’t need to use this. Because currently I am using Site Settings > Apps & Integration > Meta Pixel. Just pasted the Pixel ID there but now I don’t have any chance to edit the script, to add the parameters that Consent Pro needs (or do I?). It seems there is no different solutions, so I will do what you said and paste the script inside the custom code section. It will work but feels like a workaround.

Regarding Consentbit and Google fonts, I have now deleted all the classes, but Google font is still loaded. I don’t think it is loaded through css via a class, because the following is injected into the DOM (I can’t find what injects this):

<link href="https://fonts.googleapis.com" rel="preconnect"/>

<link href="https://fonts.gstatic.com" rel="preconnect" crossorigin="anonymous"/>

<script src="https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js" type="text/javascript"></script>

<script type="text/javascript">WebFont.load({ google: { families: ["Montserrat:100,100italic,200,200italic,300,300italic,400,400italic,500,500italic,600,600italic,700,700italic,800,800italic,900,900italic"] }});</script>

I’ve removed the app, deleted all related classes, and checked every code embed and the custom code section, but I still can’t find where this is coming from. It almost seems like the app has injected code into parts of Webflow that I can’t access — or maybe I’m just overlooking something.

Do you have any idea how I could remove this? It’s really puzzling.

1 Like
5

You have two classes that reference Montserrat as a font. You need to remove those or modify them so that Montserrat and the loading scripts are not loaded. Look for .consent-close and .close-consent.

2 Likes
6

Hi @webdev thanks for your reply!
I saw that the classes .consent-close and .close-consent use font-family: Montserrat, but that’s not what’s causing the Google Fonts request. Those classes only reference the font, they don’t actually load it.

Just to be sure, I’ve removed both classes — but the font is still being loaded from Google Fonts. So the issue must be somewhere else in the project where Montserrat (or the loading script) is included.

Do you have an idea where else Webflow might be adding the Google Fonts link automatically?

1 Like
7

Hello @Mirko_H, did you find the class that was loading the font? because I just checked your published site and Google Fonts is not loading anymore.

2 Likes
8

Here is Webflow reference you might want to review.

https://help.webflow.com/hc/en-us/articles/33961364593043-Add-Google-Fonts#how-to-find-google-fonts

2 Likes
9

Hi @Pablo_Cortes no, I didn’t find it. But indeed it looks like the Google Font isn’t being loaded anymore. I have no idea why. I checked the website right after your comment, and it was gone. Maybe it was a caching issue?

Thank you, but I’ve never used the page settings to add Google Fonts to my website and even after deleting the two classes you mentioned, the font was still there. Maybe it was the server cache? But that doesn’t really make sense to me, since it should be cleared after every publish. Browser caching is disabled on my end as well, so that doesn’t fit either. I’m quite sure Consentbit injected it into the DOM, since I only used Montserrat in the cookie consent banner.

However, I can’t explain why it’s disappeared now. Anyways, everything is working again, so the issue is resolved.
Thank you both for your help—I really appreciate it.

2 Likes