Bug: Opt-out banner wasn't properly deleted

[florian]

Description

In short: Opt-in banner doesn’t show correctly because previously created global opt-out banner doesn’t seem properly deleted in the database.

1. Created global opt-out banner.
2. Requirement changed: Needed region-specific opt-in banner.
3. Signed up for Premium plan.
4. Deleted previously created global opt-out banner in App.
5. Created region-specific opt-in banner.
6. Region-specific opt-in banner doesn’t show, but global opt-out banner still does?

Code pasted in Chrome Dev Console (see bold text):

Note how region-specific detection worked, but instances are wrong:

console.log(“Detected region:”, window.fs_consent_pro_detected_region);
console.log(“Is EU:”, window.fs_consent_pro_detected_region_is_eu);
console.log(“License:”, window.fs_consent_pro_license);
console.log(“Config instances:”, window.fs_consent_pro_config?.instances);
console.log(“Active instance:”, window.FinsweetConsentPro?.instanceConfig);

console.log(“URL override region:”, new URLSearchParams(location.search).get(“consent-pro-region”));
console.log(“URL override mode:”, new URLSearchParams(location.search).get(“consent-pro-mode”));

console.log(
“ConsentPro scripts:”,
Array.from(document.querySelectorAll(“script”))
.map(s => s.src || s.outerHTML.slice(0, 120))
.filter(src =>
src.includes(“consent”) ||
src.includes(“finsweet”) ||
src.includes(“fs-consent”)
)
);
VM1284:1 Detected region: PY
VM1284:2 Is EU: false
VM1284:3 License: premium
VM1284:4 Config instances: {opt-out: {…}}
VM1284:5 Active instance: {mode: ‘opt-out’, bannerType: ‘opt-out’, regions: ‘Global’, pages: Array(1), categories: {…}, …}animation: {duration: 300, easing: ‘ease’, animation: ‘fade’}bannerType: "opt-out"categories: {essential: {…}, analytics: {…}, marketing: {…}, personalization: {…}}disableScroll: falsedisableScrollBehavior: "banner-or-preferences"language: "en"metadata: {instance: ‘opt-out’, name: ‘Consent Pro’, lastupdate: ‘2026-05-13T00:11:08.469Z’, createdAt: ‘2026-05-13T00:11:08.469Z’}mode: "opt-out"pages: [‘*’]regions: "Global"resetInteractions: falseshowTrackers: truesource: "/features/integration"useCustomToggleButton: true[[Prototype]]: Object
VM1284:7 URL override region: null
VM1284:8 URL override mode: null

Actual app settings (only opt-in active):

Site URL

• URL: starbridge.webflow.io
• Site ID: 68a834f29776727eae1bc0f6

[Support-Finn]

Hey @florian!

Your Webflow implementation is actually correct — the fs-consent-instance="opt-in" attributes are properly set on your banner and preferences elements. The issue is coming from the app/backend configuration, not your HTML.

Here’s what the diagnostics are telling us: your region detection is working fine (Paraguay, non-EU) and your license shows premium. But window.fs_consent_pro_config.instances is still returning {opt-out: {...}} — that’s being fetched from the Consent Pro backend, not your Webflow HTML. And your dashboard is showing “Your setup is not finished. Please check all pending actions.”

Until setup is fully completed on the app side, the backend is likely still serving the old opt-out configuration.

Here’s what to try:

1. Open the Consent Pro app in Webflow Designer
2. Go to the Actions tab and complete every item listed there — that’s where pending configuration steps live
3. Check the Install tab to make sure all setup steps are marked as done
4. The goal is to reach the “You are all set” confirmation — that’s the signal your config has been fully applied
5. Once you see that, republish your site
6. Test in an incognito window and run your console checks again to see if config.instances now reflects opt-in

One thing worth noting — your opt-out instance metadata in the console shows it was recently updated, even though you deleted it from the Banners view. If completing the pending actions doesn’t update the config, it’s possible the deletion didn’t fully propagate on the backend, which would need our team to look at directly.

Let us know what you find after working through those steps. If the opt-out config is still showing up after that, we’ll get the team to dig into the backend config for your site.

[florian]

Hi there, thanks for your help!

I’ve completed all the steps, console logs are the same unfortunately. My hypothesis is still that deletion didn’t fully propagate, because where the “Global opt-out” banner is located (features/integration) isn’t the same as where the region-specific opt-in banner (/cookie-policy) is now located?

Also see “lastUpdated” item in “opt-out” banner metadata object.

Thanks again,
Florian

[florian]

Can someone please help here or give an update?

@Support-Finn

[florian]

Bumping this. Would someone mind looking into this from the support/dev team?