A compliant cookie banner, in place as soon as it is installed

Install the module: the banner appears at the bottom of every page, with three buttons of the same size and the same colour, “Refuse all”, “Customise” and “Accept all”. Four categories (necessary, preferences, statistics, marketing) are ready in French, English and Arabic, none is ticked in advance. The first scan of the shop is done during the installation.

The visitor's choice is asked again after 6 months, as the CNIL recommends, and each time you change your cookie policy (an “Ask all visitors again” button). A discreet button lets visitors change their mind at any time.

A banner shown while Google Analytics is already running protects nothing. Here, the known trackers are neutralised in the page before it reaches the browser:

• by signature: the scripts, pixels and frames of Google Analytics, Google Ads, Google Tag Manager, Meta, Microsoft Advertising, Microsoft Clarity, Hotjar, Matomo, TikTok, Pinterest, LinkedIn, Snapchat, Criteo, YouTube, Vimeo and Google Maps stay inactive until their category is accepted, without touching the code of the other modules;
• by module: a module known to set trackers (Google Analytics, Facebook, Marketing with Google…) has its display and its scripts put on hold, then restored as soon as consent is given, without reloading;
• a blocked video or map shows a short message in its place.

The shop's cookies of a refused category are deleted in the browser.

The four signals ad_storage, analytics_storage, ad_user_data and ad_personalization are set to “denied” in a script placed at the top of the page, before any Google tag, then updated as soon as the visitor chooses (and from the top of the page for a visitor who has already chosen).

• Basic (default): Google tags only load after consent.
• Advanced: Google tags load at once and receive the refusal until consent.

The same choice is sent to Microsoft Advertising (UET consent mode) and to Microsoft Clarity. A test run in a real browser for each version checks the order: refusal before any gtag, then update after “Accept all” or “Refuse all”.

The module reads the files of your active modules and of your theme, and visits the home page, a category and a product page of your shop. What it finds is sorted by a database of more than 2,200 cookies: the Open Cookie Database (Apache 2.0 licence), completed with our PrestaShop data. An unknown cookie becomes “to validate” and stays refused as marketing until you decide; a classification you made by hand is never overwritten by a scan.

The scan runs again every week (native cron tasks module, or an address to give to your host) and on demand. The database is updated online: the file is signed by LNKBOOT and checked before use, and nothing is sent from your shop.

Every choice is written to the consent log: date, accepted categories, version of your policy, anonymous identifier of the browser and shortened IP. Nothing else. The log is read page by page, exported as CSV for an audit, and purged by itself after 12 months (adjustable).

The CMS page of your cookie policy receives the table of the shop's cookies by itself, by category, with a link that reopens the visitor's choices.

The server renders the same page for all visitors: the banner is always present and hidden, and the choice is read in the browser. A full-page cache therefore stays correct. The choice cookie is strictly validated on the server before it enters the log.

Figures measured on the delivered module, gzip-compressed (level 9). A single stylesheet, the one of the chosen display: 1.3 KB. A script in native JavaScript, loaded deferred: 3.2 KB. The Consent Mode script at the top of the page, inline: 0.4 KB. Less than 5 KB in all. No font added, no external resource. The classification database stays on the server: the shop loads nothing from it.

Three displays (bar at the bottom, box in a corner, centred window), a button colour whose text stays readable, a “Learn more” page. The names and descriptions of the categories can be changed in each language. Everything else is folded into “Advanced settings”. The live preview, on the right, shows the banner on desktop and mobile while you type.

Neutral markup (.lnkec, BEM), one stylesheet per display, template that the theme can override. Other scripts read the choice with window.lnkConsent.has('statistics') and the lnkconsent:change event. You can also declare a script yourself: type="text/plain" and data-lnkec="marketing". In Arabic, the banner reads from right to left without any setting.

Each version is verified by a real installation: PrestaShop 1.7.8 and 8.1 for the 1.1.N package, PrestaShop 9.0 for the 1.9.N package. The tests cover installation, display, the back office and uninstallation.