Collect cookie consent on PrestaShop without theme edits, with Google Consent Mode v2
Lightweight Cookie Banner asks visitors for their cookie choice in your shop's own colours, passes that choice to Google and Microsoft advertising, and remembers it for the next visit. Setup is one screen: wording, policy link, position and colours.
A notice alone does not meet the obligation: optional cookies and the features behind them have to wait for consent. The module holds them back until the visitor agrees to their purpose and keeps a record of each decision.
You pick from eight positions and three button layouts, and every shop and language gets its own text, ready-made in English, German, French, Polish, Italian and Spanish. A returning visitor's saved choice applies before any measurement starts.
Your consent signals stay dependable, and the banner looks like part of the shop.
What changes in the shop after installation?
Lightweight Cookie Banner adds a complete cookie-choice layer to a PrestaShop store: it asks for a decision, applies it to optional activity, passes the answer to measurement systems and keeps evidence of what the visitor selected.
- A decision with consequences: non-essential activity follows the selected purposes.
- A notice that belongs to the shop: theme colours, eight positions and three action layouts shape its appearance.
- A precise visitor choice: accept all, refuse all and separate purpose preferences remain available.
- Timely advertising signals: Google and Microsoft receive the starting state and every later change.
- The right context: wording and settings follow each language, shop and return visit.
- Merchant-owned evidence: consent history and diagnostics stay under shop control.
Useful defaults make the first launch short, while purpose rules, appearance, language, shop context, memory period and policy details provide the depth needed for a larger catalogue.
Where does the notice fit into the storefront?
During installation the module reads the active theme and starts with a matching palette. Background, text and action colours remain editable, so the first result is immediate and the final result still follows the merchant's design decisions.
Eight positions include full-width bars at the top and bottom, all four corners, a floating bottom panel and a centred dialog with a backdrop. Actions appear side by side, in a vertical stack or in a compact arrangement. The centred presentation manages focus and keyboard navigation, keeping the choice clear for visitors using assistive technology.
What exactly does the visitor choose?
The first level offers three plain routes: accept everything, refuse everything or customize the decision. The preferences panel separates advertising, analytics and personalisation, explains each purpose and links to the shop's policy without turning the purchase path into a long form.
Non-essential cookies, modules and page features remain inactive until their purpose has permission. Closing the centred dialog never invents consent, and the visitor reopens the same preferences later to withdraw or replace an earlier choice.
How do advertising and analytics receive the decision?
The module places the saved or configured starting state before connected advertising and measurement begin. Google Consent Mode v2 receives the status for advertising storage, advertising data, personalisation and analytics, while Microsoft advertising receives the matching choice.
Accepting, refusing or changing one purpose sends an immediate update. A returning visitor begins with the validated saved decision rather than a temporary global default, so campaign reporting follows what that person actually selected from the first moment of the visit.
What happens in every language, shop and later visit?
English, German, French, Polish, Italian and Spanish begin with native notice text, actions and purpose explanations. Every field remains editable, and a defined fallback keeps a newly added language from producing an empty or mixed-language banner.
Each shop in a multistore installation has its own policy link, wording, colours, purposes and memory period, with inheritance where one common setup is appropriate. The saved answer hides repeated prompts, while a permanent preferences link gives the visitor a direct route to review or change it.
What stays under the merchant's control?
The storefront contacts no hosted consent provider merely to display the notice or remember an answer. The shop stores the selected purposes without attaching them to a customer profile, while the proof history records the decision, time, language, shop and policy revision for review and export.
A built-in review identifies missing text, action labels, colours, memory periods and inconsistent consent settings. Only one mypresta.rocks consent product owns the task at a time, preventing duplicate notices and conflicting signals. The result combines a one-screen start with the operational control required after launch.
-
Referencemprcookiebanner
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront-office
-
GDPR RelevantYes
-
Business GoalLegal & Compliance
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageManage Store
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Lightweight Cookie Banner adds a clear accept/deny cookie notice to your PrestaShop store, saves the visitor’s choice in a first-party cookie, and can update Google Consent Mode v2 without loading third-party scripts.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1343
questions
9
categories
v1.2.152026-05-27
- AddedCertify cookie banner consent settings
- Addedcomplete FR/DE/ES/IT/PL translations
Loading full changelog...
Works Well With Lightweight Cookie Banner
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Governance
If you run Facebook Pixel, your store sends browser events and optional server-side purchase data to Meta Ads, which means scripts are loading and reading shopper activity. Under consent rules you need a way to hold or release that behaviour based on the visitor's choice.
Lightweight Cookie Banner provides that as a separate consent layer: a practical accept-or-deny notice with configurable text and design, storing the decision in a first-party cookie. It blocks matching scripts before consent and reactivates them once it is granted, recording the visitor's decision. It is a lean banner with separate advertising, analytics and personalisation preferences.
Running both, you keep your Meta measurement while giving shoppers a clear consent choice that governs script behaviour. The banner holds the Meta Pixel until the visitor accepts, then reactivates it, so tracking fires according to the recorded accept-or-deny decision rather than on every session by default.
Governance
With Google Analytics GA4 active, your store sends ecommerce activity such as product views, cart events and purchases to Google, so analytics scripts run on shopper sessions. Consent rules mean you need a clear mechanism to record and respect each visitor's choice about that tracking.
Lightweight Cookie Banner is that mechanism, kept deliberately simple: an accept-or-deny notice with configurable text and design that stores the visitor’s consent choice locally and can pass the choice to Google Consent Mode.
Because GA4 is a Google target, the pairing fits cleanly: the banner can signal Consent Mode for your Google analytics while GA4 keeps measuring ecommerce behaviour. You get practical consent handling and useful analytics together, with separate advertising, analytics and personalisation preferences.
Governance
Hotjar on your store connects heatmaps and session recordings with real shopping context, which means a recording and analytics script loads on visitor sessions. That kind of behavioural capture is exactly what consent rules expect you to gate on the visitor's choice.
Lightweight Cookie Banner gives you a practical accept-or-deny notice with configurable text and design, storing the decision in a first-party cookie. It blocks matching scripts before consent and reactivates them once it is granted, recording the visitor's decision so you have a clear basis for whether scripts should run. It is a lean banner, not a full cookie scanner.
Used alongside each other, the banner handles the consent decision while Hotjar handles the behavioural insight once that decision allows it. The banner holds Hotjar's script until the visitor accepts and reactivates it afterwards, so recording runs on the recorded choice rather than loading unconditionally.
Bundle
Lightweight Cookie Banner gives your store a practical accept-or-deny consent notice with configurable text and design, storing the visitor decision in a first-party cookie. It blocks matching scripts before consent and reactivates them once it is granted, recording each decision. It is about consent, not about defending forms.
reCAPTCHA & hCaptcha Protection sits in a different problem space: it reduces and filters spam and bot submissions on contact, registration, login and newsletter forms using reCAPTCHA v2, v3 or hCaptcha. The two share no functionality and do not depend on each other.
They make sense together as part of a clean launch setup rather than as one feeding the other: the banner covers the consent requirement most stores face, and the captcha layer covers form abuse. Each is configured independently, and together they handle two of the common housekeeping needs of a public storefront.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
Who builds and maintains this module
Built and maintained by David Miller and mypresta.rocks. David has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.