內容簡介
Wiwi Cookie Consent 是一款小巧且開發者友好的同意橫幅外掛，專為不需要訪客帳號的行銷網站設計。它允許用戶在同意前阻止追蹤腳本運行，確保網站符合隱私要求。
【主要功能】
• 預設選擇加入，所有類別默認關閉
• 真正的腳本阻擋，僅在同意後啟用
• 每類別獨立同意，便於管理
• 快速添加 Google Analytics 4、Meta Pixel 和 Google Ads 模板
• 完全可訪問，支援鍵盤導航
• 自訂樣式，選擇禁用外掛 CSS
外掛標籤
開發者團隊
原文外掛簡介
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, plus an always-on Necessary section that lists the essential cookies.
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.
