I am using Finsweet Consent Pro on a Webflow project and need to implement Geolocation-based visibility.
Currently, the consent banner is displaying globally to all users on their first session.
However, in certain countries, a cookie consent banner is not a legal requirement. Showing the banner to these users creates unnecessary friction and negatively impacts our conversion rates. I am looking for a way to exclude specific countries from seeing the banner while keeping it active for GDPR-compliant zones.
i have the
Expected Behavior
The banner should only trigger for users browsing from regions where cookie consent is legally mandated (e.g., EU/GDPR). Users from excluded countries (i have set the excluded countries in google tag manager - with granted status for all cookies basically “opt out”.) should be able to browse the site without the banner appearing.
Actual Behavior
The banner is currently “hardcoded” to appear for every single new visitor, even if this country is listed on google tag manager, it seems that the global banner kicks in - except for the EU countries & UK.
Note: I’m using the Custom GTM Loader logic alongside Consent Pro. The goal is to ensure the launchGTM function triggers automatically for exempted regions/countries without requiring a manual click on the banner.
My goal is to comply with legal requirements for each country/region, not to enforce stricter measures than necessary.
Hey @bar.m.hai!
Showing the banner only where it’s legally required is the right approach — here’s what to check to get the region-based visibility working correctly.
The core issue is that Consent Pro and GTM must be configured in sync. Excluding countries only on the GTM side doesn’t suppress the Consent Pro banner itself — Consent Pro has its own region settings per banner in the dashboard, and those need to be configured separately.
Here’s what to verify:
-
Go to the Banners section in Consent Pro and check the Regions column for each banner. Your Opt In Banner should have specific regions assigned (EU, UK, EEA, etc.). For your Informational Banner — if that field is empty or set globally, that would explain why it’s showing to everyone. Can you share a screenshot of the Regions column for both banners? 
-
In your Consent Pro dashboard, go to Banners and click the copy button next to the Regions column. Paste those exact values into the Regions field in your GTM “Consent Pro Init” tag under Region-Specific Consent Settings. If the values don’t match between the two, GTM’s consent defaults won’t align with what Consent Pro expects.
-
Double-check your GTM consent defaults per banner type:
- Opt In banner → all fields set to Denied
- Informational banner → all fields set to Granted
-
For the launchGTM function in excluded regions — as long as your region-specific consent defaults are set to Granted for those countries, the “Consent Initialization - All Pages” trigger on your Consent Pro Init tag should fire GTM automatically without any banner interaction needed.
Once you confirm what regions are assigned to your Informational Banner, we can pin down exactly where things are off. If everything looks right on both sides and the issue persists, we’ll loop in @Support-Luis or @Support-Pedro to dig into your specific setup.
Thanks for the response, but I think we are missing each other on the core UX requirement here.**
Feature Gap: Consent Pro lacks a “No Banner” state for Geolocation Compliance**
The suggestion to use an Informational Banner for excluded regions is not a solution - it’s a conversion killer. In countries where no cookie law exists, showing any UI element (even “Informational”) adds unnecessary friction, clutters the UI, and negatively impacts our conversion rates.
By writing “Showing the banner only where it’s legally required is the right approach” you contradict yourself because there is no option to hide the banner in your dashboard.
only a selection of: Opt in/Opt out/Informational/Do not sell
The Problem: Your current dashboard requires every region to be mapped to a banner type (Opt-In, Opt-Out, Do not sell or Informational). There is no option for “No Banner / UI Suppressed” for specific regions/countries.
The Technical Contradiction:
-
I want to comply with GDPR/UK-GDPR/CCPA by showing the correct banner in those regions.
-
In “Rest of World” regions or specific countries where the law doesn’t require a banner, I want the launchGTM function to trigger automatically with granted status, but with zero UI footprint.
-
Currently, if I don’t assign a region to a banner, it often defaults to the “Global” banner. If I do assign it to “Informational,” the user is still forced to see/dismiss a notice they don’t legally need to see.
The Question for Support/Dev: How can we configure Consent Pro to completely suppress the banner UI for specific geolocations while still allowing the script to initialize and fire GTM tags as “Granted”?
If the dashboard doesn’t support a “None” option for regions, is there a specific attribute or script override we can use (e.g., fs-consent-suppress="true") that respects the GTM Geolocation settings without rendering the Finsweet component?
Showing a banner where it isn’t required is not “the right approach”- it’s a bad user experience. I need a way to turn the UI OFF for specific countries.
Can @Support-Luis or @Support-Pedro weigh in on how to achieve a “Zero-Banner” state for non-regulated regions?
Thanks.
Chiming in on this. Trying to show:
- Banner only on EU + UK regions.
- No banner outside those regions.
For GTM settings: Denied consent & opt-in for EU regions, non-EU regions by default granted.
Actual situation:
- Banner shows on all regions.
Can someone chime in (and possibly improve docs long-term)? The situation with multiple regions + tagmanager settings for multiple regions (especially with default/global granted) is not fully clear imo.
Thanks,
Florian
PS: Also setting the 1 banner (only showing UK + EU) to one page (e.g. only show on “Thank you page”) as a test, still shows it globally on all pages.
Edit: Region-specific settings seem fine. Likely issue is with improper deletion of previous global instance.
