WP Manifestindependent plugin directory
manifest / privacy / digitizer-cookie-consent

Digitizer Cookie Consent

Cookie consent banner for WordPress: categories, blocking until consent, Google Consent Mode v2, Hebrew and multilingual.

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/digitizers/digitizer-cookie-consent/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

A cookie consent banner for Hebrew and multilingual sites: categories, blocking until consent, Google Consent Mode v2, and cookies deleted on refusal.

Description

Digitizer Cookie Consent shows a cookie consent banner, holds back the scripts you list until a visitor agrees to their category, and tells Google's tags and other plugins what the visitor chose. It was built for Hebrew and multilingual sites, and works on any site.

What it does

  • Four categories - essential, functional, analytics, marketing - each with its own switch in the preferences view.
  • Scripts you paste per category (Google Analytics, Tag Manager, Meta Pixel, any snippet) load only after the visitor consents to that category.
  • Google Consent Mode v2: the defaults are set first in the page head, before any Google tag, and updated from the visitor's choice.
  • The WP Consent API: plugins that read it, such as Site Kit and WooCommerce order attribution, follow the visitor's choice.
  • When a visitor refuses or withdraws a category, the cookies you list for it are deleted from the browser, and again on every page while it stays refused.
  • A link anywhere on the site reopens the banner: any link to #dpt-cookie-settings, an element with the class dpt-cb-open, or the [dpt_cookie_settings] shortcode. A floating button does the same.
  • Cache-proof: the banner is rendered hidden and a small script in the head decides whether to show it, so a page cache or CDN never shows it to a visitor who has already answered. Built-in compatibility with WP Rocket and Cloudflare Rocket Loader.

Built for Hebrew and multilingual sites

Texts are edited per language - Hebrew and English are seeded, and any language can be added by its code. The language is chosen per page from the WordPress locale, so it works with WPML, Polylang and TranslatePress, and the banner turns right-to-left or left-to-right with it. The settings screen is in Hebrew and English.

Design

Colors, fonts (or Elementor's global font), sizes, corner radius, positions, button styles, a background image, an overlay and entry animations - enough to match an existing banner with settings alone, no custom CSS.

Admin-provided scripts

The scripts you paste on the Scripts tab are stored as you entered them and printed on your site: after consent when script blocking is on, or in the page head when it is off. Only a user who may post unfiltered HTML can save scripts; anyone else's are filtered.

Your own legal review

This plugin gives you the tools - categories, blocking until consent, a reject button as prominent as accept, a way to withdraw consent. Whether a particular site meets the law that applies to it depends on what that site does. Check with your own legal adviser.

External services

None. The plugin sends nothing anywhere. Google's tags, if you use them, are your site's own, loaded as you configured them.

Installation

  1. Install and activate the plugin.
  2. The banner is live at once with its default texts. Go to Settings -> Cookie Consent to review the texts, the categories and the design.
  3. Paste each tracking script into its category on the Scripts tab, and turn on Google Consent Mode v2 if you use Google's tags.

Frequently Asked Questions

Does it make my site compliant?

It gives you the tools. Whether a site complies depends on what the site does and which law applies to it - check with your own legal advice.

Does it send data anywhere?

No. The visitor's choice is kept in their own browser (a first-party cookie and localStorage). Nothing is sent to Digitizer or anyone else.

I am moving from Digitizer Pro Tools' Cookie Banner.

Activate this plugin: it imports the module's settings - texts in every language, design, categories, scripts, the consent version - and keeps the same consent cookie, so visitors who already chose are not asked again. Digitizer Pro Tools steps aside while this plugin is active.

Can it delete cookies set by Facebook or LinkedIn?

Only the site's own cookies that scripts can read. Cookies set on other domains (.facebook.com, .linkedin.com, .doubleclick.net) and cookies marked HttpOnly are out of a web page's reach. WordPress's and WooCommerce's own cookies are never deleted.

How do I add a "cookie settings" link to my footer?

Link to #dpt-cookie-settings, give any element the class dpt-cb-open, or use the [dpt_cookie_settings] shortcode.

Does a choice carry over to my other subdomains?

Yes, by default: the choice is stored on the parent domain, so www, the bare domain and the site's other subdomains share it. If sibling subdomains are separate sites, keep the choice on each host with add_filter( 'digitizer_cookie_consent_cookie_domain', '__return_empty_string' );, or return the domain to use.

Screenshots

  1. The banner in Hebrew, in the corner of the page.
  2. The banner in English, as a bar along the bottom.
  3. The preferences view: a switch per category.

Changelog

1.0.0

  • First release on WordPress.org, from the Cookie Banner module of Digitizer Pro Tools 1.46.1.