vgdevsolutions

<p><strong>VGDev Cookie Banner for Consent Mode v2</strong> is a lightweight, self-hosted GDPR cookie consent solution that integrates natively with Google Consent Mode v2, Google Tag Manager (GTM) and Google Analytics 4 (GA4).</p>
<p>All consent signals start as <code>denied</code> and are updated in real time based on the visitor’s choices — fully compliant with Google’s requirements for EU markets.</p>
<h4>Key Features</h4>
<ul>
<li>✅ <strong>Google Consent Mode v2</strong> — all 7 consent signals managed automatically</li>
<li>✅ <strong>Google Tag Manager (GTM)</strong> — head snippet + body noscript injected automatically</li>
<li>✅ <strong>Google Analytics 4 (GA4)</strong> — standalone gtag.js support (when GTM is not used)</li>
<li>✅ <strong>GDPR Compliant</strong> — consent defaults to denied before any tracking occurs</li>
<li>✅ <strong>Multilingual Privacy Policy</strong> — set a different privacy policy URL per language</li>
<li>✅ <strong>29 built-in languages</strong> — auto-detected via WPML, Polylang or WordPress locale</li>
<li>✅ <strong>Performance Mode</strong> — lazy loads the banner after user interaction (boosts PageSpeed score)</li>
<li>✅ <strong>Force Consent</strong> — block the page until the user makes a choice</li>
<li>✅ <strong>Fully customizable</strong> — colors, layout, position, floating button, and more</li>
<li>✅ <strong>Self-hosted</strong> — no external consent management platform needed</li>
<li>✅ <strong>Lightweight</strong> — no jQuery dependency for the front-end script</li>
</ul>
<h4>Google Consent Mode v2 Signals</h4>
<p>The plugin manages all required consent signals:</p>
<ul>
<li><code>ad_storage</code></li>
<li><code>ad_user_data</code></li>
<li><code>ad_personalization</code></li>
<li><code>analytics_storage</code></li>
<li><code>functionality_storage</code></li>
<li><code>personalization_storage</code></li>
<li><code>security_storage</code></li>
</ul>
<h4>Consent Categories</h4>
<ul>
<li><strong>Necessary</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>security_storage</code></li>
<li><strong>Functionality</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>functionality_storage</code>, <code>personalization_storage</code>, <code>security_storage</code></li>
<li><strong>Analytics</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>analytics_storage</code>, <code>security_storage</code></li>
<li><strong>Marketing</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>ad_storage</code>, <code>ad_user_data</code>, <code>ad_personalization</code>, <code>personalization_storage</code></li>
</ul>
<h4>Multilingual Support</h4>
<p>Works out of the box with WPML, Polylang and WordPress locale. You can also set per-language privacy policy URLs so visitors always see the privacy page in their own language.</p>
<h4>Performance Mode</h4>
<p>Enable lazy loading to load the cookie banner only after the first user interaction (scroll, click, mouse move or touch). Since Google PageSpeed Insights does not simulate interactions, the banner will not appear in the performance audit — significantly improving your Core Web Vitals score.</p>
<h4>Built-in Languages</h4>
<p>English, Greek, German, French, Spanish, Italian, Portuguese, Dutch, Polish, Czech, Slovak, Hungarian, Romanian, Bulgarian, Croatian, Serbian, Slovenian, Estonian, Latvian, Lithuanian, Finnish, Swedish, Danish, Norwegian, Russian, Ukrainian, Chinese, Japanese, Arabic.</p>
<h3>External Services</h3>
<p>This plugin connects to external services provided by Google when the site administrator configures a Google Tag Manager (GTM) Container ID or a Google Analytics 4 (GA4) Measurement ID in the plugin settings.</p>
<h4>Google Tag Manager (GTM)</h4>
<p>When a GTM Container ID is entered in the plugin settings, the plugin loads the Google Tag Manager JavaScript snippet from Google’s servers. This happens on every front-end page load.</p>
<ul>
<li><strong>What it does:</strong> Loads the GTM container script so that tags configured inside GTM (analytics, advertising, etc.) can fire according to consent status.</li>
<li><strong>What data is sent:</strong> The GTM Container ID and standard browser information (IP address, user agent, page URL, referrer) are sent to Google’s servers when the script is loaded. Additional data may be collected depending on the tags configured within GTM by the site administrator.</li>
<li><strong>When it is sent:</strong> On every front-end page load, after the consent defaults have been set.</li>
<li><strong>Service provider:</strong> Google LLC</li>
<li><strong>Terms of Service:</strong> <a href="https://www.google.com/analytics/terms/tag-manager/" rel="nofollow ugc">https://www.google.com/analytics/terms/tag-manager/</a></li>
<li><strong>Privacy Policy:</strong> <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
</ul>
<h4>Google Analytics 4 (GA4) via gtag.js</h4>
<p>When a GA4 Measurement ID is entered and no GTM Container ID is configured, the plugin loads the Google Analytics gtag.js script from Google’s servers.</p>
<ul>
<li><strong>What it does:</strong> Loads the GA4 measurement script to collect website analytics data (page views, events, etc.) according to consent status.</li>
<li><strong>What data is sent:</strong> The GA4 Measurement ID and standard browser information (IP address, user agent, page URL, referrer) are sent to Google’s servers. Analytics data (page views, session data, events) is only collected according to the visitor’s consent choices.</li>
<li><strong>When it is sent:</strong> On every front-end page load, after the consent defaults have been set. Actual analytics data collection depends on user consent.</li>
<li><strong>Service provider:</strong> Google LLC</li>
<li><strong>Terms of Service:</strong> <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">https://marketingplatform.google.com/about/analytics/terms/us/</a></li>
<li><strong>Privacy Policy:</strong> <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
</ul>
<p><strong>Note:</strong> No data is sent to any external service by this plugin unless the site administrator explicitly configures a GTM Container ID or GA4 Measurement ID. The cookie consent preferences are stored locally in the visitor’s browser and are not transmitted to any external server.</p>


