Consent Pro V2: iframe stays blocked although its trackers are categorized as Essential

Consent Pro
1

Webflow site, Site ID 678a89f0194f8914c8a921eb. Consent Pro V2, migrated from V1. The Finsweet Components app was installed in parallel and has since been fully removed, including the leftover code under Site Settings → “Code added by Apps”.

We embed charts from visualize.graphy.app on two pages. All three of the provider’s trackers are categorized as Essential in the Consent Manager, each with the provider set to graphy.app:

  • AWSALBTG
  • AWSALBTGCORS
  • referrer

The embed code in Webflow is a plain iframe with a normal src attribute and no Consent Pro attributes:

html

<iframe src="https://visualize.graphy.app/view/…" loading="lazy" allowfullscreen="true"></iframe>

Problem: After rejecting all cookies, the iframe is still blocked and shows “Iframe is blocked. Accept cookies to load it”.

Inspecting the rendered element shows the runtime script has rewritten it:

html

<iframe fs-consent-processing=""
        fs-consent-src="https://visualize.graphy.app/view/…"
        fs-consent-blob="blob:https://www.pcostudio.com/…"
        src="blob:https://www.pcostudio.com/…">

Two things stand out: there is no fs-consent-categories attribute on the element, and fs-consent-processing remains on it after processing.

What we already tried:

  • Set the provider on all three trackers so they share one provider entry
  • Ran a fresh scan afterwards
  • Searched Global Settings and Scan Settings for an iframe allowlist or a per-domain exception
  • Verified the source embed code contains no Consent Pro attributes

Question: How do we exclude a specific iframe domain from automatic blocking so it loads regardless of the consent decision, given that its trackers are already categorized as Essential?

Context: the charts are on our case studies page. Visitors who reject cookies currently see a placeholder instead of the content, which we would like to avoid.

2

Hey @justin1

A couple of suggestions based on the data you provided

Check the “Load Script Async” in Global Settings

The docs explicitly state to “Never combine auto-blocking with async loading — use the synchronous (non-async) setup for auto-blocking”

If Async is on, try turning it off, copy the updated script from the Installation tab into Webflow Site Settings Custom Code, then republish, retest

Also verify with the debugger

Append ?consent-pro-debugger=true to your site url so it shows the debugger overlay active
Check whether it reports of the graphy.app trackers before consent

Manual fix

The docs document a manual way to set fs-consent-categories="essential"

<iframe
    fs-consent-src="https://visualize.graphy.app/view/…"
    fs-consent-categories="essential"
    loading="lazy"
    allowfullscreen="true"
></iframe>

Elements marked only essential load immediately, without waiting on consent

Could you share your site url so we can diagnose? Thanks