Digivator Cookie Consent Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Digivator Cookie Consent asks visitors which cookies they are happy for your website to use, remembers the answer, and passes it on to the tools that need it. Optional categories stay off until a visitor agrees to them.
Built to work with Site Kit by Google
Digivator Cookie Consent is built to work with Site Kit by Google. Site Kit prints the Google tag for Analytics and other Google services, and Digivator Cookie Consent holds that tag back until a visitor agrees to Statistics or Marketing, then tells Google Consent Mode what the visitor chose. No extra setup is needed. Site Kit by Google is a product of Google. This plugin is independent and is not affiliated with or endorsed by Google.
Categories
- Essential is always on and cannot be switched off. It covers storage the site needs to work, including remembering the visitor’s cookie choices.
- Statistics covers analytics and measurement, including Google Analytics. Google Analytics is never treated as essential.
- Preferences covers remembering visitor choices and personalisation.
- Marketing covers advertising, remarketing and marketing tracking.
The banner
The default wording is: “We use cookies to understand how visitors use this website and offer personalised experiences. You can choose which cookies to allow.” You can edit it in the settings.
- Accept essential switches off statistics, preferences and marketing, saves the choice, updates the WordPress Consent API and Google Consent Mode, and removes the banner straight away.
- Accept all switches on all four categories, saves the choice, updates the same integrations, and removes the banner straight away.
- Cookie preferences opens a window with a switch for each optional category. Nothing is preselected. Essential is shown as always on. A Save preferences button stores the visitor’s real choices and closes the window.
Accept essential and Accept all are the same size and weight so neither is favoured.
Changing or withdrawing consent
A small floating Cookie preferences button appears once a choice has been made (you can turn it off). You can also add a link to your footer or menu. Visitors can reopen the window at any time, change each category and save.
Choices are remembered
- The choice is stored in a first-party cookie called
digivator_cookie_consentwith the consent version, a timestamp and one true or false value per optional category. The cookie isSameSite=Lax, isSecureon HTTPS and is limited to your site’s path. - If the browser refuses the cookie, the same record is kept in
localStorageinstead. If both are blocked, the visitor’s choice applies to the current page only and they are asked again on the next page. Storage failures never switch an optional category on. - A missing, malformed, expired or old-version record counts as no consent.
- Change the Consent version setting when your policy or the cookies you use change in a material way, and every visitor is asked again.
- No personal data is collected. The plugin has no tracking, no telemetry and makes no requests to any other site.
Script blocking
A banner alone does not stop tracking, so Digivator Cookie Consent can hold back scripts that you register. A held-back script is printed as an inert type="text/plain" placeholder and is only started once the visitor allows its category. The page output is identical for every visitor, so page caching cannot hand one visitor’s scripts to another.
Built in, and on by default, the plugin holds back Google tags that WordPress prints through its script functions: the Google tag (gtag.js) from Google Site Kit including its inline setup code, the Google Tag Manager container snippet, and Google AdSense. You can register your own scripts by handle, by URL or by hand-written markup. See “Developer notes” below.
WordPress Consent API
If the official WP Consent API plugin is active, Digivator Cookie Consent:
- declares itself as a supporting plugin and sets the consent type to opt-in (PHP filter
wp_get_consent_typeand JavaScriptwindow.wp_consent_type) - keeps these documented categories in step with the visitor’s choice using
wp_set_consent():functional(always allow),statisticsandstatistics-anonymous(both follow Statistics),preferences, andmarketing - uses only the documented values
allowanddeny - reports
functionalas allowed even before a choice is made, because essential storage never needs consent - resets any stale “allow” values to “deny” when there is no valid saved choice, for example after the consent version changes
- registers its own cookie with
wp_add_cookie_info()and matches the Consent API cookie lifetime to your “Remember choices for” setting
If the plugin is not installed, everything else works and no JavaScript errors occur. The Consent API only passes choices around. Registering a category does not block anything, so other plugins must read the choice (wp_has_consent()) or be registered with Digivator Cookie Consent to be held back.
Google Consent Mode v2
When enabled (the default) Digivator Cookie Consent runs gtag('consent', 'default', ...) in the head before any other script, with everything optional denied. If the visitor has already chosen, a matching gtag('consent', 'update', ...) follows immediately. Every later choice sends a new update straight away, including withdrawals.
Category
Consent Mode signals
Essential (always on)
functionality_storage, security_storage
Statistics
analytics_storage
Preferences
personalization_storage
Marketing
ad_storage, ad_user_data, ad_personalization
This is the same category split that Google Site Kit 1.191.0 uses in its own Consent Mode and WP Consent API mapping. You can change it with the digivator_cookie_consent_google_signals filter.
Accessibility
The banner and window work on desktop, tablet and mobile. They are keyboard accessible, have visible focus outlines, use labelled controls and ARIA attributes, announce saves to screen readers, use the native modal dialog element so focus stays in the window while it is open and returns afterwards, and respect reduced-motion settings. While the banner is showing, the page keeps extra space and scroll padding so the banner never hides the control that has keyboard focus (WCAG 2.2 criterion 2.4.11). These checks were made with automated and keyboard tests in Chromium. The banner has not been manually tested with screen readers.
Colours
Choose every colour in Settings > Digivator Cookie Consent with the native WordPress colour pickers. A live preview updates as you pick, and the page warns you if a pairing falls below WCAG contrast. Defaults are a purple and navy palette.
Compliance readiness checklist
Settings > Digivator Cookie Consent includes a ticked checklist for UK GDPR and PECR, EU GDPR and ePrivacy, Google’s requirements and WCAG 2.2 level AA. Each item has a plain text status:
- Built in means the plugin does it by design and automated tests cover it.
- Set up on this site or Action needed is worked out from your saved settings, for example whether the banner is on, a privacy policy link is set, Google tags are held back, Consent Mode is on and your colours are readable.
- You confirm is for things only you can know, such as whether your privacy policy lists your cookies. Tick the box when it is true.
- Not covered lists what the plugin does not do, such as server-side records of consent, cookie scanning, IAB TCF certification and region detection. These are never counted as ticks.
The ticks show that settings and checks are in place. They are not legal advice or a certificate, and a full set of ticks does not mean your site complies with any law.
Important
Digivator Cookie Consent is a consent interface and a blocking helper. It does not make a website compliant with UK GDPR, PECR or any other law by itself. You remain responsible for the cookies and scripts on your site, your privacy policy and your legal compliance. See the limitations below.
Developer notes
Register an enqueued script
add_action( 'wp_enqueue_scripts', function () {
digivator_cookie_consent_register_script( 'my-pixel', 'marketing' );
} );
Call it before the script prints. A trailing * matches any handle with that prefix. Several categories mean “any of these” (array( 'statistics', 'marketing' )).
Register rules for handles, URLs or inline code
add_filter( 'digivator_cookie_consent_script_rules', function ( $rules ) {
$rules[] = array(
'category' => 'marketing',
'src' => 'connect.facebook.net/en_US/fbevents.js',
);
$rules[] = array(
'category' => 'statistics',
'inline' => 'window.myAnalytics',
);
return $rules;
} );
A rule needs category plus at least one of handle, src or inline. Rules apply to scripts printed through wp_enqueue_script(), wp_add_inline_script(), wp_print_script_tag() and wp_print_inline_script_tag(). Inline scripts that carry data rather than code are never blocked.
Hand-written markup
<script type="text/plain" data-digivator-cookie-consent-category="statistics" data-digivator-cookie-consent-src="https://example.com/tool.js"></script>
<script type="text/plain" data-digivator-cookie-consent-category="marketing">window.myPixel = true;</script>
Use data-digivator-cookie-consent-src instead of src. Several categories separated by spaces mean “any of these”.
Other hooks and functions
digivator_cookie_consent_google_signalsfilters the category to Consent Mode signal map.digivator_cookie_consent_cookie_patternsfilters the first-party cookie name patterns cleared on withdrawal.digivator_cookie_consent_preferences_link( $args )prints the preferences button.digivator_cookie_consent_has_consent( $category )is a server-side check of the saved choice. Do not use it to change the HTML of cacheable pages.- JavaScript:
window.DigivatorCookieConsentoffersgetConsent(),hasConsent( category ),open(),acceptAll(),acceptEssential()andsave( { statistics, preferences, marketing } ). - JavaScript event:
document.addEventListener( 'digivator_cookie_consent_updated', function ( e ) { /* e.detail.consent, e.detail.previous, e.detail.source */ } ). The standardwp_listen_for_consent_changeevent also fires when the Consent API is active.
Notes
- Scripts started after consent are added in document order. If a held-back script depends on another script, register both.
- A Content Security Policy must allow the inline scripts WordPress prints and the scripts you release.
Privacy
Digivator Cookie Consent stores the visitor’s choice in a first-party cookie (or localStorage) named digivator_cookie_consent. It contains the consent version, a timestamp and a true or false value for statistics, preferences and marketing. It holds no personal data and is never sent to the plugin authors or any other service. The plugin makes no external requests and loads no remote assets. When the WP Consent API plugin is active it also writes its own wp_consent_* cookies. A suggested paragraph for your privacy policy is added to Settings > Privacy > Policy Guide.
Screenshots
No screenshots provided
