Cookies Revolution: setup and help

Follow the steps in Quick start.

If mprcookiebanner is already installed and enabled, disable or uninstall it before installing Cookies Revolution. The installer rejects installation while that other module is active.

Open Cookies Revolution > Design and set Blocking Mode before configuring individual rules.

In Settings > Configuration > General, Require a cookie choice before using the page defaults to off. Turn it on to block background clicks, keyboard focus and scrolling until the visitor accepts, rejects or saves preferences. It hides the banner close button. It does not itself change the script engine or Consent Mode settings. Hard block always requires a choice.

Keep cart, login, payment and security scripts outside optional blocking rules. Add or tighten rules only after checking the corresponding storefront flow.

Open Cookies Revolution > Settings > Configuration. The English field labels and fresh-install defaults are:

General

Re-consent after now uses the decision timestamp. A missing, invalid or future timestamp does not satisfy a configured age check. The consent version is an internal eight-character hash covering active categories, registered storage entries, rules, services, Consent Mode ownership and relevant integration bindings. It is generated by the module, not entered manually.

Google Consent Mode

Default Google signals deny optional storage and grant security_storage. Updates follow the validated category and service mappings. Google consent signals do not by themselves replace script blocking rules.

Consent Logging

Enable Consent Logging defaults to on. Log Retention defaults to 365 days. Use Purge old consent logs to remove entries older than that retention period. Do not assume that entering a retention number schedules automatic purging.

Open Consent Log to review saved decisions or export CSV. Records include visitor, IP and user-agent hashes, category/service choices, consent version, source and date. CSV also includes a country_code column, which stays empty.

Cookie Policy Page

Auto-Update CMS Page defaults to on. Policy content requires manual updates regardless of this setting. After changing the catalog, use Create cookie policy page or Update cookie policy page manually.

Custom Policy URL (overrides CMS) is empty by default and is multilingual. Enter your own policy URL to replace the generated page link. The generated CMS page ID starts at 0 and is stored internally when you create it.

Legal pages readable before a choice is empty by default. Enter comma-separated CMS page IDs for other pages that should remain readable without the consent wall. The policy page is handled as a legal-page exception too.

Vendor integrations

Without the corresponding consent, the adapter withholds visitor identification and email pickup. Search and recommendations remain available; anonymous page views can still reach Clerk. A selected service must be active, belong to this shop and match the category selected for that purpose.

Advanced

Legacy default consent override defaults to denied. Its choices retain legacy opt-in/opt-out labels, but current Hard and Soft modes deny optional categories by default. No block releases scripts while Google signals still require a validated decision. Use Blocking Mode as the primary control.

Script blocking engine defaults to on. Hard block forces it on; Soft block uses its stored value; No block forces it off.

Before generating the policy, review the active category descriptions and the registered cookie names, providers, purposes and durations in Cookie Categories and Cookies. The generator uses this inventory to build a table for each active category.

Use Create cookie policy page in the settings form, then inspect the generated CMS page in each shop language. The generator creates a content entry for every language, using that language's category and cookie text; its introductory text and table headings are fixed English strings in this version. Review and edit the resulting wording before relying on it.

After inventory changes, use Update cookie policy page manually. This replaces generated content across the page's languages and only updates the page recorded as created by this module. A separately chosen shop policy page is not overwritten by this action.

Cookie Categories

Open Cookie Categories. Installation adds Strictly Necessary (necessary), Functional (functional), Analytics & Performance (analytics) and Marketing & Advertising (marketing). Necessary is required. All four start active; optional categories are switchable.

Use Name, Description, System Name, Required (cannot be disabled), Active and Icon. Translate the visitor text. Example icons are shield, settings, chart and megaphone.

The GCM: ... switches map categories to ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage and security_storage. The installed mappings put security in Necessary, functionality in Functional, analytics in Analytics, and advertising/personalization in Marketing. Change mappings to match the actual scripts and purposes you use.

Services

Open Services when visitors need to choose a service separately within an optional category. Enter Name, Description, System Name, Provider, Category and Active. A service belongs to an optional category; its system name cannot be changed after creation.

Use Google Consent Mode types it owns to assign types separately to the service. A type can have only one service owner and must also be mapped by that service's category.

Assign related rules and registered cookies to the service. Before moving, deactivating or deleting a service in use, choose Its rules and cookies to reassign them. If Clerk.io uses the service, change the vendor binding first.

Cookies

Open Cookies to review installed common PrestaShop, Google, Facebook, DoubleClick and Bing entries, then add the actual storage used by your shop.

Installed wildcard defaults have their pattern flag enabled. Registered entries describe storage and allow cleanup matching; adding a cookie to the list alone does not block the script that creates it.

Open Script Blocking and add a rule with Category, optional Service, Rule Type, Pattern (Regex), Description, Excluded controllers and Active. The available types match external script URLs, inline script content or iframe URLs.

For an analytics script URL:

Category: Analytics & Performance
Rule Type: URL Pattern (matches script src)
Pattern (Regex): googletagmanager\.com/gtag/js
Description: Google gtag.js
Active: Yes

