# The ConsentPro application in Webflow isn't working

**URL:** <https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533>\
**Category:** Finsweet Components\
**Created:** [August 28, 2026, 9:09pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533 "2026-08-28T21:09:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![holland.ryser](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/holland.ryser/32/6504_2.png) [@holland.ryser](https://forum.finsweet.com/u/holland.ryser)\
**Post date:** [August 28, 2026, 9:09pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/1 "2026-08-28T21:09:56Z")

</div>

## Description

I can’t complete a scan, my set up says it is incomplete, I also can’t validate my script. Need this fixed ASAP.

## Site URL

**Required:** Please provide a staging/production URL where we can see the issue

- URL: [https://jobnimbus-dev.webflow.io/](https://jobnimbus-dev.webflow.io/)
- Webflow Read-only link: [Your Webflow Read-only link here]

## Steps to Reproduce

1. [First step]
2. [Second step]
3. [Third step]  
…

## Expected Behavior

[What did you expect to happen?]

## Actual Behavior

[What actually happened?]

## Video/Screenshots

**Required:** Please provide a short screen recording showing the issue

- Video link: [Loom/Screen recording URL]
- Screenshots (if applicable): [Upload or link to screenshots]

## Additional Context

- Browser: [e.g., Chrome 120, Safari 17]
- Device: [e.g., Desktop, iPhone 14]

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

---

<div class="post-metadata">

**Author:** ![Support-Finn](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-finn/32/5169_2.png) [@Support-Finn](https://forum.finsweet.com/u/Support-Finn)\
**Post date:** [August 29, 2026, 6:03pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/2 "2026-08-29T18:03:03Z")

</div>

Hey @holland.ryser!

This looks like a **Consent Pro** setup issue — we’ve seen this pattern come up a few times, and there are usually a handful of quick things to check.

A few questions to help narrow it down 🙏

1. Are you publishing to **production** (your live domain) or just staging (the [webflow.io](http://webflow.io) subdomain)?
2. Is the **Consent Pro dashboard open in your browser** at the moment you hit publish? The app sometimes needs to be active to properly detect your setup.
3. Do you have any pages set to **draft** or **password-protected**? Those can block the scan from completing.

While you check those, here are a few steps that have resolved this for others:

- Publish to production with the Consent Pro dashboard open in your browser — this lets the app detect your setup correctly.
- In Webflow, go to Site Settings → SEO and confirm the auto-generated sitemap is enabled. The scanner relies on this to find your accessible pages.
- Go to Project Settings → Custom Code → Head Code and verify the Consent Pro script tag with your `siteid` is present.

Once those are confirmed, try running the scan again from the Consent Pro dashboard and see if it clears up. 💪

Let us know what you find — happy to dig deeper once we know which step might be the sticking point.

---

<div class="post-metadata">

**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/5523_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\
**Post date:** [August 29, 2026, 6:34pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/3 "2026-08-29T18:34:07Z")

</div>

Hey @holland.ryser

To add on to what @Support-Finn suggests

The ConsentPro installation looks correct  
The tracking scripts on the site however need to be wired to work with ConsentPro

First of all, move the two ConsentPro installation `<script>` tags to be the very first scripts in `<head>` ahead of the `Facebook Pixel` and `Intellimize` snippets

Your tracking scripts then need to look something like this

```auto
<script type="fs-consent" fs-consent-categories="analytics" src="https://example.com/analytics.js"></script>

```

The tracking scripts

- Meta/Facebook Pixel

```auto
<script type="fs-consent" fs-consent-categories="marketing">

```

- Google Tag Manager

```auto
<script type="fs-consent" fs-consent-categories="analytics,marketing">

```

- Microsoft Clarity

```auto
<script type="fs-consent" fs-consent-categories="analytics">

```

- Bing UET

```auto
<script type="fs-consent" fs-consent-categories="marketing">

```

- Ahrefs Analytics

```auto
<script type="fs-consent" fs-consent-categories="analytics" src="https://analytics.ahrefs.com/analytics.js" data-key="YuVYPUuJ0s/QEneoVk3pGA" async></script>

```

- G2 Attribution Tracking

```auto
<script type="fs-consent" fs-consent-categories="marketing">

```

Republish then re-run the scan, it should now detect these scripts and let validation pass

Here are some helpful links in the docs

> **[Async Script Loading - Consent Pro V2 | Consent Pro Docs](https://docs.consentpro.com/v2/async-script-loading)**
>
> Configure async script loading with manual blocking in Consent Pro V2 to improve Core Web Vitals without compromising GDPR compliance. Covers enabling async, manually blocking scripts, iframes, and images, the callback queue pattern, and best...

> **[HTML Attributes Reference - Consent Pro Documentation | Consent Pro Docs](https://docs.consentpro.com/v1/attributes/)**
>
> Complete HTML attributes reference for Consent Pro cookie consent banners. Learn how to customize your GDPR & CCPA compliant consent forms using Webflow Designer with fs-consent-element attributes.

---

<div class="post-metadata">

**Author:** ![holland.ryser](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/holland.ryser/32/6504_2.png) [@holland.ryser](https://forum.finsweet.com/u/holland.ryser)\
**Post date:** [August 31, 2026, 4:45pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/4 "2026-08-31T16:45:40Z")

</div>

Yes, I can confirm that this is what I have been doing, but the dashboard still isn’t working. We currently have approximately 30% of our pages showing that they do not have cookie consent.

We do have some draft pages, but none of them are password-protected. We have had draft pages in the past, and everything worked fine, so I don’t believe that should be causing this issue, especially since every website is going to have pages that are in draft.

I have sent multiple emails to Support regarding this issue and have also attached a message from our engineer with additional details. I would appreciate it if you could review the information there as this issue seems to go beyond our set up.

Webflow indicated that the issue is likely related to the ASN blocking feature and mentioned that they have worked with your team to determine a workaround. Could you please look into this and let me know what the next steps are?

Also, the two ConsentPro scripts are the first 2 tags in the code already. I am also trying to run a scan on the dashboard and it is stuck in a loop and won’t finish. We had another company do an audit and they found that 30% of our pages aren’t showing any form of Cookie consent and that a ton of tags aren’t actually firing the way they should and are sometimes firing before consent is given in regions where that can’t be the case. This needs to be resolved ASAP.

---

<div class="post-metadata">

**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/5523_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\
**Post date:** [September 1, 2026, 1:08pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/5 "2026-09-01T13:08:12Z")

</div>

Hey @holland.ryser

Sorry for this, the good news is that the dev team is already on this case & an update should be ready soon

I also updated the thread on Crisp on the same

Let me get back to you with updates as soon as the dev team gives the go-ahead

Thanks for the patience

---

<div class="post-metadata">

**Author:** ![holland.ryser](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/holland.ryser/32/6504_2.png) [@holland.ryser](https://forum.finsweet.com/u/holland.ryser)\
**Post date:** [September 3, 2026, 5:32pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/6 "2026-09-03T17:32:26Z")

</div>

I sent a response yesterday, and the day before. What you sent was already tried by our team on Friday and we are still having issues.

We really need to get a response on this as soon as possible. At this point, we are seriously considering switching to a different software solution.

This does not appear to be a setup issue. Based on what we’re seeing, it appears to be a compatibility issue between ConsentPro and our reverse proxy configuration. Using a reverse proxy is not an unusual setup, and plenty of companies operate this way, so we need to understand why this configuration is not working with ConsentPro and, more importantly, how we can resolve it.

We need a clear response and a viable solution ASAP. Please escalate this issue.

---

<div class="post-metadata">

**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/5523_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\
**Post date:** [September 3, 2026, 6:05pm UTC](https://forum.finsweet.com/t/the-consentpro-application-in-webflow-isnt-working/7533/7 "2026-09-03T18:05:26Z")

</div>

Hey Holland, could you please checkout the solution on Crisp

Pasting it here again 🙏

> Hello Holland,
> 
> An issue with the User-Agent that your team allowed, you’ve used the following name,
> 
> ```auto
> ConsentProBot/1.0
> 
> ```
> 
> The correct User-Agent should be simply
> 
> ```auto
> ConsentProScanner
> 
> ```
> 
> Another thing, we have pushed an update that supports reverse-proxied sites.
> 
> Inside Consent Pro’s configurator, you can access the domain editor, and you should now see three fields available: the first one will have the staging domain, the second will have the Webflow custom domain and the third will allow for a custom domain.
> 
> Here you’ll be able to define your public URL: [https://www.jobnimbus.com/](https://www.jobnimbus.com/),
> 
> Once you’ve added the domain, a fresh scan will be triggered. After this, you should be able to see the information from this domain land in the Consent Logs tab.

> Also, it’s important to note that the User Agent is a browser-shaped string like:
> 
> ```auto
> Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 ConsentProScanner
> 
> ```
> 
> The agent string may change, but it will always contain ConsentProScanner. So the WAF rule should look for ConsentProScanner in the string instead of trying to match it.
> 
> Can you please try this and let us know if it resolves the issue?