# Is Finsweet cookie plugin for Webflow blocking my Lead Forensics tracking?

**URL:** <https://forum.finsweet.com/t/is-finsweet-cookie-plugin-for-webflow-blocking-my-lead-forensics-tracking/6931>\
**Category:** Finsweet Components\
**Created:** [February 25, 2026, 2:21pm UTC](https://forum.finsweet.com/t/is-finsweet-cookie-plugin-for-webflow-blocking-my-lead-forensics-tracking/6931 "2026-02-25T14:21:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![os1](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/os1/32/3447_2.png) [@os1](https://forum.finsweet.com/u/os1)\
**Post date:** [February 25, 2026, 2:21pm UTC](https://forum.finsweet.com/t/is-finsweet-cookie-plugin-for-webflow-blocking-my-lead-forensics-tracking/6931/1 "2026-02-25T14:21:22Z")

</div>

## Description

The tracking visitors script for Lead Forensics has stopped working when switching to Webflow.

## Site URL

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

- URL: [https://invoiceapprovals.com.au/](https://invoiceapprovals.com.au/)
- Webflow Read-only link: [Your Webflow Read-only link here]

## Steps to Reproduce

## In DevTools → **Network** , do you see `802353.js` load on refresh? (Yes/No)

1. If **Yes** , click it and tell me:
  - **Status** (200 / blocked / 404 / other)

  - **Initiator** (this is key: it tells us what injected it)

2. If **No** , then LF is simply not running on that page at all.  
…

## Expected Behavior

Find the script ID number listed in either Page Source code or in the Elements inspector.

## Actual Behavior

No code or reference seen.

---

<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:** [February 25, 2026, 4:23pm UTC](https://forum.finsweet.com/t/is-finsweet-cookie-plugin-for-webflow-blocking-my-lead-forensics-tracking/6931/2 "2026-02-25T16:23:40Z")

</div>

Hey @os1 💪

This is actually related to **Consent Pro** (the cookie/consent management tool) rather than Components.

Looking at your HTML, the issue is that your Lead Forensics tracking script doesn’t have any consent management attributes on it:

```html
<script type="text/javascript" src="https://consortiumtradeagency.com/js/812592.js"></script>

```

Because this script tag isn’t tagged with a consent category, Consent Pro doesn’t know how to manage it — so it’s likely being blocked by default or not loading because the consent system can’t categorize it.

**What typically needs to happen:**

Third-party tracking scripts like Lead Forensics need to be tagged with the appropriate consent category so that Consent Pro knows when to allow them to run based on user consent. Since Lead Forensics is a visitor tracking tool, it would typically fall under the **analytics** or **marketing** consent category (depending on how your privacy policy defines it).

If adding consent attributes to the script tag doesn’t work (sometimes external scripts load sub-resources that bypass attribute-based blocking), there’s also a JavaScript API approach using Consent Pro’s API to dynamically load the script only after consent is given. But let’s try the simpler attribute approach first 🙏