Cookie scanner and blocker in depth
How the scan works
The scan opens about 14 pages: the home page, two categories, two products, the cart, the contact page, two CMS pages, the search results, the login and registration pages, the "page not found" page and the store locator, plus the pages you add. They load in your browser as a visitor who accepted everything, with the consent signals of Google Consent Mode and Microsoft Ads granted, so tags that wait for consent load too.
The scan records scripts, frames, pixels, cookies and storage keys. Cookies a page cannot see (HttpOnly or set by other domains) are inferred from the services found. When a page does not report back, the module fetches it on the server and analyses its HTML.
The findings are grouped into services with a bundled dictionary of 45 services, such as Google Analytics, Meta Pixel, Hotjar and YouTube. Its tracker data is derived from the Open Cookie Database (Apache-2.0).
Categories
| Category | Use it for |
|---|---|
| Necessary | What the shop cannot work without: session, cart, security, payment. Never blocked. |
| Preferences | Services that remember the visitor's choices. |
| Statistics | Analytics and measurement. |
| Marketing | Advertising, retargeting and social pixels. |
| Unclassified | Not classified yet. Give every service a real category. |
Approving and editing services
Each row of Review shows the service, its provider, category and blocking state, and where it was found; Details lists the evidence. A ! icon means "May break the page when blocked"; a G marks a Google tag.
The ⋯ menu holds:
- Edit texts and settings: the Name, Description and Expiry shown in the pop-up, one tab per language. Under Advanced, the script, inline script and frame patterns and the hosts decide what is held back. Untick Hold back until consent for a service that breaks the shop when blocked.
- Ignore: out of the pop-up, never blocked. It can be restored.
- Delete: removed from the pop-up. The next scan proposes it again if it is still there.
Blocking states
| State | Meaning |
|---|---|
| Blocked once approved | New, not approved yet. |
| Will be blocked until consent | Approved; blocking is still off. |
| Blocked until consent | Held back until the visitor accepts its category. |
| Not blocked (necessary) | In Necessary, always allowed. |
| Handled by Consent Mode | Left to Google or Microsoft consent mode. |
| Banner only | No pattern: listed in the pop-up, its cookies deleted on refusal. |
| Not blocked (your choice) | Hold back until consent is off. |
| Not blocked (ignored) | Ignored. |
Blocking and strict mode
With blocking on, the module rewrites each page before sending it and defers the scripts, frames and pixels of approved services outside Necessary. When the visitor accepts a category, its services start without a reload. A blocked video or map shows a placeholder with a Manage cookies button.
When a visitor withdraws consent, the refused services' cookies that the page can reach are deleted at once; the others expire on their own.
Strict mode (Go live > Advanced settings, off by default) also catches trackers that other scripts add later. It may break some scripts, and it does not cover fetch or beacon requests, tags hard-coded above the module's script, or scripts delayed by a performance module. Use it only when a tracker still loads with blocking on, and test it in the preview first.
The Consent Mode exemption
With Google Consent mode V2 enabled (off by default) and Leave Google tags to Consent Mode on (Go live > Advanced settings, the default), Google Tag Manager, Google Analytics and Google Ads load for every visitor, and Consent Mode tells them what they may store. They show as Handled by Consent Mode. Turn the setting off to hold them back like other services.
The Microsoft UET tag is left to Microsoft Ads consent mode the same way, while that mode is on with a UET tag ID.
Trackers you create yourself
Items that match no known service are listed under Unclassified — not blocked, optional. To handle one, click Create tracker, pick the Category, enter the Name shown in the banner and the Provider, and click Create tracker.
A tracker created from a host blocks the scripts and frames of that host once blocking is on. One created from a cookie is Banner only: it is listed and its cookies are deleted on refusal, but its script is not blocked. Storage keys and shared library hosts such as jsDelivr or cdnjs cannot be blocked. For a code the scan never sees, use a custom script (see Custom scripts).
Scanning again
Scan again after you add or remove a tracking module, change the theme, and every few months. New services appear under New from the scan; approved ones keep their settings. A new scan clears the checks of Check the shop.
With Notify me about unclassified items on (Go live > Advanced settings, the default), GDPR Config shows a notice after a scan that leaves unclassified items, with a Review them link.
Custom scripts
Custom scripts are tracking codes and styles you add yourself, for example a snippet you would otherwise paste into your theme. Each is listed in the pop-up under its category and loads only for visitors who accept it.
Open Modules > GDPR Custom scripts.
Click a status to switch a script on or off; drag a row by its Position to change the order in the pop-up. To add a script, click Add new, fill in the form and click Save.
| Field | What to enter |
|---|---|
| Internal name | A name for the back office. |
| Active | Off keeps the script out of the shop. |
| Activate Consent mode V2 | The script always loads and follows the Google consent signals. For Google Analytics and Tag Manager codes, with Google consent mode V2 enabled. |
| Keep inline js scripts | Keeps the inline code in place when PrestaShop optimises JavaScript. |
| Expiry, Provider, Frontend name, Description | The pop-up texts, in each language. |
| External CSS, External JS | The address of a file to load. |
| Inline CSS, Inline JS | Code, without the <style> or <script> tags. |
| Script category | The category visitors accept. Necessary always loads. |
The script is added to the pages a visitor opens after accepting it. To start it on the same page, turn on the Reload settings of GDPR Pop-up configuration.