# Clarity Lens

A Microsoft Clarity behavioural-data audit for a live site. Built by DNA (Daily Needs Association).

One skill: `/microsoft-clarity`. It reads a site's live Microsoft Clarity data, segments it by
device, traffic source, landing page and new-vs-returning, finds the single funnel stage leaking
hardest, and prescribes specific fixes, including exactly where a CTA or button should sit based
on the heat map and scroll depth, each one ranked by expected impact and shippable as a test.

This is the deep version of a Clarity read: it diagnoses a cause and a stage, not just a symptom
list. It replaces DNA's earlier lead-magnet `clarity-check` skill, which asked for pasted numbers
and returned a flat top-three list.

## Install

1. Add this pack to your Claude Code (project knowledge, or wherever your skills are installed).
2. Generate your own Microsoft Clarity Data Export API token: open your Clarity dashboard for the
   site, go to Settings, Data Export, generate a new token. This token is yours alone, one token
   per Clarity project.
3. Add the Microsoft Clarity MCP server to your own Claude Code config with that token
   (`@microsoft/clarity-mcp-server`, started with `--clarity_api_token=<your token>`).
4. In Claude Code, say "run my Clarity" or type `/microsoft-clarity`.

The skill requires a live Clarity MCP connection. It does not work from pasted dashboard numbers;
if the connection is missing it stops and walks you through the setup above rather than guessing.

## What it does

- Segments the data before drawing any conclusion, so a site-wide average never hides where the
  real leak is.
- Maps every page to a funnel stage (entry, browse, offer, intent, checkout) and finds the stage
  losing the most visitors relative to its own traffic.
- Reads the heat map against scroll depth to decide exactly where a CTA belongs, whether an
  existing one needs to move, and whether a dead zone means it is invisible, mislabelled, or
  untrusted.
- Confirms the diagnosis by pulling session recordings of non-converters on the leaking page.
- Ranks fixes by expected impact and writes each one as a testable experiment with a metric to
  watch, then saves a baseline so the next run checks whether last time's fix actually worked.

## What it never does

Never edits the live site; every fix is a recommendation staged for your own go. Never promises a
revenue, order, or traffic number; it states the mechanism and the expected direction only, never
a projected outcome. Never invents a figure that was not read live in that run.
