Everything you'd want to know before you install.
A detailed look at how DataFirefly Cookie Consent — GDPR/CNIL & Google Consent Mode v2 for WordPress works, why we built it the way we did, and the thinking behind the features above.
Why Google Consent Mode v2 has become mandatory
Since March 2024, Google no longer accepts conversion signals from European sites that do not implement Consent Mode v2. Without Consent Mode v2 properly configured, your Google Ads conversions disappear from reporting and your audiences no longer build. The 7 required signals must be declared as default before GTM loads, then updated according to user choice. This plugin automatically outputs the gtag consent default block in the head with priority 1, ensuring it runs before any GTM container or Google Analytics 4 tag.
The audit that detects what other plugins ignore
Most consent plugins simply display a banner and store user choices. DataFirefly Cookie Consent goes further: it actually scans your homepage and detects the trackers actually loaded. 23 known trackers are identified (Google Analytics 4, GTM, Meta Pixel, TikTok, LinkedIn, Pinterest, Snapchat, Twitter, Bing UET, Matomo, Microsoft Clarity, Hotjar, Mixpanel, Plausible, HubSpot, Intercom, Crisp, Tawk, YouTube, Vimeo, Stripe and others) plus 11 at-risk WordPress plugins are monitored. You immediately see what is compliant and what is not, with a score from 0 to 100.
A CNIL and Garante compliant audit log
Every consent is logged in a dedicated table with UTC timestamp, persistent anonymous UID, event type (accept_all, reject_all, custom, withdraw), policy and banner version, complete per-category state. The IP is double-protected: SHA-256 hashed with random salt generated at plugin activation (irreversible and CNIL compliant) plus truncated to /24 for IPv4 or /64 for IPv6 for anonymous analysis. CSV export with UTF-8 BOM and semicolon separator for direct opening in French Excel. Pretty JSON export with unicode preserved for integration in your third-party tools.
A modern, accessible, multilingual banner
The v3 banner offers 3 layouts: full-width bar at top or bottom, discrete corner card, centered modal for the strictest sites. Light, dark or auto themes (follows prefers-color-scheme). Reject all button required at first level (CNIL recommendation of 17 September 2020). Per-category customization modal with accessible iOS-style toggles. Animations respectful of prefers-reduced-motion. Full-screen responsive on mobile under 640 pixels. Interface and banner translated into 5 languages: French, English, Spanish, German, Italian.
Designed for developers
Public JavaScript API exposed on window.dfcc with methods open, accept, reject, withdraw, getConsent and hasConsent per category. POST REST endpoint at wp-json/dfcc/v1/consent to log a consent event from your code. Shortcode to open the modal from the footer. WordPress hooks dfcc_before_banner_render, dfcc_after_consent_logged and dfcc_consent_mode_defaults to customize all behaviors. PSR-4 code under the DataFirefly/CookieConsent namespace. Compatible with WPML, Polylang, Cloudflare and WooCommerce HPOS.
There are no reviews yet.