Need to know about conset form

Consent Pro
1

1. Preferred — stop hardcoding the tags. Remove 6sense, Clarity, Meta, LinkedIn, HubSpot embeds from Webflow custom code, fire them
only via GTM (GTM-TQGH824) gated by Consent Mode = granted, and let Consent Pro drive the signal. Hardcoded head scripts are the
reason blocking fails.
2. Or enable Consent Pro’s auto-blocking and categorize every tracker in its dashboard so it rewrites/holds them until opt-in —
then confirm blockedScripts > 0.
3. Either way, on the contact/PHI page, remove Clarity session replay + HubSpot Collected Forms + 6sense entirely rather than
relying on the banner.

2

Hey @digital_old!

Your instinct is right that the consent signal needs to gate the trackers properly — a couple of framing points worth clarifying before you implement, though, because they change the approach slightly.

On the “hardcoded scripts bypass Consent Pro” concern — that’s partially accurate. The real mechanism isn’t that hardcoded head scripts inherently escape blocking, it’s that they escape blocking when they lack the required attributes. Consent Pro needs two things on each script tag:

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

Set type=“fs-consent” and fs-consent-categories to the appropriate value (analytics, marketing, or personalization). Scripts tagged this way get held until consent is granted — regardless of whether they’re hardcoded in Webflow’s custom code. So Option 2 is viable without moving everything to GTM, as long as those attributes are present.

One critical constraint: never combine auto-blocking with async loading. Use the synchronous Consent Pro script setup — no async or defer.

On the GTM path (Option 1), the flow is:

  1. Import the Consent Pro GTM template and create a “Consent Pro Init” tag triggered on Consent Initialization – All Pages
  2. Create a Custom Event trigger named consent-updated
  3. Update all tracker tags (6sense, Clarity, Meta, LinkedIn, HubSpot) to fire on consent-updated
  4. Add consent checks per tag under Advanced Settings → Consent Settings → “Require additional consent for tag to fire”

For link, page view, or form submit triggers, GTM Group Triggers with the AND principle work here.

On verifying blocking — Consent Pro doesn’t expose a blockedScripts > 0 counter. Listen to per-script events instead:

window.FinsweetConsentPro.on('script-blocked', (detail) => {
  console.log('[blocked]', detail.src, detail.categories);
});

On the PHI/contact page (Option 3) — removing Clarity, HubSpot Collected Forms, and 6sense from PHI-adjacent pages entirely is the more conservative call. Consent Pro handles the technical consent layer, but full compliance with healthcare-specific regulations is your responsibility. Please work with a qualified attorney on that piece. :folded_hands:

Could you share your actual staging URL? The HTML in your post looks like a placeholder, so we can’t verify the current implementation from that. :flexed_biceps: