Loading tutorials…
Loading tutorials…
Clarity is free and the install is famously easy — but the choices you make in the first 45 minutes (data masking, retention, project ownership) are hard to undo later. This walkthrough gets the configuration right the first time.
Who this is forFounders, marketers, and operators who want behavior analytics on their site without paying Hotjar prices. If your site does $50K+/year in revenue and you have no behavioral data, you are flying blind on every conversion decision — the cost of NOT having Clarity is now larger than the cost of setting it up.
What you'll need
Step 1
Sign in at clarity.microsoft.com with Microsoft, Google, or Facebook. Create a Project (one Project per site, not per environment).
Go to clarity.microsoft.com and click "Sign up free." Choose Microsoft, Google, or Facebook auth — pick the account that will outlast contractors and freelancers (use a shared ops account, not a personal Gmail).
After auth, you land on the Dashboard with a "+ New Project" prompt. Click it.
Name the Project after the site (e.g., "everestx.com — production"). Add the website URL (apex domain, no trailing slash).
Set the industry category and project size. These do NOT affect tracking — they only tune the Insights defaults later.
Click "Create." Clarity generates a Project ID — note it down, you will need it for the tag install.
Step 2
Settings → Privacy. Choose Strict (default), Balanced, or Relaxed masking. This decides what gets recorded — and what you cannot un-record.
In the left sidebar, open Settings → Privacy.
Default is "Strict" — all input fields, text content, and images masked. Best for any site collecting PII (email, phone, addresses) and for any site touching healthcare, finance, or kids.
"Balanced" masks only inputs and sensitive fields. Page text and images record normally. Good default for most ecommerce and SaaS sites.
"Relaxed" masks only password fields. Use this only on marketing sites with zero PII collected — landing pages, blog content, brochureware.
For specific elements that need extra protection, add CSS selectors to the "Mask additional elements" list (e.g., `.credit-card-input`, `[data-pii]`). For elements you want to UN-mask, add them to "Unmask elements."
Save. This setting applies retroactively to all future recordings — but not to ones already captured.
Step 3
Settings → Data → Retention period (default 30 days; max 13 months on free tier). Add internal IP addresses to exclude from tracking.
Settings → Data. Set "Retention period" to 90 days minimum. The 30-day default is too short to catch weekly conversion patterns and seasonal behavior.
Add your office IP, your VPN IP, and any contractor IPs to the "IP Block" list. This stops your own testing from polluting recordings and heatmaps.
If you use a VPN, your IP rotates — add a `*` wildcard for your subnet, or use the User-Agent block instead.
Add any QA tools, bot User-Agents, and uptime monitors (Pingdom, UptimeRobot) to the User-Agent block list.
Save. Filters apply going forward; existing recordings stay in the dataset.
Step 4
Settings → Team. Invite by email. Roles: Admin, Member, or Viewer.
Settings → Team. Click "Add user."
Use Admin role sparingly — Admins can change masking, delete Projects, and access raw data. Typically only the data owner and one backup.
Member role lets users view recordings, create heatmaps, and filter — but cannot change Project settings. Default for marketers and CRO specialists.
Viewer role is read-only on Recordings and Heatmaps. Use for stakeholders who want to spot-check but should not be filtering or sharing.
For contractors who leave the team often, invite them via a shared mailbox alias (e.g., `cro-contractor@yourdomain.com`) so you can revoke access by reassigning the mailbox.
Step 5
Settings → AI Insights → Enable. Choose digest frequency and recipients.
Settings → AI Insights → toggle "Enable AI summaries" to ON.
Choose what AI summarizes: Recordings, Heatmaps, or Both. Both is the default and is fine for most sites.
Set "Weekly digest email" — pick at least one human recipient who will actually read it. Empty digests go to "noreply" inboxes and the team stops noticing real signals.
AI Insights need 1,000+ recordings per week to produce useful clusters. If your traffic is below that, AI summaries will be noisy for the first month — set expectations.
Save. First AI digest arrives one week after install.
Step 6
Dashboard → Project health card should show "No tag detected" (expected until step 2 of next tutorial). All other Settings should show green.
Return to Dashboard. The "Project health" card at the top right shows configuration status.
Expected state at this point: "No tag detected" (this is normal — you have not installed yet) and "Privacy mode: [Strict/Balanced/Relaxed]" matching what you chose.
If you see "Configuration incomplete" warnings, click through to resolve them before installing the tag — the warnings will block data collection or quietly drop fields.
Note the Project ID from Settings → Setup. The next tutorial uses this to install the tracking code.
Common mistakes
Using a personal Microsoft/Google account for the Project owner
What goes wrong: When the founder or contractor who set this up leaves, Clarity access goes with them. Recovering Admin access takes 2-4 weeks of Microsoft support back-and-forth. In that window, no one can fix masking or add users — and ~$2,000 of behavioral data goes unanalyzed.
How to avoid: Always use a shared/ops Microsoft or Google account as the Project owner. Add named individuals as Admins/Members so departures do not lock out the team.
Choosing Strict masking on a non-PII site
What goes wrong: Strict mode masks button text and link labels, so when you finally try to debug a rage-click cluster three months in, you cannot see what users were actually clicking. Two weeks of useful recording context is lost.
How to avoid: Pick masking based on what you actually collect. Brochureware → Relaxed. Standard ecommerce/SaaS → Balanced. Healthcare/finance/kids → Strict. Add specific CSS selectors to mask only the truly sensitive elements.
Leaving the 30-day default retention
What goes wrong: Default 30-day retention means your Q4 holiday recordings are gone before you can compare them to Q1 baseline. You lose ~$5,000-15,000 of season-over-season learning every year.
How to avoid: Bump retention to 90 days minimum (free tier max is 13 months — use it). Set the change before your busiest traffic period, not after.
Not filtering internal IPs
What goes wrong: Your own QA testing, contractor reviews, and bot traffic pollute every heatmap. Click maps show buttons being clicked that no real user clicks. Bad data drives bad CRO decisions — average cost of one wrong test: $1,500-3,000.
How to avoid: Settings → Data → IP Block. Add office IP, contractor IPs, and known bot User-Agents. Re-audit quarterly when remote teams change networks.
Adding the whole company as Admins
What goes wrong: Six people can change masking settings, delete Projects, or accidentally rotate the tag ID. The day someone clicks the wrong toggle, you lose continuous data — and the audit log only tells you who, not why.
How to avoid: Two Admins maximum (owner + backup). Everyone else is Member or Viewer. Treat Admin like a production database password.
Recap
Done — what's next
How to install the Microsoft Clarity tracking code
Read the next tutorial
Hand it off
Most operators install Clarity and never look at it again — which is the same as not having it. If you would rather have a vetted CRO specialist review recordings weekly, surface real friction points, and turn the data into A/B tests, that is what EverestX matches you with. From $14-16/hr part-time; typical ongoing engagements land at $400-800/month.
See CRO specialist rates
Genuinely free. No session caps, no recording caps, no feature paywall — Microsoft monetizes Clarity indirectly through Bing ads and Azure data. The only practical limits are 13-month retention and rate limits on the API tier.
Clarity if cost matters and you want unlimited sessions. Hotjar if you need built-in surveys and feedback widgets. Both if you have a CRO specialist who will actually use both — otherwise pick one. For most SMBs under $1M revenue, Clarity alone is enough.
The Clarity tag is ~38KB gzipped and loads asynchronously. PageSpeed impact is typically 50-100ms on mobile — measurable but not in the range that affects rankings or conversion. If you are on a heavily optimized site, load it via GTM with a 2-3 second delay to push it below the LCP threshold.
No — recordings and heatmaps are tool-specific and not portable. Run both in parallel for 30 days, validate Clarity is capturing what you need, then disable Hotjar. Export any Hotjar reports you need before cancellation.
Strict masking + IP anonymization (enabled by default) covers most GDPR/CCPA requirements for behavioral data. You still need a cookie consent banner that delays the Clarity tag until consent is given — Clarity provides a Consent API for this (see Settings → Setup → Consent).
Microsoft Clarity
The install itself is 30 seconds. Doing it cleanly so consent banners, GDPR rules, and SPA route changes do not break tracking takes about 30 minutes. Here is the full path.
Microsoft Clarity
Clarity generates heatmaps automatically — but the default view aggregates desktop + mobile + tablet across every URL variant. That is unusable. Here is the configuration that produces heatmaps you can actually act on.
Microsoft Clarity
Clarity is free with no caps. Hotjar costs $39-589/month with session limits. So why isn't this an obvious win for Clarity? Because Hotjar has features Clarity does not — and on the wrong site, the savings are not worth the gaps.
Microsoft Clarity
You installed Clarity. You watched some recordings. You ran an A/B test or two. So why is conversion rate still flat? This is the honest framework: when DIY CRO hits its ceiling and a specialist starts paying for themselves.