Description
Cookie consent elements work fine on chrome and other browsers, but on Dia browser, the banner, preference center, and persistent cookie icon just all appear and are unable to interact with them
Site URL
Required: Please provide a staging/production URL where we can see the issue
Steps to Reproduce
- Load site in Dia Browser
Expected Behavior
Normal cookie interaction
Actual Behavior
Seems like its not connecting to anything where the elements become interactive
NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.
Hey @alexander1!
The HTML structure looks correct — your fs-consent-element attributes are all properly configured. The issue where all elements appear simultaneously and are unresponsive is the classic symptom of the Consent Pro script not initializing properly.
The “No trackers detected for this category” and “No providers detected for this category” messages in your screenshot confirm the script hasn’t completed initialization, which is why nothing is interactive.
Since this is happening specifically in Dia browser, let’s run through a few diagnostic steps to pinpoint what’s going on:
- Confirm the Consent Pro script tag is in Webflow Project Settings → Custom Code → Head section. It should look like:
<script src="https://api.consentpro.com/v2/cdn/runtime/[your-site-id].js" type="text/javascript" finsweet="consentpro"></script>
If you can share the exact snippet you have there, that would help a lot.
-
Open DevTools in Dia (right-click → Inspect → Console tab), reload the page, and look for any red error messages. Screenshot anything you see.
-
In the same DevTools, go to the Network tab, reload, and filter by “consent” or “finsweet” — do those requests show as successful (200) or blocked/failed?
-
Test the same page in Chrome or Safari to see if the issue is specific to Dia or affecting all browsers.
To be honest, Dia is a relatively new browser and isn’t in our officially tested browser list, so this is a bit of a collaborative investigation 
Once you share those findings, we can figure out whether it’s a script loading issue, Dia’s privacy features blocking something, or something else entirely.
Hey @alexander1
Building on to what @Support-Finn suggested, the Dia browser has quite aggressive content-blocking features that will prevent GTM, Consent Pro and the likes from loading
Considering it works good on Google Chrome & other browsers, we recommend to temporarily disable content blocking in Dia to confirm
Also please note that this is a built-in browser privacy feature so it does not necessarily indicate a problem with the Consent Pro configuration
