Your Cookie Banner Is a Prop. Let's Fix That.
Clicks past. Blocks nothing. Tracks everyone anyway. If that's your idea of GDPR compliance, a regulator has a very different one — and they don't grade on effort.
A Consent Banner That Actually Consents
Loads first. Blocks before it should. Tells every other tracking plugin in your store exactly what your visitor said — automatically.
First In Line, Every Time
Your banner loads before every other script on the page — not somewhere in the middle, hoping tracking hasn't already fired. Blocking only works if it actually goes first.
One Field. Done.
Paste your account ID, hit save. No developer invoice for "cookie compliance." No excuse left standing that involves the word "later."
Automatic Blocking
Cookies get detected and held back before consent, with zero manual script tagging. Or switch to Manual mode if you'd rather drive stick yourself.
One Banner, Every Pixel Obeys
Your visitor answers once. Every other tracking plugin already running your store reads that same answer automatically — no separate consent logic to wire per integration.
Speaks The Visitor's Language
Lock the banner to one language, or let it auto-detect and greet every visitor correctly. Nobody wonders if your store even operates where they're standing.
Silent Until You Finish The Job
Skip the setup and it simply does nothing — no half-broken banner flickering on your homepage as evidence you started a project and walked away.
One Banner, Every Pixel Falls In Line
Right now, every tracking plugin on your store is probably running its own half-finished consent check — three separate chances to get it wrong instead of one chance to get it right. This collapses all of it into a single decision your visitor makes exactly once.
- Visitor answers the consent banner one time
- Every other tracking plugin already installed reads that same answer
- Zero per-integration consent wiring left for you to forget
Blocking That Actually Blocks
A consent banner that loads after your tracking scripts already fired isn't consent — it's a receipt for something that already happened. This one forces its banner script to the front of the line so blocking gets a real chance to matter.
- Banner script loads ahead of every other script on the page
- Automatic mode detects and blocks cookies with zero manual tagging
- Manual mode available for surgical, hands-on control
Built For Store Owners, Not Privacy Consultants
Four admin fields. No legal document to draft, no separate compliance dashboard to learn. Configure it once and it stays invisible until you need to change something — the way infrastructure is supposed to behave.
- One-field account connection, no developer required
- Stays out of your own admin screens entirely
- Debug logging on demand when you actually need to look under the hood
Real-World Use Cases
Stop Pretending Your Banner Works.
Every day it stays fake is a day you're choosing exposure over a five-minute fix.
Translated In The Following Languages
Arabic Unitag (ar-AA), Chinese, Traditional (zh-TW), Danish (da-DK), Dutch (nl-NL), English (en-GB), English, USA (en-US), Finnish (fi-FI), French (fr-FR), German (de-DE), Greek (el-GR), Hebrew (he-IL), Italian (it-IT), Japanese (ja-JP), Norwegian Bokmål (nb-NO), Persian Farsi (fa-IR), Polish (pl-PL), Portuguese, Brazil (pt-BR), Portuguese, Portugal (pt-PT), Russian (ru-RU), Spanish (es-ES), Swedish (sv-SE), Turkish (tr-TR)
License Information
An active license entitles you to updates, downloads, and support for the duration of the license period. You may continue using this plugin indefinitely without an active license; however, support, updates, and downloads will not be available while your license is inactive.
- Developer J2Commerce
- Extension Type Apps
- J2Commerce Version 6.x
- Joomla Version 6.x
Arabic Unitag
Chinese, Traditional
Danish
Dutch
English
English, USA
Finnish
French
German
Greek
Hebrew
Italian
Japanese
Norwegian Bokmål
Persian Farsi
Polish
Portuguese, Brazil
Portuguese, Portugal
Russian
Spanish
Swedish
TurkishNew Feature Cookiebot uc.js consent-banner script injected as the literal first element in , enabling Automatic Cookie Blocking
New Feature Blocking Mode plugin parameter: Auto (data-blockingmode) or Manual (async)
New Feature Culture plugin parameter to force the Cookiebot banner language
New Feature CBID plugin parameter with hint format guidance
New Feature Debug plugin parameter for verbose logging of skip conditions
Improvement Frontend-only, disabled automatically when no CBID is configured
Update Requires Joomla 6.x, J2Commerce 6.x, and a Cookiebot account (CBID)
You may also be interested in these products
Stay Updated
Subscribe for free and be the first to know about the latest features, updates, and new additions.