Microsoft Clarity Integration for CS-Cart

The General tab holds the connection between CS-Cart and the Microsoft Clarity project. Admins enter the Project ID copied from the Clarity Overview page and switch recording on.

• Enter the Clarity Project ID taken from the Clarity project Overview page.
• Set Enable Storefront Tracking to Yes or No to control recording.
• Set Require Cookie Consent for Tracking to Yes for cookie-less anonymous mode.
• Tick Use Custom Tracking Script to paste a script instead of the generated one.
• Keep tracking off in the administration and vendor panels, which the module enforces.

Telemetry and Custom Session Tags attach CS-Cart context to each Clarity session. The tags become filters inside Clarity, so recordings can be grouped instead of watched at random.

• Customer Group tags the session as Guest, Registered, Wholesale, or a custom group.
• Storefront Currency & Language records the active currency and browser locale.
• Device Category sorts the session as Desktop, Tablet, or Mobile.
• Storefront ID names the storefront a shopper browsed in a multi-storefront setup.
• Active Vendor Name & ID marks the vendor for Multi-Vendor installations.
• UTM Traffic Source Campaign variables capture utm_source, utm_medium, and utm_campaign.

Ecommerce Events to Record decides which shopper actions are sent to Clarity as named events. Each event shows up as a clickable marker on the session playback timeline.

Merchants pick the events they care about, so a busy catalog does not fill every recording with noise. Stores that also alert shoppers on those actions can pair it with CS-Cart Advanced Notification.

• Product Detail View Actions fire when a shopper opens a product page.
• Cart Increments & Removals fire when items are added to or removed from the cart.
• Checkout Funnel Progress Steps fire as the shopper moves through checkout.
• Final Order Purchase metrics fire when checkout is completed.
• Product Search queries log the keywords a shopper typed into catalog search.
• Customer Logins & Registrations and Wishlist & Product Comparison updates log account and list activity.

Microsoft Clarity samples sessions when traffic is heavy, so a purchase can go unrecorded. Priority Recording Upgrades call the Clarity upgrade API and keep the visits that matter.

Stores that run campaigns or flash sales use this to guarantee a replay for every completed order, including orders placed through CS-Cart Razorpay Magic Checkout.

• Cart Page Load raises recording priority when a shopper opens the cart.
• Checkout Form Load raises priority as soon as checkout begins.
• Order Complete Page raises priority when the shopper reaches the order confirmation.
• Each upgrade works on its own, so a store can keep only the checkout trigger.

PII Privacy Content Masking keeps customer data out of the replays. A masked field shows stars in the recording, while unmasking rules keep public content readable.

• Personal Information hides name, email, and phone inputs.
• Address details hide billing and shipping fields.
• Financial entries hide credit card numbers, CVV, and payment forms.
• Custom Masking Selectors accept CSS selectors for any extra block to hide.
• Unmasking Public Elements keep specification grids and the review feed readable.
• Custom Unmasking Selectors accept CSS selectors for blocks that must stay visible.

Admin Dashboard Analytics Settings connect the CS-Cart backend to the Clarity Data Export API. Generate the token on the Data Export page of the Clarity project, then paste it here.

• Data Export API Token stores the Clarity REST Data Export token.
• Enable Dashboard Widget turns the backend insights screen on or off.
• Report Date Range sets the window the metrics are pulled for.
• Primary Grouping Dimension groups metrics by Device, Browser, OS, or Country.
• Update Cache Interval sets how long the dashboard reuses stored metrics.

The Microsoft Clarity Insights screen sits under Website > Microsoft Clarity in the admin sidebar. It shows project metrics inside CS-Cart, so a merchant does not have to open the Clarity portal.

Clarity allows 10 Data Export calls per project per day, and the module respects that limit.

• Metric cards report Sessions, Rage Clicks, Dead Clicks, and Average Scroll Depth.
• Dimension Breakdown Metrics list the same figures per segment with engagement time.
• Last Updated shows the time the stored metrics were pulled from Clarity.
• Refresh Data pulls new figures, capped at 10 requests per day.
• Saved setting changes read the cache and spend no API request.
• Go to Microsoft Clarity opens the full project in the Clarity portal.