Banner Not Showing
Symptom
The consent banner does not appear when visiting your site in a fresh incognito window.
Checklist
Before diving into causes, verify:
- You're testing in a private/incognito window (existing consent cookie hides the banner)
- The script tag is present in your page source (
View Source→ search forconsentforge) - Your embed token matches the property in the Dashboard
Cause 1: Script tag not loading
How to check: DevTools → Network → filter by "consentforge" — the script should appear.
Fix: Ensure the script tag is in <head>, not deferred by a tag manager that fires too late. The script must load before consent is needed.
Cause 2: Domain not authorised
How to check: DevTools → Console — look for a ConsentForge warning about unauthorised domain.
Fix: Add your domain to the property's authorised domains: Property → Settings → Domains → Add Domain.
Cause 3: Consent already stored
How to check: DevTools → Application → Cookies — look for cf_consent.
Fix: Delete the cf_consent cookie and reload in incognito.
Cause 4: Banner hidden by CSS
How to check: DevTools → Elements — search for .cf-banner. Check if it has display: none or visibility: hidden applied.
Fix: Remove conflicting CSS from your site's stylesheet. ConsentForge's styles are scoped but high-specificity site CSS can still override them.
Cause 5: adblocker or browser extension
How to check: Test without any browser extensions. Some adblockers block cdn.consentforge.com.
Fix: Allowlist cdn.consentforge.com in your adblocker for testing. Note: some visitors may always see no banner due to adblockers — this is expected and not a compliance risk (adblockers typically block all tracking too).
Cause 6: Property has no published policy
How to check: Dashboard → Property → Policy — check if a policy is published.
Fix: Publish your policy: Policy → Publish Policy.
Still not working?
Contact support at support@consentforge.com with:
- Your property ID
- Your domain URL
- A HAR file from DevTools (Network → Export HAR)