Cookie consent banner for your public sites

Feature

Week of July 9, 2026

If your community has Google Analytics, a Meta Pixel, or custom tracking code configured, visitors to your community site, embedded site, and advocate site now see a cookie consent banner — and those trackers only load after the visitor accepts. Communities with no trackers configured see no banner at all.

Per-category choices — Visitors can accept or decline Analytics (Google Analytics) and Marketing (Meta Pixel and custom tracking code) independently. A “Cookie Preferences” footer link lets them change their mind later.
Tracking vs. essential custom code — The custom head/body code fields under Settings → Analytics are now consent-gated tracking slots. New “Essential” head/body code fields load on every page view without consent — use them for non-tracking needs like fonts or widgets, never for tracking scripts.
Why this matters — Privacy laws like the California Invasion of Privacy Act increasingly treat pre-consent tracking as a liability. This change moves your sites to a consent-first posture with no action needed from you.

No admin action required. Existing Google Analytics and Meta Pixel settings keep working — they simply wait for visitor consent before loading.

Related: Analytics & Tracking