These cookies are essential for the website to function properly. They enable core functionality such as security, shopping cart, and account access. You cannot disable these cookies.
These cookies enable enhanced functionality and personalization, such as remembering your language preference or region. If you do not allow these cookies, some features may not work properly.
These cookies help us understand how visitors interact with the website by collecting and reporting information anonymously. This helps us improve our website.
These cookies are used to deliver advertisements that are relevant to you based on your interests. They also help measure the effectiveness of advertising campaigns.
Microsoft Clarity connects your PrestaShop store to Microsoft's behaviour analytics and adds product, cart and order context to recordings. You enter a Project ID and switch tracking on to start.
Microsoft's service provides session recordings, heatmaps and signals for frustrating clicks or excessive scrolling. It is free, with no traffic limit stated by Microsoft; the purchase price covers the PrestaShop module, separately from Microsoft's services.
You switch eight shopping actions individually and add rules for selected clicks or pages. Consent changes take effect on the current page, staff visits stay out, and each shop keeps its own project. Reports identify abandoned carts and checkout exits.
A report links the affected cart or order to its recording, helping you investigate the journey behind a lost purchase.
Microsoft Clarity connects a PrestaShop store to Microsoft’s behaviour analytics and enriches recorded sessions with separately controlled shopping events, product context and order context.
Microsoft’s service records visits. The module adds the structure needed by a merchant: page view, product view, successful add to cart, successful add to wishlist, checkout start, search, registration and purchase are eight separate actions, each with its own switch.
Product names, identifiers and categories accompany product activity. Cart and purchase sessions carry value, currency, item count and transaction reference. You choose which actions enter Clarity, then add rules for a chosen click, an address fragment, a shop page or a named storefront action. Fixed context and details from the action travel with the rule, while once-only rules prevent repeated noise.
Microsoft Clarity shows the visit as a recording and summarises behaviour through click, scroll, attention and drop-off heatmaps. Its dashboard identifies dead clicks, repeated frustrated clicks and excessive scrolling, while live visitor views, filters and AI summaries shorten the route from a broad traffic number to the page element that needs work.
The service is free, and Microsoft states no traffic limit. The price displayed on this page covers the PrestaShop module and its commerce events, controls, diagnostics and reports. Microsoft Clarity and any optional Microsoft services remain separate from the module purchase.
The module provides the bridge between the two sides: Clarity shows how the visit unfolded, while shop actions and order context explain what that behaviour meant commercially.
You choose whether collection follows the supported MPR consent module and whether the current consent state is sent to Clarity. A grant starts collection on the current page, a withdrawal changes the state immediately and later module events stop without requiring a page reload.
Recognised back-office staff browsing the storefront never enters customer recordings. For returning shoppers, an optional pseudonymous identifier connects relevant sessions without sending a name, email address, postal address or telephone number. Its use remains subject to consent, and deletion or rotation breaks the link.
Tracking starts disabled, an invalid Project ID never activates it, and every privacy choice remains visible in the readiness panel. These controls support a deliberate privacy setup without pretending that software alone settles the merchant’s legal obligations.
The first launch needs one field, the Clarity Project ID, followed by the enable switch. The panel checks the identifier, collection state, consent guard and custom rules, and explains every missing or invalid setting before the merchant expects recordings to arrive.
In a multistore installation, each shop has its own Project ID, enabled state, consent policy and event selection, with explicit inheritance where several storefronts share a setup. Automatic context identifies the shop, language, customer group, currency and page type, so recordings from different brands or markets stay distinguishable.
The sales demo adds a live monitor for project status, consent, page context and every standard or custom action as it is sent. Setup remains short, while the same panel supports detailed rules when the catalogue, campaigns or storefront count grows.
The PrestaShop reporting screen groups abandoned carts, problematic orders and the checkout stage where each journey ended. Filters narrow the result by date, shop, language, customer group, product, cart value and stage, while a drill-down links the shop record to its relevant Clarity session.
Cart and order correlation separates a visitor who only browsed from one who entered checkout and stopped at delivery, payment or confirmation. The report preserves the commercial consequence alongside the behaviour evidence: value at risk, items involved and whether an order later appeared.
Exports support a recurring review with the store team, while privacy controls determine retention and the fields included. The merchant gets a short list of journeys worth investigating instead of an unstructured recording archive.
Be the first to share your experience with this product.
Microsoft Clarity for PrestaShop adds the official Clarity browser script to your store and enriches Clarity recordings with PrestaShop page, product, cart, order, currency and search context. It helps you find useful recordings faster while heatmaps and session replays stay inside Microsoft Clarity.
The module supports PrestaShop 1.6, 1.7, 8.x and 9.x. It adds the Microsoft Clarity script through the storefront header hook, so Clarity runs with its own asynchronous tracking code and your recordings and heatmaps are processed in your Microsoft Clarity account, not on your server. The module does not create extra database tables for tracking data.
You can keep back-office sessions out of Clarity. When "Exclude employee browsing" is enabled, which is the default, the module does not load the Clarity script while a logged-in employee is browsing the storefront, so your team's own visits are not recorded. Regular customer sessions are still tracked normally.
Add the Microsoft Clarity Project ID, enable tracking, save the module configuration, then verify the storefront script. The Project ID field accepts only 5 to 64 letters or numbers, so paste only the project id, not the whole Clarity script tag. The module's own help points merchants to clarity.microsoft.com > Settings > Overview.
https://www.clarity.ms/tag/PROJECT_ID.The header hook loads the Clarity script only when tracking can run: the module must be active, employee browsing can be excluded, and marketing consent must be present when the module is configured to respect an MPR consent module.
By default the module installs with tracking disabled and an empty project id, but most event switches are enabled once tracking is active. The code can send page view, product view, add-to-cart, wishlist, checkout start, search, purchase and signup events, plus page tags such as currency and page type. Purchase tracking is emitted on order confirmation and includes order-derived tags; signup is stored as a short-lived cookie flag during account creation and sent on the next matching header render.
Consent handling is tied to the MPR cookie modules when they are installed. With RESPECT_CONSENT enabled, Cookies Revolution is checked through the mprcr_consent marketing category, and Lightweight Cookie Banner is checked through mprcookie_consent. If neither module is active, the module treats consent as available. Custom events are supported too, but their JSON rules are validated: event names, selectors, URL/controller triggers and tag payloads must fit the module's limits before the admin controller accepts them.
Yes, the module can respect consent before tracking. It checks consent from mprcookiesrevolution or mprcookiebanner when available, can send a Clarity consent signal, and can block client-side tracking until marketing consent is granted for the PrestaShop storefront.
Yes, it can send PrestaShop ecommerce events and tags to Clarity. The module includes page view, product view, add to cart, checkout start, purchase, search, wishlist and signup events, and purchase tags can include value, currency, item count and transaction reference.
The module attaches shopping context as Clarity session tags and events: page type and controller, product name, category and IDs, cart and order value, currency, item count, order reference and the search term. It does not send customer names, email addresses, passwords or payment details. Tracking only runs when the module is enabled with a valid Project ID and, where configured, after marketing consent is granted.
Yes, custom Clarity events can be configured with JSON rules. The module supports click selectors, URL contains rules, controller or module matching and DOM events, then sanitizes event names and tags before sending them from the PrestaShop storefront.
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Microsoft Clarity is showing your team how shoppers behave through heatmaps, recordings and events tagged around product views, cart actions and checkout starts. Clarity also reports checkout exits and value at risk, while GA4 adds acquisition, attribution and revenue reporting across channels.
Google Analytics GA4 covers that, sending ecommerce activity, product views, cart activity, checkout starts, purchases, searches and account creation, built from PrestaShop actions, with a validated Measurement ID. It complements Clarity: one shows qualitative behaviour, the other provides quantitative ecommerce reporting, each configured on its own.
Together you get the why and the how-much. Clarity reveals where shoppers hesitate while GA4 measures product views, conversions and revenue at scale, so you can spot a friction point in recordings and then size its impact in analytics, with each tool answering a different part of the same performance question.
Microsoft Clarity adds heatmaps, recordings and custom events to your store, focusing on understanding on-page behaviour. As your measurement needs grow, you typically end up running several analytics and marketing tags, which are easier to organise centrally than to scatter across the theme.
Google Tag Manager helps there, adding your GTM container and feeding it ecommerce shopping events from real behaviour so tags can work with product views, cart changes and purchases. It does not run Clarity from its container; the two stay independent, with GTM organising its own tags alongside the dedicated Clarity module.
Used together, Clarity keeps doing its behavioural job while GTM manages the rest of your tag stack with shared ecommerce events. You get focused session insight and a tidier way to handle other tags, each tool in its own lane rather than one absorbing the other's responsibilities.
Microsoft Clarity gives you heatmaps and recordings that show where shoppers struggle, which is rich raw material but still requires expert interpretation to turn into prioritised, revenue-focused changes, especially across a full buying journey.
B2C Conversion Audit provides an independent journey review as a service, walking your real buying journey on mobile and desktop, analysing the funnel from view to purchase and pinpointing where shoppers leave, then mapping each leak to its likely revenue impact and a concrete fix. It complements Clarity with an expert journey review and an optional GA4 cross-check.
Together you pair your own session evidence with a structured conversion review. Clarity shows the behaviour while the audit turns observations into a prioritised plan, so instead of watching recordings and guessing what to change first, you get an evidence-informed verdict on which checkout and product-page issues to fix for the biggest conversion gain.
30 days return right
Plug & Play Modules
Dedicated Support First
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
