The short answer
GA4 tells you what visitors did. Three free tools fill the gaps. Microsoft Clarity shows how they did it, with session recordings and heatmaps. Google Search Console shows what people searched for before they arrived. Bing Webmaster Tools does the same for Bing. Set up all three, and treat Clarity like any other analytics tool when it comes to consent.
What each tool answers
| Tool | Answers | Does not answer |
|---|---|---|
| GA4 | Which channels, pages and events led to leads | Why people stopped, or what they searched |
| Clarity | Where people click, scroll and get stuck on a page | How many leads a channel sent |
| Search Console | Which Google queries showed and clicked your pages, and indexing problems | What visitors did after they arrived |
| Bing Webmaster Tools | The same view for Bing search | Google search |
Use them together. A typical month: Search Console shows a page getting more clicks, GA4 shows those visitors rarely send the form, and Clarity recordings show the form is below a long block of text on phones. No single tool would have told you that.
Install Clarity
Clarity's setup guide gives three ways to install it: a third-party platform integration, the tracking code pasted into the head, or an npm package. It also has a Google Tag Manager integration that it detects automatically and can publish into your container.
On a Webflow or Astro site that already runs Tag Manager, adding Clarity through the container keeps every tag in one place and under the same consent rules. On Astro, the npm package is an option if you prefer code.
A few points from Microsoft's own docs worth knowing before you switch it on:
- Clarity should not be used on sites or apps aimed at people under 18.
- It cannot capture what is inside a canvas or a third-party iframe. A Cal.com or Calendly embed will show as a box, not as the booking flow.
- It detects bot traffic by default and leaves it out of session counts.
- To check the install, look for POST requests to
clarity.ms/collectin the Network tab, or open the project and watch live sessions.
Clarity also has a Google Analytics integration, set up from its own settings, that links session recordings to your GA4 data.
Clarity and consent
Microsoft's Clarity consent mode page says that from 31 October 2025, Clarity enforces consent signals for visits from the European Economic Area, the UK and Switzerland, and that a valid signal is needed for full functionality there. Consent mode is on by default for visitors from those regions. You can also turn cookies off for everyone, under Settings, Setup, so Clarity waits for consent everywhere.
You pass the choice with the ConsentV2 API:
window.clarity('consentv2', {ad_Storage: "granted", analytics_Storage: "granted"})
Without consent, Microsoft says Clarity runs in a no-consent mode: it sets no cookies and gives each page view its own ID, so recordings are not joined into multi-page sessions. If a visitor rejects after accepting, Clarity deletes its cookies and restarts in no-consent mode. You are responsible for telling Clarity when consent changes.
The practical setup: if you use a consent tool, check whether it passes the signal to Clarity. If you built your own banner, call consentv2 in the same place you send Google's consent update. To check it, Microsoft gives a console snippet that prints the current consentStatus, which should read denied before a choice and granted after Accept.
Decision rule If Clarity runs outside Tag Manager's consent checks, it needs its own consent call. A heatmap tool that ignores the banner is the most common gap we find in audits.
Keep recordings private
Recordings show real people using your site, so set masking before you watch any. Clarity's masking docs describe three modes, set under Settings, Masking:
| Mode | What is masked |
|---|---|
| Strict | All text content |
| Balanced (default) | Content Clarity treats as sensitive, such as numbers and email addresses |
| Relaxed | No content, except input boxes and dropdowns |
Input boxes and dropdowns are masked in every mode. To mask one part of a page, add data-clarity-mask="True" to the element, and it and its children are masked whatever the site setting says. Masking changes apply to new recordings only, so set it before launch, not after someone notices a problem.
Search Console
Add a domain property. Google's property help says it covers both protocols and every subdomain, including www and non-www, and that it verifies by DNS record only. A URL-prefix property covers only the exact prefix you type, so it misses data from other versions of your address.
- Verify the domain with the DNS record Google gives you.
- Submit your sitemap in the Sitemaps report. Google says this does not guarantee every URL is crawled, but it helps it find them.
- Link Search Console to GA4 in GA4 Admin, under Product links. You need the Editor role in GA4 and verified owner status in Search Console.
- Publish the Search Console report collection in GA4's Library. Google says it is unpublished by default.
- Expect Search Console data in GA4 about 48 hours after Search Console collects it.
For what to do with the data once it is there, see Search Console quick wins.
Bing Webmaster Tools
Bing is smaller than Google, but it costs ten minutes to set up. When Bing announced its import option, it said you can import your verified sites from Search Console, including their sitemaps, and that imported sites are verified automatically. Check the current sign-up screen, as the steps may have changed since.
Once the site is in, check that your sitemap shows as processed, and look at the search performance report once a month alongside Search Console. If the two disagree on which pages matter, that is worth a look.


