Cookie consent for PrestaShop 1.7 and 8

GDPR cookie consent for PrestaShop, installed as a native module. Consent Mode v2, GTM and pixels included. No pageview limits, unlimited subdomains under one licence.

or see all twelve platforms

Why PrestaShop sites need consent that actually blocks

PrestaShop runs serious e-commerce, often across several country stores and language versions. That combination — real traffic, multiple shops, marketing pixels on every product page — is exactly where consent tools priced per pageview become expensive fastest.

Installing on PrestaShop

Upload the module

Back office → Modules → Module Manager → Upload a module. PrestaShop usually enables it straight after upload.

Open the setup screen

It has already read your database settings from app/config/parameters.php — you just configure the banner.

Clear the cache

Advanced Parameters → Performance. Realistic time: 5 to 10 minutes.

What’s specific to PrestaShop

Two things matter here. First, the cache. PrestaShop caches aggressively, and a freshly installed module frequently appears to do nothing until you clear it under Advanced Parameters → Performance. This is the single most common reason people think a module failed on PrestaShop — so our guide tells you to do it before you start doubting the installation.

Second, the version split. PrestaShop 1.7 and 8 keep database credentials in app/config/parameters.php, while older 1.6 installations use config/settings.inc.php. Cookie Craft reads both, so the same package works across versions without you looking anything up.

Included on PrestaShop, not upsold

No feature is held back for a higher tier. One plan, everything in it.

Google Consent Mode v2

The four signals GA4 and Google Ads need to run properly in the EEA — analytics_storage, ad_storage, ad_user_data, ad_personalization — set from your visitor’s real choice.

GTM, Meta & TikTok

Google Tag Manager, Meta Pixel and TikTok Pixel get base placement and consent-aware loading — no snippets pasted into your PrestaShop templates, no second plugin to gate them. Your tracking plan still defines the events and conversions.

One licence, one root domain

fr.example.com and de.example.com are subdomains of one root and are covered by a single licence; example.fr is a different root domain. Structuring country stores as subdomains is worth considering on licence cost alone.

A guide for your exact site

Your install guide is generated with your real PrestaShop paths already filled in, in twelve languages — no example.com placeholders to translate into your own setup.

Why it matters here

PrestaShop shops tend to have high page counts and seasonal traffic spikes. A consent tool billed by pageviews charges you most in exactly the month your campaign works. Cookie Craft’s price does not move.

The pixels matter more here than on a content site: Meta and TikTok conversion tracking drive real revenue, and both need to be blocked before consent and released after it — cleanly, without double-firing. Cookie Craft handles the gating, and warns you if it detects a pixel implemented twice.

What it does — and what it doesn’t

Cookie Craft does not scan your PrestaShop site to discover cookies automatically, and it does not write your privacy policy for you. It gives you the mechanism: a banner your visitors actually interact with, real blocking of the scripts you configure, and correct Consent Mode v2 signals to Google. What you declare in it is up to you.

Consent for PrestaShop, done properly.

Self-hosted, first-party, and everything included — €25/month or €240/year per root domain.