Analytics
AI agent for Microsoft Clarity: find the landing pages that lose your paid traffic
TL;DR
Microsoft Clarity connects with a Data Export token per project. The agent reads Clarity's own numbers for the last 1, 2 or 3 days — sessions, users, pages per session, scroll depth, engagement time and friction signals — broken down by page, source, campaign, channel, device, country, browser or OS, and ranks the landing pages with the most friction. It never changes your site or your Clarity settings.
Connecting it
- 1In your Clarity project, a project admin opens Settings → Data Export → Generate new API token and copies it.
- 2Open Integrations, press Connect a project on the Microsoft Clarity card, give the project a name, paste the token and press Check and save.
- 3Repeat for each project — every project has its own token. Then pick the project in the context picker and write the goal.
What Clarity's API allows (and the agent respects)
- The last 1, 2 or 3 days only — the last 24, 48 or 72 hours from the moment of the call. Longer ranges, such as last week or last month, cannot be read through the API; the agent says so and points to the Clarity dashboard.
- 10 requests per project per day. Microsoft's limit, shared by everyone who connected the same project. Answers are kept for a while, so asking the same question again costs nothing; the card shows how many requests are left today.
- Up to 3 breakdowns per request (page URL, source, medium, campaign, channel, device, country, browser, OS) and up to 1,000 rows, with no paging — a list that reaches 1,000 rows may be incomplete, and the answer says so.
- One token reaches one project. A token is never assumed to reach another project; Replace token swaps a project's token in place and refuses a token from a different project.
What the agent reads
- Traffic: sessions, bot sessions (counted apart), distinct users and pages per session.
- Engagement: scroll depth and total / active time on page.
- Friction signals: dead clicks, rage clicks, quick backs, excessive scrolling, script errors and error clicks — as a share of sessions and as counts.
- Where visitors came from: sessions and behaviour by source, medium, campaign or channel, optionally by device or page.
Landing-page opportunities
- Ranked pages: pages with enough sessions (20 by default) and the strongest friction — rage clicks from 5 % of sessions, dead clicks or quick backs from 10 %, low scroll depth — each with its numbers. The thresholds are ours, stated in every answer.
- Paid traffic quality: read beside your ad platforms' clicks, a campaign whose visitors bounce straight back points at the landing page or the targeting, not the bid.
- Concrete changes to try: move the call to action above the fold where scroll depth is low, fix the element that draws rage or dead clicks, speed up a page with many quick backs.
Read-only. The agent reads Clarity and never changes your site or your Clarity settings, so there is nothing to approve. When the window had no human sessions, it says there is no data rather than reporting zero problems.
Frequently asked questions
- Does Agent Planners support Microsoft Clarity?
- Yes. Connect each Clarity project with its Data Export token and the agent reads traffic, engagement and friction signals for the last 1–3 days and ranks the landing pages to fix first. It is read-only.
- Can it read more than three days of Clarity data?
- No. Clarity's Data Export API returns only the last 1, 2 or 3 days. For longer ranges use the Clarity dashboard; the agent says so instead of guessing.
- Why does it limit how often it reads Clarity?
- Clarity allows 10 API requests per project per day. The agent reads once per question, keeps the answer for a while, and labels an older answer with the time it was read.
- Can one token cover several Clarity projects?
- No. Each Clarity token belongs to one project; connect each project with its own token.