ConsentPilot
GDPR consent management for WordPress: cookie banner, blocking of tracking scripts and iframes before consent, and a consent log with CSV export.
Use with caution
ConsentPilot works, but test it on a staging site before relying on it in 2026. It runs on 20+ sites and was last updated 2 months ago, and scores 45/100 on our health check.
- Small user base (20+ active installs)
- Very few reviews so far
- Only tested up to WordPress 6.7 (latest is 7.1)
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release β each site that auto-updates counts as a download.
Rankings
Where ConsentPilot stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| consent | >100 |
| cookie banner | >100 |
| cookie consent | >100 |
| GDPR | >100 |
| privacy | >100 |
Version adoption
Share of active sites per release.
About ConsentPilot
From the official readme Β· v0.1.10Description
ConsentPilot is a GDPR consent management plugin for WordPress. Known tracking
scripts and embedded iframes (YouTube, Vimeo, maps) stay blocked in the page
until the visitor agrees to the relevant category, and every consent is
logged in the database as documentation, as required by GDPR art. 7.1.
ConsentPilot is configurable out of the box: choose between three banner
layouts, position, colors and banner text; describe your cookie categories;
add custom blocking patterns for tracking scripts not covered by the built-in
list; and export the consent log as CSV for compliance documentation.
Features
- Consent banner in three layouts: box, bar or popup
- “Accept all”, “Decline all” and per-category choice
- Blocks known tracking scripts before consent, Google Analytics, Google
Tag Manager, Meta Pixel, Hotjar, LinkedIn and more - Also blocks tracking scripts hosted on your own domain
- Iframe blocking for YouTube, Vimeo, Google Maps and Spotify
- Custom blocking patterns, block anything you add yourself
- Custom cookie categories with descriptions
- Consent log in the database with hashed, anonymized IP
- CSV export of the consent log for documentation
- Policy versioning, request fresh consent when your privacy policy changes
- Google Consent Mode v2 integration for Ads/Analytics in the EEA
- Geo-targeting, only show the banner in selected regions (with Cloudflare
or a custom GeoIP integration) - Keyboard accessible, light/dark theme aware
- No frontend dependencies, the banner is lightweight and fast
- Fully translatable
Support and documentation
Full documentation, screenshots and a contact form are available on the
plugin homepage at helene.cloud/consentpilot.html.
Bug reports and feature requests can also be sent through the contact form
on helene.cloud.
Installation
- Upload the
consentpilotfolder to/wp-content/plugins/, or install via
“Plugins β Add New β Upload Plugin”. - Activate the plugin under “Plugins” in wp-admin.
- Go to “ConsentPilot β Settings” to customize the banner.
- Describe your cookie categories under “ConsentPilot β Cookies”.
Requirements: WordPress 6.3+, PHP 7.4+.
Changelog
Fixes the issues raised in the WordPress.org plugin review: removed output-buffer pattern and removed paywall checks on Consent Mode v2 and geo-targeting.
0.1.10
- Fixed: on the page view where a visitor accepts cookies,
Google Analytics or Google Tag Manager would fail to send
the pageview because the consent update reached dataLayer
after the gtag script had already loaded and dispatched its
first pageview as consent-less. The consent update is now
pushed to dataLayer before the tracking scripts are
unblocked, so gtag reads a granted state on its very first
read of the queue. The visitor who accepts and closes the
tab is now counted. - Improved: scripts caught by the wp_head guard (introduced
in 0.1.8) now correctly restore their src attribute from
data-consentpilot-src when consent is given. Previously the
unblock routine rebuilt the script element without setting
src, so head-guarded scripts never fetched. - Improved: Consent Mode v2 consent updates write directly to
window.dataLayer via a local gtag wrapper instead of
depending on window.gtag being defined as a function at
call time, matching Google’s recommended integration
pattern.
0.1.9
- Compliance: “Accept all” and “Decline all” now share the same
visual weight as a matched pair of primary-coloured buttons.
The previous default made “Accept all” more prominent than
“Decline all”, which EDPB Guidelines 03/2022 on deceptive
design patterns and the Norwegian Data Protection Authority
identify as a pattern that can render consent invalid. The
“Customize” button remains a lighter outline button, which is
permitted since it is not a consent choice itself but a
gateway to per-category selection. Existing custom-CSS
overrides in the Pro version are not affected. - Added a small stable public JavaScript API on window.ConsentPilot
so other plugins and theme code can integrate without guessing
at CSS class names. Methods:
window.ConsentPilot.open() – open the consent panel
window.ConsentPilot.getConsent() – read stored consent
window.ConsentPilot.hasConsent(cat) – check a category
The internal method name openSettings() introduced in 0.1.7
is kept as an alias for backwards compatibility. - Fixed: scripts blocked by the wp_head guard (introduced in
0.1.8) never actually loaded after consent was given. The
head guard moves the “src” attribute to “data-consentpilot-src”
to neutralize the script, but the unblock routine only knew
about the old “type=text/plain” pattern from the enqueue-side
blocker, so it rebuilt the script element without ever
restoring the src. The unblock routine now restores src from
data-consentpilot-src, mirroring how iframes are already
handled. This was the root cause of Google Analytics not
firing on the page view where consent was given. - Fixed: Consent Mode v2 consent updates are now written
directly to window.dataLayer instead of relying on
window.gtag being defined as a function. gtag scripts load
async, and the previous defensive check returned silently
when window.gtag was not yet a function, dropping the
consent-update signal for that page view. dataLayer is a
queue that GA/GTM process when their script finishes
loading, matching Google’s own recommended pattern.
0.1.8
- Improved: raw tracking scripts embedded in themes or in
“header/footer” plugin fields are now also caught. Previously
ConsentPilot only blocked scripts that went through the
WordPress script queue (wp_enqueue_script). A small guard is
now written into the page head at priority 1 that watches the
document for hardcoded tags from Site Kit,
WPCode, Insert Headers and Footers, GTM plugins, and theme
header code, and neutralizes matched patterns before the
browser fetches them. - Scripts placed literally in header.php before the wp_head()
call still cannot be blocked – the plugin has no code running
at that point. This is a rare setup; move the script into a
wp_head hook or into WordPress’s enqueue system.
0.1.7
- Added a new setting to hide the floating “Cookies” reopen
button. Site owners who prefer a discreet footer link over a
permanently visible corner button can now switch it off under
Settings > Appearance. - Added a [consentpilot_link] shortcode that renders an “Change
cookie settings” link anywhere in a page, post, or widget. The
link opens the consent settings on click. Optional text and
class attributes: [consentpilot_link text=”Cookies”]. - Added a data-consentpilot-open attribute so a theme developer
can hook a menu item or footer link to the same open action
without a shortcode. - Added a small public JS API: window.ConsentPilot.openSettings()
for cases where JavaScript is the right integration point. - Cleaned up two leftover “(Pro)” comments that suggested Consent
Mode v2 and geo-targeting were paywalled – both have been fully
free since 0.1.1.
0.1.6
- Fixed: the floating “Cookies” reopen button now uses the primary
colour you have configured under Settings β Appearance, instead
of falling back to the default blue on returning visitors.
Previously the colour was only applied when the full banner
rendered, so the reopen button on returning sessions never
picked it up.
0.1.5
- Fixed: when a visitor reopens the consent banner after having
saved their choices, the checkboxes now reflect what was
previously saved (e.g. all four categories checked after
“Accept all”) instead of resetting to only “Necessary”. Their
actual saved consent was never lost β only the UI display was
incorrect β but the mismatch was confusing.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own β no account needed.
Best ConsentPilot alternatives
All consent plugins βFAQ
ConsentPilot: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org Β· checked Nov 16, 2026
Is ConsentPilot free?
Yes. ConsentPilot is free to download and use from the official WordPress.org plugin directory.
Is ConsentPilot safe to use in 2026?
ConsentPilot works, but test it on a staging site before relying on it in 2026. It runs on 20+ sites and was last updated 2 months ago, and scores 45/100 on our health check.
How many websites use ConsentPilot?
ConsentPilot is active on 20+ WordPress websites and has been downloaded 656 times since it launched in May 2026. It was downloaded 74 times in the last 30 days.
Does ConsentPilot work with WordPress 7.1?
ConsentPilot is officially tested up to WordPress 6.7.11, while the latest release is 7.1.4. It may still work, but try it on a staging site first.
What PHP version does ConsentPilot need?
ConsentPilot requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was ConsentPilot last updated?
The latest version, 0.1.10, was released on September 24, 2026 (2 months ago).
Who makes ConsentPilot?
ConsentPilot is developed and maintained by Helene Groenberg.
What are the best alternatives to ConsentPilot?
The most popular alternatives to ConsentPilot are CookieAdmin (400K+ installs), WP Consent API (300K+ installs) and TermsFeed AutoTerms: Privac⦠(70K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages β with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org β no credit card




