Microsoft Clarity on Shopify: setup and data checks

Connect Microsoft Clarity to Shopify with the current supported method, then check recorded page coverage, masking, consent and duplicate installations.

Yes, Microsoft Clarity connects to Shopify through Microsoft’s official app. Use the app’s new-installation or existing-project route, then verify the recorded pages and privacy behaviour. A connected dashboard alone does not prove that the whole buying journey is captured.

Choose the current installation route

Use Microsoft’s Shopify app for a new installation, and connect the existing project when migrating an older snippet. First record the store, intended project identifier and the people who control both accounts.

Review the Microsoft Clarity app’s data access before installing it. The listing includes customer activity and device data, product and order access, web pixels and theme editing. Compare the installation permission screen with the access your store approves.

Confirm who administers the Clarity project under Settings > Team. Microsoft’s team permissions give project settings control to Admins. Give a retailer-controlled account administrative access before an agency or contractor changes the connection.

Install or reconnect the app

Microsoft’s Shopify installation guide separates these paths.

  1. Find Microsoft Clarity: AI Insights in Shopify’s App Store. Select Install and review the requested data access.
  2. For a new installation, choose Go to app settings. Enable Clarity JS, save and return to the installation page.
  3. Refresh the app dashboard if it does not update automatically. Allow a few hours for dashboard data to populate.
  4. For a pre-installed snippet, choose Connect Project instead. The project admin follows the emailed link and signs in to connect the existing project.
  5. Return to the installation page and refresh. Confirm the intended project is connected before testing.

Microsoft documents automatic migration of an older theme.liquid installation without code changes. Inspect any other Clarity installation, including a tag-manager copy, separately. Keep a recoverable copy before removing confirmed redundant code.

Microsoft documents checkout and post-checkout tracking through Shopify’s pixel for Shopify Plus accounts. Treat checkout coverage on the actual store as a separate acceptance check.

Check the recorded retail journey

Run a fictional shopping journey and locate its actual pages in the connected project’s Recordings view. Use test products and invented customer details so the privacy check does not expose a real customer.

Define the pages you expect to capture before starting. Include the active theme and any separate account or checkout domain in the record.

A fictional browsing check

Test actionWhat to findWhat the result establishes
Open a test collectionThe collection page in the replayThat this page is being captured
Open one product and choose a variantThe product page and visible interactionThat product selection is represented in the replay
Add the item and open the cartThe cart page or cart interactionThat the captured journey reaches the basket
Continue to the store’s test checkoutThe pages actually present in the replayThe observed checkout coverage for this installation

Record the missing pages explicitly. Microsoft’s setup documentation says Clarity cannot capture inside third-party iframe or canvas elements. A recording of the surrounding page does not establish visibility into an embedded payment interface.

Verify masking with fictional content

In Settings > Masking, inspect the selected mode and any element overrides. Microsoft’s masking documentation describes Balanced as the default, with Strict and Relaxed alternatives. Input boxes and dropdowns remain masked in every mode.

Place invented sensitive text in each relevant page state, including account details displayed outside form inputs. Review a new replay and confirm that the text is hidden. Add explicit element masking for content that the selected mode leaves visible.

Only project administrators can change masking settings. Changes affect new recordings, can take up to an hour and do not repair earlier captures. Repeat the fictional journey after the new setting takes effect. Keep sensitive content out of stylesheets because Microsoft documents a masking limitation there.

A visible cookie banner does not prove that Clarity receives the visitor’s choice. Microsoft’s Consent Mode instructions describe passing consent through a supported consent platform or the Consent API.

Use a fresh browser profile to test declined and accepted choices. Where Consent Mode applies, check Clarity’s reported consent state and the browser’s cookie storage. Declined cookie permission must not create Clarity’s _clck or _clsk cookies. Accepting or withdrawing consent must update the reported state.

Microsoft requires consent signals for full functionality for visits from the European Economic Area, United Kingdom and Switzerland. Check the behaviour for the visitor’s region, including overseas customers of an Australian store.

Cookie denial can still permit limited collection. A collection request alone does not prove cookies were accepted or that a continuous replay exists.

Resolve missing or duplicated records

Separate a delayed dashboard from a wrong destination or missing installation before adding another script. Microsoft’s installation troubleshooting starts with installation and collection-request checks.

Diagnostic checks and expected results

SymptomCheckCorrection and expected result
Newly connected app has an empty dashboardConfirm Clarity JS is enabled and generate a test visitRefresh after the documented collection delay. The intended project must show the test activity
Activity appears in another projectCompare the connected project with the intended project identifierUse the existing-project connection route. New activity must appear in the intended project
One page type is absentCheck whether that page loads Clarity and whether the missing content is embeddedRestore the documented installation on a supported page. Record an unsupported embedded area as a coverage limit
Two Clarity installations are presentInspect the app, theme and tag manager for the same or different project identifiersRetain the intended app connection and remove only a confirmed redundant copy. Repeat the journey with one intended installation
No collection requests on an expected pageConfirm app activation and inspect browser errors or blocked requestsCorrect the installation or the specific blocking rule. Fresh interaction must produce a collection request and project activity
A journey splits across page visitsCompare consent state with cookie storageCorrect missing consent transmission where permission was granted. Retest continuity without overriding a refusal

Microsoft’s verification method checks network POST requests to Clarity’s collection endpoint alongside activity in the project. Inspect requests privately and share only redacted results when escalating a failure.

If installing the app created an unexpected project, Microsoft’s Clarity FAQ explains that the app uses store credentials. It documents adding the store owner’s account to an existing project to connect it. Resolve account access before replacing the tracking code.

After a theme change, repeat the page checks. For rollback, restore the saved theme or tag-manager configuration only if it was the confirmed previous installation. Check for duplicate collection again before returning to normal monitoring.

Use recordings with their limits

Use a recording to form a testable explanation of a shopper’s actions, then compare it with store events and order records. A replay ending at a product page does not establish that the customer failed to buy.

Microsoft describes Clarity as having no traffic sampling. Collection still depends on script execution, consent and page coverage. Filters and retention also change the recordings available to inspect. These limits prevent the visible replay list from being treated as a complete store order count.

Clarity’s recordings overview explains that replays reconstruct page content and actions. They are not screen videos. Full recordings have a limited retention period, with only a subset retained for longer unless favourited.

For example, repeated clicks on a delivery panel suggest a usability question. Compare that observation with the actual button behaviour and the store’s cart or checkout events. Test the suspected fault before attributing lost purchases to the panel.

Turn the verified observation into an ecommerce insights question with an observable result, such as whether customers can open delivery details before adding the product. Keep the recording, the reproduced behaviour and the order evidence distinct when deciding what to change.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup