Katrangan

Lobbit Cookie Consent is a cookie banner with a consent log, built around the GDPR and the guidelines of the Italian data protection authority (Garante) of 10 June 2021. Everything is stored on your own site: there is no account to open and no external dashboard.

Banner

Small banner with “Accept all” and “Reject” buttons of equal weight, and “Customize” to choose by category.
No cookie wall: the site stays usable before and after the choice.
The choice is stored together with the version of the policy; when the version changes, the banner asks again.
The preferences can always be reopened: floating icon or link in the footer, plus the [custcc_preferences] shortcode.
Texts, colours and position are set from the settings.

Consent log

Every choice is recorded with date, categories, policy version and a consent ID.
Search, filters, CSV export and automatic deletion after the retention period.
You choose what stays when the plugin is deleted: everything (the default), only the consent log, or nothing. When something would be deleted, the Plugins screen asks before deactivating or deleting it.
The IP address is truncated by default.

Integrations

Google Analytics 4 with Consent Mode v2: in basic mode (default) nothing is downloaded from Google before consent; advanced mode is optional.
Google Tag Manager, loaded after the first consent, with the consent state and a custcc_consent_update event at every choice.
Meta Pixel, loaded only after consent to marketing.
Custom scripts by category, inert in the page until consent.
The data-custcc-category attribute keeps any other script blocked until consent.

Cookie scan and Cookie Policy

Catalog of the most common cookies (WordPress, WooCommerce, Elementor, WPML, Polylang, Wordfence, Google Analytics, Google Ads, Meta Pixel, YouTube, Vimeo, reCAPTCHA, Cloudflare and Turnstile, Hotjar, Clarity, LinkedIn, TikTok) with provider, purpose, duration and category.
Scan from three sources: active plugins and connected services, Set-Cookie headers of a sample of pages of your own site, names of the cookies in the browser of the administrator.
Table of the cookies, to classify or correct by hand.
Cookie Policy page generated from the list of cookies and the data of the controller, through a block or the [custcc_cookie_policy] shortcode. It follows the list by itself.
A new optional cookie, a new company or a change of category make the plugin propose a new policy version, published only after you confirm.

Privacy Policy

Five steps of questions about what the site does, the data it uses, retention, recipients and special cases.
Privacy Policy page generated from the answers, through a block or the [custcc_privacy_policy] shortcode.
The two policies and the banner link to each other.

Export and import

The configuration in a JSON file: settings, controller, list of the cookies, Privacy Policy answers. A backup, or a starting point for another site.
Before an import you see what would change, part by part, and choose what to write.

Accessibility

Banner, preferences panel and generated pages checked against WCAG 2.2 AA.
The banner is the first keyboard stop, Escape never decides for the visitor, the focus goes back where it was when the panel closes.
A warning in the settings when the chosen colours are hard to read.

The interface and the generated texts are ready for translation; translations are delivered through translate.wordpress.org.

Please note

The plugin gives you the tools and proposes prudent texts, but it is not legal advice and using it does not by itself make a site compliant. You remain responsible for the content of your policies; for health data, minors, profiling and other delicate cases, ask a lawyer.

External services

The plugin does not contact any external service on its own. The services below are used only if the administrator connects them in the Integrations tab, and only after the visitor has given consent to the matching category (with one exception, described under Google).

Google Analytics 4 and Google Tag Manager (Google Ireland Limited / Google LLC)

Used to measure visits (Analytics) or to load the tags of your container (Tag Manager), when you enter a measurement ID or a container ID. The script is loaded from www.googletagmanager.com after the visitor consents; from that moment the browser of the visitor sends to Google the IP address, the address of the page, the identifiers stored in the Google cookies and the consent state. If you turn on the advanced Consent Mode, the Google library is loaded on every page before the choice, with all storage denied, and sends cookieless signals to Google.

Meta Pixel (Meta Platforms Ireland Limited)

Used to measure and build audiences for advertising, when you enter a Pixel ID. The script is loaded from connect.facebook.net only after the visitor consents to marketing; from that moment the browser of the visitor sends to Meta the IP address, the address of the page, the Pixel ID and the identifiers stored in the Meta cookies.

