PrestaShop Cookie Banner: Consent Mode v2 Guide

A PrestaShop cookie banner is not just a notice on top of the storefront. In a real shop, a visitor may land on a product page from Google Shopping, add an item to the cart, move through checkout, pay on an external provider page and return to an order confirmation page. Consent has to follow that journey.

PrestaShop is modular by design. Themes, modules, hooks, Google Tag Manager, payment extensions, chat widgets and old template snippets can all add JavaScript at different moments. The practical question is not only whether the banner is visible, but whether optional cookies, localStorage entries and network requests wait for the visitor's choice.

This article is a practical implementation guide, not legal advice. CookiePilot can help install and connect consent management in PrestaShop, but each shop still needs configuration, an inventory, category mapping and real browser testing.

Consent Is Runtime Architecture

A visible banner is only one layer. Before optional tags run, the shop needs a default consent state. Necessary features such as session handling, cart, security and payment continuity can remain available, while analytics, advertising, embedded media, chat and remarketing usually need to follow the visitor's choice.

The sequence matters: set conservative defaults, load the CMP early, hold optional scripts, show the choice interface, then update tags after accept, reject or partial selection. If GA4, Google Ads, Meta Pixel or a heatmap tool sends requests before the default state exists, the implementation is not aligned with the banner text.

Use the local CookiePilot features page as a functional checklist, then verify the actual storefront. A PrestaShop shop is judged by browser behavior, not by an admin screenshot.

Build The Inventory

Start with a complete technical inventory. Include the active theme, child theme, modified .tpl files, header snippets, modules, checkout extensions, payment providers, delivery modules, analytics, ads, affiliate tags, product recommendations, reviews, newsletter popups, live chat, video embeds, fraud prevention, security tooling and customer service platforms.

Test more than the homepage. Review category pages, product pages, search, cart, checkout, login, account creation, contact forms, payment return and the order confirmation page. Some scripts only appear after a coupon, for logged-in customers or after a payment module receives a response. In multistore setups, repeat the inventory by domain, language, theme and shop context.

Classify each technology by purpose. A session cookie for a cart is different from a remarketing identifier. A fraud check may be operationally necessary in checkout, while a conversion pixel is usually optional. Do not rely on the module name alone; inspect what it stores and where it sends data.

Consent Mode v2

If the shop uses Google services, add Google Consent Mode v2 to the implementation plan. The four key signals are analytics_storage, ad_storage, ad_user_data and ad_personalization. For EEA visitors, optional purposes should normally start with cautious denied defaults before the relevant Google tags load.

After the CMP records a choice, it sends an update. If the visitor accepts analytics but not ads, analytics_storage may become granted while ad_storage, ad_user_data and ad_personalization remain denied. If the visitor later withdraws consent, the new state must be respected on reload and on later pages.

Consent Mode v2 does not replace consent, transparency or legal analysis. It is a Google signal layer. Other vendors still need script rules, tag triggers or their own consent APIs. For GTM details, use Consent Mode v2 with Google Tag Manager and Google's official Consent Mode documentation.

Setting Up CookiePilot

Begin with the local CookiePilot PrestaShop integration. The integration or module helps install and connect CookiePilot with the shop. Treat it as the starting point for consent management, not a promise that every theme override, module and custom tag is already categorized correctly.

Configure the domain, language, banner text, categories, vendor descriptions and privacy policy links. Map each inventory item to the right category, and make sure visitors can reopen preferences and withdraw consent later. If you are replacing another CMP, compare the workflow with the local Cookiebot alternative. For planning, check pricing, especially if you run multiple domains, staging stores or agency-managed shops.

Test in staging where possible. If staging is not available, use a clean browser profile, clear storage between scenarios and save evidence from cookies, localStorage, network requests and GTM preview.

Hooks, Modules And Theme Code

PrestaShop's official documentation on module hooks explains why a consent audit cannot stop at one header file. Modules can inject output through header, footer, product, cart, checkout and order confirmation hooks. A marketing script may be attached somewhere you do not expect.

Custom themes need the same attention. Check .tpl files, CMS blocks, tag manager snippets, module configuration fields and old agency code. If cache or performance modules bundle scripts, test the rendered page in the browser. Consent works only when the final HTML and network behavior match the stored preference.

Test Matrix

Scenario	What to verify
First visit	Optional cookies and requests do not start; Google defaults are denied.
Reject	Analytics, ads, chat and video remain held back by category.
Partial choice	Only the accepted category runs.
Accept	Allowed tags start once and Consent Mode receives an update.
Withdrawal	The new preference is stored and respected after reload.
Product page	Ecommerce events follow the same consent state.
Cart and checkout	Necessary purchasing functions work without optional tracking.
Payment return	Conversion tags do not bypass the CMP on the thank-you page.
Mobile	Banner and preferences remain usable without blocking purchase controls.
Logged-in customer	Account status does not override optional tag rules.
Multistore	Each domain, language and theme variation is checked.

Release Checklist

• Keep a dated inventory of modules, cookies, storage and network calls.
• Confirm local English banner text, categories and privacy links.
• Set denied defaults before optional Google tags.
• Test reject, accept, partial choice and withdrawal.
• Review PrestaShop hooks, theme files, module settings and GTM triggers.
• Record theme version, module versions, GTM container version and test results.
• Ensure a persistent preferences link exists in the footer or privacy area.
• Re-run the audit after new campaigns, modules, payment changes or theme updates.

For broader wording and category planning, compare the general GDPR cookie banner guide.

UK And EU Regulatory Context

For English-language European shops, useful official sources include the European Data Protection Board and the European Commission's GDPR information. The specific assessment depends on your market, visitors, vendors, purposes, contracts and technical implementation.

The safe operational posture is modest: say the CMP helps collect, store and respect choices. Avoid saying that a module makes the shop fully compliant. If the shop sells across borders, align the banner, privacy policy and vendor list with the countries you target.

FAQ

Is installing the PrestaShop module enough?

No. The module helps with installation and connection, but browser behavior across theme, modules, GTM and checkout still needs testing.

Can necessary cookies run without the same consent flow?

In practice, cookies for session, cart, security and payment may be necessary, but they should be documented and kept separate from analytics or marketing.

Does Consent Mode v2 make the shop compliant?

No. It sends technical signals to Google services. It does not replace consent, information duties or legal review.

Why test checkout separately?

Payment, fraud prevention and conversion measurement often appear only in checkout or after the payment return.

What is a partial choice?

The visitor may accept analytics but reject marketing. Your categories and tags must reflect that difference.

When should the audit be repeated?

After new modules, GTM changes, theme releases, campaigns, payment changes and new customer service tools.

Practical Next Step

Open the PrestaShop integration, build the inventory, then run the test matrix in a clean browser. If the flow is complex, send your module list, tags and checkout path through contact. Teams running several platforms can also compare the related guides for WooCommerce and Shopify.