FrontConsent

Description

FrontConsent shows a lightweight, configurable cookie consent banner with Accept and Reject actions, following the guide published by Spain’s AEPD (Agencia Española de Protección de Datos) as well as GDPR/ePrivacy requirements. Rejecting costs the visitor the same number of clicks as accepting, no non-essential cookie is set before the visitor decides, and the decision can be changed at any time.

Choose between a full-width bottom bar, a boxed panel (bottom-left or bottom-right) or a centered popup, and customize the message, button labels, cookie policy page, accent color and cookie expiration.

Google Consent Mode v2:
Google Tag Manager and/or GA4 are only requested and loaded after a visitor accepts — never before — and returning visitors who already accepted get the scripts on normal page load. Implements Google Consent Mode v2, so it also holds back tracking from other analytics/ads plugins that respect it — including Google Site Kit — until the visitor decides.

Tracking integrations:
Paste a Google Tag Manager or GA4 ID (or install snippet), or a Clientify, Brevo or ChatGPT Ads snippet, and FrontConsent automatically detects which tool it belongs to and only loads it after consent.

Acceptance stats:
The settings page shows a simple accepted/rejected acceptance-rate stat (site administrators are excluded from the count).

Advanced Cookie Management (FrontConsent PRO):
Extend Cookie Notice with separate Necessary, Analytics and Marketing preferences, a customizable preferences dialog and a reusable trigger that lets visitors update their choices later. Google Ads, Meta Pixel and Microsoft Clarity only run after the relevant category is accepted. It also supports the official Meta Pixel for WordPress plugin by holding its Pixel and Conversions API signals until Marketing consent.

More information in the FrontConsent PRO page.

External services

This plugin only connects to external services that the site owner explicitly configures — none are contacted by default. All connections below happen entirely in the visitor’s own browser, after that visitor has accepted the relevant cookie category; no data is ever sent from the server.

Google Tag Manager / Google Analytics 4 (GA4)
If a site administrator enters a Google Tag Manager container ID or a GA4 Measurement ID in the plugin settings, the visitor’s browser loads the corresponding Google script (https://www.googletagmanager.com/gtm.js or https://www.googletagmanager.com/gtag/js) once the visitor accepts. This sends standard Google Tag Manager/Analytics data (e.g. page views, and any events the site’s own tag configuration adds) to Google.
Service provided by Google: Terms of Service, Privacy Policy.

Clientify Analytics (Plus or classic)
If a site administrator adds a Clientify Analytics tracking ID, the visitor’s browser loads Clientify’s tracking script (https://analyticsplusdev.clientify.net or https://analytics.clientify.net) once the visitor accepts, sending page-view and visitor tracking data to Clientify.
Service provided by Clientify: Terms of Service, Privacy Policy.

Brevo
If a site administrator adds a Brevo tracking snippet, the visitor’s browser loads Brevo’s SDK (https://cdn.brevo.com/js/sdk-loader.js) once the visitor accepts, sending visitor tracking data to Brevo.
Service provided by Brevo: Terms of Service, Privacy Policy.

ChatGPT Ads (OpenAI)
If a site administrator adds a ChatGPT Ads Pixel ID, the visitor’s browser loads OpenAI’s ads pixel script (https://bzrcdn.openai.com/sdk/oaiq.min.js) once the visitor accepts, sending conversion/attribution tracking data to OpenAI.
Service provided by OpenAI: Terms of Use, Privacy Policy.