The cookie scan only requests pages of your own site.

Gambar conto

The banner on the site: Reject and Accept all have the same weight.

The choice by category, opened with Customize. — The banner on the site: Reject and Accept all have the same weight.

Pemasangan

In WordPress go to Plugins Add New, search for “Lobbit Cookie Consent”, install and activate. Or upload the zip from Plugins Add New Upload Plugin.
Open the Cookie Consent menu.
In the Controller tab enter the data of the data controller.
In the Integrations tab connect the services you use, then run the scan in the Cookies tab.
Create the Cookie Policy and the Privacy Policy pages from their tabs.

Moving from another site with this plugin? Import its export file from the Tools tab.

FAQ

Does the banner block scripts before consent?: It blocks the services connected in the Integrations tab, the custom scripts entered there and every script marked with the data-custcc-category attribute. Scripts added by other plugins must be marked, or their handle added with the custcc_blocked_handles filter.
My site only uses technical cookies. Do I need the banner?: No. Turn the banner off in the settings and keep the Cookie Policy page.
How does a visitor change the choice?: Through the floating icon or the link in the footer: one of the two is always active. You can also place the [custcc_preferences] shortcode or a link to #custcc-preferences anywhere.
What does the consent log store?: Date, action, categories, policy version, consent ID, the address of the page, the browser (user agent) and the IP address, truncated by default. No name and no email address. Rows are deleted automatically after the retention period you set.
Can theme and script developers read the choice?: Yes. The page receives a custcc:change event at every choice, and window.custcc.has( 'statistics' ) returns the current state.
How do I copy the configuration to another site?: In the Tools tab download the export file, then upload it in the Tools tab of the other site. The preview shows what would change; the linked pages stay the ones of each site. Run a scan afterwards to check the list of the cookies against the new site.
Why does the policy page show a title different from my other pages?: On the pages of the policies the plugin prints the title itself, in line with the text, and hides the one of the theme, because some themes print it outside the column of the content and do not let it be turned off. To change the title, rename the page. To leave the title to the theme, add add_filter( 'custcc_policy_own_title', '__return_false' );.
Does it work on multilingual sites (WPML, Polylang, TranslatePress, Weglot)?: Yes. The default texts of the banner and the generated policies follow the language of the page: leave the text fields of the Banner tab empty and there is nothing to translate. With WPML and Polylang the texts you type in the settings (banner texts, name and address of the controller, free texts of the Privacy Policy, purpose and provider of the cookies edited by hand) are listed in the wpml-config.xml file of the plugin and appear in String Translation (WPML) or in the string translations of Polylang after the first save. Translate the Cookie Policy and the Privacy Policy pages as you do with any other page, keeping the block in the translation: the banner, the links between the two policies and the title of the page follow the language of the visitor. TranslatePress, Weglot and similar services translate the finished page and need nothing. For other systems the custcc_page_id and custcc_text filters are available.
Does it work with page cache plugins?: Yes. The banner is the same for every visitor and decides in the browser whether to show itself, so the pages can be cached. When you save the settings the plugin clears the page cache of LiteSpeed Cache, WP Super Cache, Cache Enabler, W3 Total Cache, WP Rocket, WP Fastest Cache, Breeze, Hummingbird, WP-Optimize, SiteGround Speed Optimizer and Nginx Helper, and the cache of the Kinsta and WP Engine hosts, so the visitors see the new texts and the new policy version at once. For another cache, of the hosting, of a CDN or of another plugin, hook its purge to the custcc_page_cache_purge action, which fires at every purge; without code, clear it by hand after changing the settings. To keep the plugin from clearing the cache, add add_filter( 'custcc_purge_page_cache', '__return_false' );.
Is the plugin legal advice?: No. The texts are a prudent starting point. You remain responsible for your policies.

Mācā ulang

There are no reviews for this plugin.

Contributors & Developers

“Lobbit Cookie Consent” is open source software. The following people have contributed to this plugin.

Antonio Morlino

Translate “Lobbit Cookie Consent” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Caathetan Owahan

1.8