For inline marketing code:

Category: Marketing & Advertising
Rule Type: Script Content (matches inline code)
Pattern (Regex): fbq\s*\(
Description: Inline Facebook Pixel
Active: Yes

The installed rules include common Google, Clarity, Hotjar, Meta, TikTok, Bing, LinkedIn and chat patterns. Check them against your actual tags. Use Excluded controllers when a rule must not apply on particular controllers, then verify those pages separately.

Matching scripts are held inert until their category or service is allowed. The rewriting uses attributes such as data-cookiecategory, data-original-src and an inert script type. Client-side guards also handle matching scripts added later. These mechanisms cannot reverse code that has already executed.

Open Cookie Scanner, run a scan and categorize pending cookies. Automatic Cookie Scanning is installed on with a 24-hour Scan Interval. The automatic scan is triggered from admin page loads when due. Use the scanner screen to manage scans; Configuration has no Scanner tab.

The scanner uses HTTP requests and detects Set-Cookie headers plus simple literal document.cookie assignments in returned HTML. It does not execute a browser session. Review cookies created after interaction, after consent or inside third-party code manually. The PHP cURL extension is needed for those scan requests.

Open Design and save your layout, visitor text and display choices.

Layout and colors

Action buttons now use the shop theme's primary, secondary and link button styles. The earlier individual Accept/Reject/Customize button color controls and Button Border Color are retired.

Visitor text

Edit each language. The English defaults are:

• Banner Title. Multilingual banner heading; default: We respect your privacy.
• Banner Message. Multilingual banner paragraph; default: We use cookies to enhance your browsing experience, serve personalized content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.
• Accept Button. Multilingual accept-all button text; default: Accept All.
• Reject Button. Multilingual reject-all button text; default: Reject All.
• Customize Button. Multilingual preferences button text; default: Customize.
• Preferences Title. Multilingual preferences panel title; default: Cookie Preferences.
• Preferences Description. Multilingual preferences explanation; default: Choose which cookies you want to allow. You can change these settings at any time. However, blocking some types of cookies may impact your experience of the site.
• Save Button. Multilingual save-preferences button text; default: Save Preferences.
• Accept All (in prefs). Multilingual accept-all button text inside preferences; default: Accept All.
• Floating Button Label. Multilingual label and tooltip for the floating button; default: Cookie Settings.
• Policy Link Text. Multilingual policy link label; default: Cookie Policy.

Dimensions and interaction

Test with a fresh browser profile, then test as a returning visitor. Check all three decision paths: Accept All, Reject All and saving selected preferences. Confirm optional requests are blocked before consent under your chosen mode and rules, and allowed after the relevant category/service is enabled. Check cart, checkout and login at each stage.

The browser uses mprcr_consent, mprcr_version and additional timestamp/service state. A category cookie can look like:

mprcr_consent=necessary:1|functional:0|analytics:1|marketing:0
mprcr_version=1a2b3c4d

Use the public API rather than editing those cookies by hand:

if (window.MPRCR && window.MPRCR.isGranted('analytics')) {
  loadAnalyticsCode();
}
document.addEventListener('mprcr:consent', function (event) {
  if (event.detail && event.detail.analytics) {
    loadAnalyticsCode();
  }
});

Implement loadAnalyticsCode() in your integration and make it idempotent so repeated consent events do not load it twice. Visitors can reopen preferences through the floating button, the account Cookie Settings link or a custom link calling window.MPRCR.showPreferences().

For custom markup, call the API from your own click handler after preventing the link's default navigation. You can also use these CSS hooks in Custom CSS:

.mprcr-banner__inner { max-width: 980px; margin: 0 auto; }
.mprcr-category__desc { line-height: 1.6; }
.mprcr-floating { box-shadow: 0 4px 14px rgba(0,0,0,.2); }

• If a tag runs before a decision, check Blocking Mode, Script blocking engine, the rule pattern, Active, category/service assignment and excluded controllers. A cookie catalog entry alone is insufficient.
• If a store function stops, review rules that match essential scripts and test a narrower pattern.
• If a returning visitor sees the banner again, check the contract version, Re-consent after and browser cookie persistence.
• If a revoked tag leaves cookies, confirm those names and storage types are registered. Cleanup attempts cannot remove inaccessible HTTP-only or third-party storage or undo executed code.
• If generated policy content is stale, run Update cookie policy page manually. Check Custom Policy URL if the wrong policy opens.
• If consent log export has blank country values, that matches the current logger. If logs are absent, check Enable Consent Logging and the browser consent-save request.
• If cached pages show old categories or design, clear the shop and page caches and run the module Integrity checks. Retest in a fresh browser context.

Use Enable Module or Module Manager disable to stop output while retaining configuration. Back up consent records and your generated policy content before uninstalling. Uninstall removes module configuration, admin pages and declared schema, and calls deletion of the generated policy page. Review any custom policy URL separately. Update custom theme links that call the module API after removal.