Title: Wiwi Cookie Consent
Author: Naiche
Published: July 21, 2026
Last modified: July 21, 2026
---
Search plugins
# Wiwi Cookie Consent
By [Naiche](https://profiles.wordpress.org/naiches/)
[Download](https://downloads.wordpress.org/plugin/wiwi-cookie-consent.1.0.0.zip)
* [Details](https://wordpress.org/plugins/wiwi-cookie-consent/#description)
* [Reviews](https://wordpress.org/plugins/wiwi-cookie-consent/#reviews)
* [Installation](https://wordpress.org/plugins/wiwi-cookie-consent/#installation)
* [Development](https://wordpress.org/plugins/wiwi-cookie-consent/#developers)
[Support](https://wordpress.org/support/plugin/wiwi-cookie-consent/)
## Description
Wiwi Cookie Consent is a small, dev-friendly consent banner. Add your tracking scripts(
Google Analytics 4, Meta Pixel, Google Ads, or anything else) through the settings
page, and the plugin blocks them from running until a visitor actually consents
to that category — nothing more, nothing less.
Built for typical brochure/marketing sites without visitor accounts or logins —
not for membership sites, and not a full cookie-compliance suite. See “What it deliberately
does not do” below for the exact boundary.
#### What it does
* Opt-in by default — every category starts OFF; nothing tracks until a visitor
chooses to allow it.
* Real script blocking — tracking code is wrapped in an inert `` element
and only activated after consent, not just hidden with CSS.
* Per-category consent — Marketing, Analytics, and Functional, each independently
toggleable in the preferences modal.
* Quick-add templates for Google Analytics 4, Meta Pixel, and Google Ads — enter
your ID, done.
* Fully accessible — keyboard navigation, focus trap, ARIA attributes on the preferences
modal.
* Style it yourself — an optional toggle disables the plugin’s own CSS entirely
while keeping every ID and class in place, so you can theme the banner from your
own stylesheet.
* Dutch and English out of the box.
#### What it deliberately does not do
* **No consent logging.** Nothing about your visitors is stored server-side — no
IP, no timestamp, no consent database. Built for anonymous-visitor sites without
accounts/logins; there’s no identified user to tie a server-side consent record
to in the first place. See the notice on the plugin’s own settings page for the
full reasoning.
* **No validation of how you classify a cookie.** You decide which category (Marketing/
Analytics/Functional) each cookie belongs to, and the plugin blocks/unblocks
it accordingly — correctly and reliably. It cannot know whether _you_ classified
it correctly (e.g. labelling an analytics cookie as “Functional” to skip consent
is a real, commonly-fined mistake). Getting the categories right is your legal
responsibility.
* **No site-wide cookie scanning or auditing.** The plugin doesn’t crawl your site
to discover what cookies exist — you declare them yourself in the cookie table.
Automatic cookie discovery is a fundamentally different (and much heavier) category
of tool; see the FAQ.
* **No scanning or filtering of other plugins, themes, or embedded content.** This
plugin only gates the tracking code you configure through its own settings —
it will not detect or block a hardcoded script elsewhere on your site, or a YouTube/
Maps/social-widget embed. Continuously scanning and filtering arbitrary page
content would need to watch the DOM on every page (e.g. a `MutationObserver`),
which runs against this plugin’s zero-front-end-impact design goal. That stays
your responsibility — self-host fonts, use privacy-enhanced embed modes, or click-
to-load placeholders.
* **No Terms, Privacy Policy, or Cookie Policy content.** The Banner & Modal Text
settings let you _link_ to existing WordPress pages for these — the plugin does
not write, generate, or validate their content. You (or your agency) must write
and maintain Algemene voorwaarden, Privacybeleid/Privacyverklaring, and Cookiebeleid
yourselves.
* **No bundled updater, no telemetry, no phone-home.** Updates come from the WordPress.
org repository like any other plugin.
### External services
This plugin does not connect to any external service on its own. It stores no data
off-site, has no telemetry, and phones home to nothing. It is a consent gate, not
a tracker.
Its purpose, however, is to let a site administrator add their _own_ third-party
tracking code and have it load only after a visitor consents. A third-party service
is contacted **only when both** of these are true: (1) the administrator has configured
that service (via a built-in quick-add template or by pasting equivalent code), **
and** (2) a visitor has granted consent to the relevant cookie category. With no
configuration, the plugin makes no external requests at all.
The services offered by the built-in quick-add templates are:
**Google Analytics 4 / Google Ads (Google Tag — gtag.js)**
Loaded from `https://
www.googletagmanager.com/gtag/js` only when the administrator enters a Google Analytics
Measurement ID (Analytics category) or a Google Ads Conversion ID (Marketing category)
and the visitor consents to that category. Once loaded, Google’s script may set
cookies and send the visitor’s IP address, page URL, and interaction events to Google
to measure site usage and advertising conversions. Terms of Service: https://policies.
google.com/terms — Privacy Policy: https://policies.google.com/privacy
**Meta Pixel (Facebook)**
Loaded from `https://connect.facebook.net/en_US/fbevents.
js` only when the administrator enters a Meta Pixel ID and the visitor consents
to the Marketing category. Once loaded, Meta’s script may set cookies and send the
visitor’s IP address, page URL, and events (e.g. PageView) to Meta to measure advertising
effectiveness. Terms of Service: https://www.facebook.com/legal/terms — Data Policy:
https://www.facebook.com/privacy/policy/
The administrator may also paste any other tracking code of their choosing; in that
case the external service contacted is whichever one that code refers to, and disclosing
it is the site administrator’s responsibility.
## Screenshots
[⌊The cookie banner as shown to visitors.⌉⌊The cookie banner as shown to visitors
.⌉[
The cookie banner as shown to visitors.
[⌊The preferences modal with per-category toggles.⌉⌊The preferences modal with per-
category toggles.⌉[
The preferences modal with per-category toggles.
[⌊The Cookie Management admin page.⌉⌊The Cookie Management admin page.⌉[
The Cookie Management admin page.
## Installation
1. Upload the `wiwi-cookie-consent` folder to `/wp-content/plugins/`, or install the
zip via Plugins Add New Upload Plugin.
2. Activate the plugin through the Plugins menu in WordPress.
3. Open the new **Cookies** menu in the admin sidebar.
4. Add your tracking code per category (or use the quick-add templates), customise
the banner text, and save.
Requires PHP 8.0 or higher and WordPress 6.0 or higher.
## FAQ
### Does this plugin store or log what visitors consented to?
No. There is no server-side consent database. See “What it deliberately does not
do” above and the notice shown at the top of the plugin’s own settings page.
### Does it block cookies from other plugins or themes?
No. It only gates tracking code entered through its own settings screen. If you
have a tracking script hardcoded in your theme or added by another plugin, route
it through Wiwi Cookie Consent’s settings if you want it consent-gated, or handle
it separately.
### Does it check whether I’ve categorised my cookies correctly?
No. The plugin blocks and unblocks exactly what you tell it to, exactly as configured—
that mechanism is reliable. Whether a given cookie genuinely belongs in Marketing,
Analytics, or Functional (and whether “Functional” is even the correct exemption
for it) is a legal judgement call only you can make. Mislabelling a tracking cookie
as “Functional” to avoid asking for consent is one of the most common cookie-banner
violations regulators actually fine — the plugin can’t catch that for you.
### Can this plugin scan my site and find all my cookies for me?
No, and that’s intentional. Automatic cookie/tracker discovery is a genuinely different,
much heavier category of tool (the kind built by dedicated consent-management platforms).
This plugin stays a lightweight blocker for the tracking code you explicitly configure—
it does not crawl pages, inspect third-party scripts, or maintain its own cookie
database.
### Do I still need to write my own Privacy Policy / Terms / Cookie Policy?
Yes, always. The plugin lets you link the banner to existing WordPress pages for
Terms & Conditions, Privacy Policy, and Cookie Policy — it does not write or supply
any legal content. That text is your (or your agency’s) responsibility.
### Does it collect any data or phone home?
No. There is no usage tracking, analytics, telemetry, or licensing call-home.
### Can I fully restyle the banner?
Yes. Enable “Don’t load the plugin’s default stylesheet” under Styling in the settings
page, and style `#wcc-cookie-banner`, `#cookie-preferences-modal`, `.wcc-btn`, `.
wcc-toggle`, and the other existing classes/IDs from your own theme CSS. The banner’s
show/hide and open/close behaviour works independently of the stylesheet.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Wiwi Cookie Consent” is open source software. The following people have contributed
to this plugin.
Contributors
* [ Naiche ](https://profiles.wordpress.org/naiches/)
[Translate “Wiwi Cookie Consent” into your language.](https://translate.wordpress.org/projects/wp-plugins/wiwi-cookie-consent)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/wiwi-cookie-consent/),
check out the [SVN repository](https://plugins.svn.wordpress.org/wiwi-cookie-consent/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/wiwi-cookie-consent/)
by [RSS](https://plugins.trac.wordpress.org/log/wiwi-cookie-consent/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.0
* Initial release.
## Meta
* Version **1.0.0**
* Last updated **2 days ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.0.2**
* PHP version ** 8.0 or higher **
* Tags
* [avg](https://wordpress.org/plugins/tags/avg/)[cookie banner](https://wordpress.org/plugins/tags/cookie-banner/)
[cookie consent](https://wordpress.org/plugins/tags/cookie-consent/)[GDPR](https://wordpress.org/plugins/tags/gdpr/)
[privacy](https://wordpress.org/plugins/tags/privacy/)
* [Advanced View](https://wordpress.org/plugins/wiwi-cookie-consent/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/wiwi-cookie-consent/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/wiwi-cookie-consent/reviews/)
## Contributors
* [ Naiche ](https://profiles.wordpress.org/naiches/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/wiwi-cookie-consent/)