Privacy Policy: new “Other data” field for every activity (contact form, quotes, orders and the others), for the data a form asks that is not in the list, such as the city. The items are added to the data listed in the policy, can be exported and imported, and can be translated with WPML and Polylang.

1.7

New choice in the Consent log tab for what happens when the plugin is deleted: keep everything (the default), keep only the consent log, or delete everything. The old “keep the consent log” box becomes “keep only the consent log” when it was ticked, “keep everything” otherwise.
When deleting the plugin would delete data, the Plugins screen asks before deactivating or deleting it, also with the bulk actions.
Banner tab: the icon settings are hidden when the link in the footer is chosen.

1.6

About tab: the “Ask for support” button opens the contact form of the developer already filled in with the site details (site address; plugin, WordPress and PHP versions; theme; language; number of active plugins), in Italian for an Italian dashboard and in English otherwise. Nothing is sent until the form is submitted. New Copy button for the same lines.

1.5

The banner offers only the categories the site uses (connected services, custom scripts, listed cookies, blocked scripts), and the default message names only those. New filter custcc_categories_in_use.
When a page written by hand is chosen in the Banner tab as Cookie Policy or Privacy Policy, the guided setup of that policy is turned off, with a notice that explains why and how to get it back.

1.4

Translations are loaded by WordPress from translate.wordpress.org; translation files are no longer shipped with the plugin.

1.3

Saving the settings clears the page cache of LiteSpeed Cache, WP Super Cache, Cache Enabler, W3 Total Cache, WP Rocket, WP Fastest Cache, Breeze, Hummingbird, WP-Optimize, SiteGround Speed Optimizer and Nginx Helper, and the cache of the Kinsta and WP Engine hosts, so the cached pages show the new banner texts and policy version at once. A notice says which cache was cleared. New filter custcc_purge_page_cache and new action custcc_page_cache_purge for any other cache.

1.2

Multilingual sites: with WPML and Polylang the texts typed in the settings can be translated through their string translation (wpml-config.xml), and the banner, the links between the two policies and the title of the policy pages follow the language of the visitor. New filters custcc_page_id and custcc_text for other systems.

1.1

The generated Cookie Policy and Privacy Policy keep the width and the side margins of the site also in themes made for page builders, where the page content is as wide as the window. New filter custcc_policy_width.
Guided path for both policies (Cookie Policy: controller, cookies, page); once the page exists the tab shows view, edit and “Repeat the guided setup”, which puts the generated text back into the same page.
The title of the policy pages is printed by the plugin in line with the text; the one of the theme is hidden, also when the theme cannot turn it off. New filter custcc_policy_own_title.
Space above and below the policy pages, for desktop and phones, set in the Cookie Policy and Privacy Policy tabs.

1.0

Tools tab: export and import of the configuration, with a preview of the changes.
Accessibility review (WCAG 2.2 AA): Escape no longer counts as a refusal, focus handling, no faded texts, contrast warning for the banner colours, keyboard-scrollable policy tables.

0.4

Privacy Policy generated through five steps of questions, with its page, block and shortcode.
Controller tab shared by the Cookie Policy and the Privacy Policy.
Links between the two policies and in the banner.

0.3

Cookie catalog and scan, table of the cookies.
Cookie Policy page with automatic policy version.
About tab.

0.2

Integrations: Google Analytics 4 with Consent Mode v2, Google Tag Manager, Meta Pixel, custom scripts by category.
Floating icon or footer link to reopen the preferences.

0.1

Banner, consent cookie and consent log.

Katrangan

External services

Gambar conto

Pemasangan

FAQ

Does the banner block scripts before consent?

My site only uses technical cookies. Do I need the banner?

How does a visitor change the choice?

What does the consent log store?

Can theme and script developers read the choice?

How do I copy the configuration to another site?

Why does the policy page show a title different from my other pages?

Does it work on multilingual sites (WPML, Polylang, TranslatePress, Weglot)?

Does it work with page cache plugins?

Is the plugin legal advice?

Mācā ulang

Contributors & Developers

Interested in development?

Caathetan Owahan

1.8

1.7

1.6

1.5

1.4

1.3

1.2

1.1

1.0

0.4

0.3

0.2

0.1

Meta

Peringkat

Kontributor

Sokong