Geenen Cookie Banner for Google Consent Mode v2
| 开发者 | geenenitsysteme |
|---|---|
| 更新时间 | 2026年8月17日 16:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Google Consent Mode v2: the default for ad_storage, ad_user_data, ad_personalization and analytics_storage is always "denied".
- Google Tag Manager support: configure a GTM container ID (GTM-XXXXXXX) in addition to, or instead of, GA4/Google Ads.
- GA4 (G-XXXX) and optional Google Ads (AW-XXXX) configurable by tag ID.
- Granular categories: visitors can accept all, deny all, or open a details panel and choose Statistics (Google Analytics) and Marketing (Google Ads) individually. Essential is always active.
- Equal "Deny" button (GDPR). Withdrawal any time via the shortcode [geencb_settings_link] or window.geencbShowBanner().
- Open the banner from any footer/menu link: point a custom link to #geencb-settings or give any element the class geencb-open - no shortcode needed.
- Optional imprint link shown next to the privacy policy link inside the banner.
- Automatic theme colors: primary, background and text color can be derived from the active block theme palette, or set manually.
- Themeable via CSS custom properties, so the banner can be restyled from your theme's Additional CSS without touching plugin files.
- Cache-safe: the stored decision is read client-side from the cookie, so it works behind full-page caches such as WP Super Cache.
- Accessible: keyboard focus moves to the banner on open, Esc dismisses it, focus returns to the previously focused element.
安装:
- Upload the
geenen-cookie-bannerfolder towp-content/plugins/. - Activate the plugin.
- Under Settings -> Consent Banner enter your GA4 Measurement ID (and optionally a Google Ads ID and/or a GTM container ID) and adjust text, colors and position.
- Optionally place the shortcode
[geencb_settings_link], e.g. in the footer, so visitors can withdraw their consent.
屏幕截图:
常见问题:
Does the plugin set cookies before consent?
No. Before a click on "Accept all", "Deny" or "Save selection" no consent-requiring cookies are set. Consent Mode is "denied" and Google tags respect that. Only the functionally necessary cookie geencb_consent (your own decision) is stored after the click.
Is gtag.js or gtm.js loaded before consent?
That depends on the tag mode. In "Basic" mode (default) the scripts load only after the click on "Accept all" (or a saved selection granting a category) - before consent not a single request reaches googletagmanager.com. In "Advanced" mode the scripts load immediately without cookies, but send only denied signals (Consent Mode v2) until consent is given; this enables Google's conversion modeling.
Are any scripts loaded without a tag ID?
No. Without a configured GA4, Google Ads or GTM ID, no scripts are loaded and the banner is not shown.
Can I use Google Tag Manager?
Yes. Enter a GTM container ID (GTM-XXXXXXX) in the settings. It loads alongside GA4/Google Ads, or on its own. The same Consent Mode v2 defaults apply, because GTM shares the dataLayer.
How do I withdraw my consent?
Use the shortcode [geencb_settings_link] or the JavaScript call window.geencbShowBanner() to reopen the banner.
Can I change the banner design?
Colors and position are settings (Appearance section). Everything else is plain CSS: put it in your theme's Additional CSS panel - Appearance -> Editor -> Styles -> Additional CSS on block themes, Appearance -> Customize -> Additional CSS on classic ones - or in a child theme stylesheet. The quickest wins are the CSS custom properties --geencb-primary, --geencb-bg, --geencb-text and --geencb-primary-contrast, e.g. :root { --geencb-primary: #e11d48; }. Scope them to :root, not to #geencb-banner - the floating cookie settings button and the [geencb_settings_link] button sit outside the banner and read the same variables. The base styles use !important to survive theme CSS, so overriding those properties needs !important too.
I use a caching plugin with "delay" or "combine" JavaScript. Anything to watch out for?
Exclude the script handle geencb-consent from JavaScript delaying, combining and deferring. It carries the Consent Mode defaults and has to run before any Google tag on the page; if it is delayed while another plugin's tag is not, the tag fires before consent is signalled.
How do I add a cookie settings link to my footer menu?
Add a custom menu link (Appearance -> Menus -> Custom Links) with the URL #geencb-settings and a label such as "Cookie settings". The plugin opens the banner when it is clicked. Alternatively use the shortcode [geencb_settings_link], or give any element the CSS class geencb-open.
更新日志:
- Author is now "Geenen IT-Systeme GmbH" and links to the company site, and the plugin list entry carries a plugin website link.
- German translations are bundled again (
de_DEandde_DE_formal). WordPress picks them by the site language under Settings -> General; sites left on English stay English. - The floating revoke button setting now names the alternatives in its description: the shortcode
[geencb_settings_link], a link to#geencb-settings, or the classgeencb-open.
- First release in the WordPress.org plugin directory.
- Renamed the plugin and its text domain; all internal prefixes, the settings option, the shortcode, the consent cookie and the CSS class names changed accordingly. Settings from earlier builds are not carried over and have to be entered once.
- Removed the Custom CSS field. Style the banner from your theme's Additional CSS panel or a child theme stylesheet instead. The CSS custom properties keep their meaning but follow the new prefix:
--geencb-primary,--geencb-bg,--geencb-textand--geencb-primary-contrast. - The Consent Mode bootstrap and the settings page script are enqueued through the WordPress script loader instead of being printed as inline tags.
- Dropped the bundled German translations. Translations now come from translate.wordpress.org and are unavailable until the plugin is published there, so the banner falls back to English until then.
- Last of the builds handed out directly, before this plugin was submitted to the directory. Notes for those earlier versions are not repeated here. They installed under a different folder name, so WordPress treats them as a separate plugin: deactivate and delete the old copy before installing this one.