VGDev Cookie Banner for Consent Mode v2

GDPR cookie consent banner with Google Consent Mode v2, GTM & GA4 integration. Lightweight, self-hosted, multilingual, fully customizable.

Ontario

<p>Plain Cookie Consent is a no-frills GDPR + ePrivacy consent banner for WordPress. It ships a single banner, Google Consent Mode v2 defaults, a server-side audit log with pseudonymised subject hashing, a DSAR lookup helper, and constant-gated Meta Pixel / Microsoft Clarity / LinkedIn Insight Tag helpers — all under GPL v2, with no upsells and no external telemetry.</p>
<p>The plugin is designed to support a GDPR/ePrivacy-compliant consent setup. Final compliance depends on the site owner’s configuration and linked privacy policy.</p>
<h4>Core compliance features</h4>
<ul>
<li>Google Consent Mode v2 defaults injected at <code>wp_head</code> priority 1, before any tag manager or gtag snippet.</li>
<li>Early inline consent replay with a revision gate — consent recorded before a policy revision bump is not replayed; the banner re-prompts instead.</li>
<li>Server-side audit log (<code>wp_plain_consent_log</code>) with a privacy-preserving SHA-256 subject hash over a daily-rotating salt, and a 730-day default retention purge (filterable via constant).</li>
<li>Consent revision system with a “Force re-consent for all users now” admin action and strict rollback if the audit insert fails.</li>
<li>Two-step choice pattern: the first layer offers Accept All and Show Options; the preferences screen (one click away) offers equal-weight Accept All, Reject All, and Save Preferences buttons.</li>
<li>Server-mirror consent cookie via a cache-safe <code>GET /mirror-nonce</code> endpoint (<code>Cache-Control: no-store</code>), so full-page caching does not break nonce validation.</li>
<li>Geo targeting: the consent-required region set is the EEA (EU-27 plus Iceland, Liechtenstein, Norway) plus the United Kingdom. Detection uses the Cloudflare <code>CF-IPCountry</code> header when present, with a fail-safe default: if the country cannot be determined, the visitor is treated as in-scope.</li>
<li>CSV/JSON streamed export of the consent log, plus a pre-uninstall evidence warning with one-click export.</li>
<li>DSAR lookup admin tool: recompute a visitor’s subject hash from IP + User-Agent and list matching consent-log entries (GDPR Art. 15 support).</li>
</ul>
<h4>Integrations</h4>
<ul>
<li>Meta Pixel: define <code>PLAIN_COOKIE_CONSENT_FACEBOOK_PIXEL_ID</code> in <code>wp-config.php</code>.</li>
<li>Microsoft Clarity: define <code>PLAIN_COOKIE_CONSENT_CLARITY_PROJECT_ID</code> in <code>wp-config.php</code>.</li>
<li>LinkedIn Insight Tag: define <code>PLAIN_COOKIE_CONSENT_LINKEDIN_PARTNER_ID</code> in <code>wp-config.php</code>.</li>
<li>Public <code>window.plainCookieConsent</code> JavaScript API (<code>getCategories</code>, <code>hasConsent</code>, <code>onChange</code>, <code>onGrant</code>, <code>onRevoke</code>) for site-specific vendors.</li>
<li>Cookie cleanup on revoke with curated defaults for LinkedIn, TikTok, Hotjar, Clarity, Yandex Metrica, and Snapchat (<code>plain_cookie_consent_autoclear_cookies</code> filter).</li>
<li><code>localStorage</code> / <code>sessionStorage</code> cleanup on a real granted-to-revoked transition (<code>plain_cookie_consent_clear_storage_keys</code> filter).</li>
</ul>
<h4>Accessibility</h4>
<ul>
<li>The banner and preferences modal are attested against WCAG 2.1 AA.</li>
<li>axe-core smoke tests (<code>wcag2a</code>, <code>wcag2aa</code>, <code>wcag21aa</code> tags) run on every push and pull request via GitHub Actions.</li>
<li>Site-level accessibility remains the operator’s responsibility.</li>
</ul>
<h4>Languages</h4>
<p>Translation catalogs ship for nine languages: English, German, Russian, Spanish, French, Italian, Dutch, Polish, and Portuguese. Banner language auto-resolution covers all nine shipped languages, including regional variants (for example de-AT or pt-BR), with any other locale falling back to English. Any shipped catalog can also be selected explicitly, and translators can override strings the standard WordPress gettext way.</p>
<h4>Not included</h4>
<ul>
<li>TCF v2.2 (programmatic publishers).</li>
<li>Consent analytics dashboards beyond the read-only Consent Health widget.</li>
<li>Multi-domain consent sync.</li>
<li>Banner A/B testing.</li>
<li>Script auto-blocking beyond Consent Mode and the documented vendor helpers.</li>
</ul>
<h3>External services</h3>
<p>This plugin has no telemetry and never sends data to its own or the author’s servers. Consent records stay in your own WordPress database.</p>
<p>The plugin can optionally load three well-known third-party marketing/analytics tags <strong>on your behalf</strong>. Each one is OFF by default and only ever loads when BOTH of the following are true:</p>
<ol>
<li>You explicitly enable it by defining the matching constant in <code>wp-config.php</code>, and</li>
<li>The visitor grants the relevant consent category in the banner.</li>
</ol>
<p>If you do not define these constants, the plugin makes no third-party requests at all. Once enabled, the tag still loads only after the visitor grants the relevant consent category in the banner.</p>
<h4>Meta (Facebook) Pixel</h4>
<p>Optional advertising measurement. Enabled by defining <code>PLAIN_COOKIE_CONSENT_FACEBOOK_PIXEL_ID</code>. When a visitor grants <strong>advertising</strong> consent, the plugin loads <code>https://connect.facebook.net/en_US/fbevents.js</code> and initialises the Pixel with your Pixel ID. From then on, on each page view, Meta receives standard Pixel data: your Pixel ID, the page URL and referrer, the visitor’s IP address and browser/user-agent, and a PageView event. Nothing is sent before advertising consent.<br />
Provider: Meta Platforms, Inc. Privacy Policy: https://www.facebook.com/privacy/policy/ — Business Tools Terms: https://www.facebook.com/legal/terms/businesstools</p>
<h4>Microsoft Clarity</h4>
<p>Optional session analytics (heatmaps and session insights). Enabled by defining <code>PLAIN_COOKIE_CONSENT_CLARITY_PROJECT_ID</code>. When a visitor grants <strong>analytics</strong> consent, the plugin loads <code>https://www.clarity.ms/tag/<your-project-id></code>. From then on, on each page view, Microsoft receives Clarity analytics data: your project ID, the page URL, the visitor’s IP address and browser/user-agent, and interaction events such as clicks and scrolls. Nothing is sent before analytics consent.<br />
Provider: Microsoft Corporation. Privacy Statement: https://www.microsoft.com/privacy/privacystatement — Clarity Terms of Service: https://clarity.microsoft.com/terms</p>
<h4>LinkedIn Insight Tag</h4>
<p>Optional advertising measurement on LinkedIn. Enabled by defining <code>PLAIN_COOKIE_CONSENT_LINKEDIN_PARTNER_ID</code>. When a visitor grants <strong>advertising</strong> consent, the plugin loads <code>https://snap.licdn.com/li.lms-analytics/insight.min.js</code> with your Partner ID. From then on, on each page view, LinkedIn receives Insight Tag data: your Partner ID, the page URL, and the visitor’s IP address and browser/user-agent. Nothing is sent before advertising consent.<br />
Provider: LinkedIn Corporation. Privacy Policy: https://www.linkedin.com/legal/privacy-policy — LinkedIn Ads Agreement: https://www.linkedin.com/legal/ads-agreement</p>
<h3>Disclaimer</h3>
<p>This plugin is provided “as is”, free of charge, for evaluation and use at<br />
the site operator’s own discretion and risk.</p>
<ul>
<li>The site operator alone chooses which plugins to install and run on their<br />
site, and bears full responsibility for that choice and its consequences.</li>
<li>The plugin is offered for informational and evaluation purposes. The<br />
authors make no guarantees and no promises of any kind — including<br />
correctness, completeness, fitness for a particular purpose, or<br />
uninterrupted operation.</li>
<li>Software may contain errors. Any errors, malfunctions, data loss, or<br />
legal consequences arising from the use of this plugin are the sole<br />
responsibility of the site operator.</li>
<li>Nothing in this plugin or its documentation constitutes legal advice.<br />
The plugin is designed to support a GDPR/ePrivacy-oriented consent setup,<br />
but it does not and cannot guarantee legal compliance of any specific<br />
site — final compliance always depends on the operator’s configuration,<br />
vendors, and policies.</li>
<li>The warranty disclaimer and limitation of liability are governed by<br />
sections 11 and 12 of the GNU GPL v2 license that ships with this plugin.</li>
</ul>


Plain Cookie Consent

Minimal clean-room GDPR/ePrivacy consent banner with Google Consent Mode v2, early inline replay, DSAR helper, and no upsells.

VGDev Cookie Banner for Consent Mode v2 vs Plain Cookie Consent