What it adds. Microsoft Clarity records how visitors behave on your site: sessions, time engaged, scroll depth, and friction such as rage clicks, dead clicks, quick backs, and script errors. OmniCommand reads one Clarity project and sets it beside your ad and analytics data, so a page that takes ad spend and loses visitors gets named.
Before you start. You need Clarity already installed on your site, and someone who is an admin of that Clarity project: only a project admin can generate the API token OmniCommand uses. In OmniCommand, Admins and Standard members can connect sources.
Connecting.
- Open your project in Microsoft Clarity, then Settings, then Data Export.
- Select Generate new API token and give it a name.
- In OmniCommand, open Microsoft Clarity on the Sources page. Type your project's name (Clarity does not share it, so it labels the project here) and paste the token.
- Choose Connect Microsoft Clarity. The first read checks the token. If Clarity refuses it, nothing is stored and the dialog shows Clarity's reason.
What OmniCommand reads. Once a day, the site's totals and the figures by page, by device, and by channel. Clarity allows 10 requests per project per day (UTC); OmniCommand uses up to 7, and the dialog shows how many are used today. If Clarity's daily limit is reached, reading resumes after midnight UTC.
History starts the day you connect. Clarity shares at most its last 3 days, so nothing older can be fetched. The connection reads those 3 days, and history grows one day at a time from there. Until the first day lands, the dialog says when collecting started.
Findings appear as data accrues. A Clarity finding needs a pattern that holds in at least 4 of the last 7 days, on a page with enough Clarity sessions (at least 100 for most checks), and some checks look only at pages taking Google Ads spend. So Clarity findings need several days of collection first, and a low-traffic page may never have one. Meanwhile, Microsoft Clarity under Channels shows sessions, friction, pages, and devices as they are recorded.
Clarity's numbers stay Clarity's. Clarity counts sessions its own way, so they will not match Google Analytics' sessions, and OmniCommand never mixes the two. Bot sessions are shown on their own, never folded in.
Disconnecting. Disconnect Microsoft Clarity from the Sources page. That removes the token from OmniCommand; to revoke it fully, delete it in Clarity under Settings, then Data Export. Microsoft Clarity counts as one connected source toward your plan's allowance.