Bridge, then block
Vendors that support it (Google, HubSpot, Adobe, Pardot) self-throttle to cookieless signals under denial. Everything else is hard-blocked until granted. How it works →
Lightning CMP is a privacy-first, edge-hosted Consent Management Platform: a cookie-consent banner and a consent engine that wire your third-party tags to the visitor’s decision. You install one snippet; the correct behaviour per visitor — which regulation applies, which categories are pre-granted, whether a banner even shows — is resolved for you at the edge.
What sets it apart is the “bridge, then block” model. Most CMPs only block a tag until consent, which throws away measurement you’re allowed to keep. Lightning first tries to bridge consent to vendors that support a consent-aware mode, so they keep sending privacy-safe, cookieless signals under denied consent instead of going dark.
Bridge, then block
Vendors that support it (Google, HubSpot, Adobe, Pardot) self-throttle to cookieless signals under denial. Everything else is hard-blocked until granted. How it works →
100/100 Lighthouse
~12 KB gzipped, loaded async, never render-blocking. The banner runs
without costing you a point. Performance →
One call to init
lightning("init", { … }). Only siteId is required, and the license key
usually supplies even that. Config reference →
WCAG 2.1 AAA
Shadow-DOM isolation, full focus trap, live-region announcements, AAA contrast — accessible out of the box. Verifying →
Four consent categories — necessary, preferences, statistics,
marketing — drive every tag on your page. necessary is always on. The other
three are granted or denied by the visitor (or pre-decided by their region’s
law), and the CMP forwards that decision to your vendors live. That’s it — the
rest of these docs is progressive detail on top of that idea.