Analytics integrations
Upcoming featureAnalytics integrations: your Google Analytics and Clarity data inside the CRO audit
An upcoming feature for the Pro and Growth plans. It opens to a few accounts first.
- Google Analytics 4
- Search Console
- Microsoft Clarity
- PostHog
- Mixpanel
The size picker sends mobile visitors away
Mobile visitors leave 1.8× as often as desktop
Google Analytics 4
42% of rage clicks on the size buttons
Microsoft Clarity
On the page: the size guide opens below the fold on mobile, after the button.
Illustration on KYMA, a demo store. The feature is upcoming.
01 What it does
Google Analytics, Clarity and more, read by the CRO audit
01
Your numbers in the audit
02
A reading step first
03
Checked against the page
04
Per client folder
02 Why it matters
Numbers say where it hurts. The page says why.
Analytics tells you that mobile visitors leave the product page twice as often, but not what on the page sends them away. A page audit tells you what looks wrong, but not which problem is costing you the most.
Put together, each answers the other's question. The audit starts from your real numbers, looks for the cause on the screenshot, and only reports a finding when the two agree. A number with no visible cause is left out instead of guessed at.
03 How it works
How to connect analytics to a CRO audit
- 01
Connect a tool
Google Analytics, Search Console, PostHog, Mixpanel or Microsoft Clarity, from the client folder. Read-only access. - 02
Pick it in the audit
Choose which tools the audit reads. Each one adds a few credits, and you are not charged for a tool that had no data for the page. - 03
Read the report
Findings cite the number and the tool behind them, next to what on the page explains it.
04 An example
Example: analytics numbers checked on the page
The number
What the page shows
Verdict
Bounce 68% on mobile, 38% on desktop
Google Analytics 4
Buy box starts below the first screen on mobile
IN REPORTRage clicks on the size buttons
Microsoft Clarity
Sizes look tappable but the guide is folded away
IN REPORTSearch query "kyma tee shrink"
Search Console
Fabric and care answers it, but it is closed
IN REPORTFewer visits on Sundays
Google Analytics 4
Nothing on the page explains it
DROPPEDIllustration on KYMA, a demo store. The feature is upcoming.
From a product page audit
- 1Mobile visitors leave 1.8 times as often as desktop visitors (Google Analytics).
- 2Rage clicks concentrate on the size selector (Microsoft Clarity).
- 3On the page: the size chart opens below the fold on mobile, after the add to bag button.
- 4One lead, fewer visits on Sundays, had no cause on the page and was dropped from the report.
05 Guide
Why combine analytics data with a CRO audit?
Analytics answers where and how much: which page loses visitors, on which device, from which source. A CRO audit answers why: what on the page makes people hesitate or leave. On their own, each leaves a gap. Analytics shows a 68% mobile bounce rate but not the cause; a page audit lists ten problems but not which one is costing you.
With analytics connected, the audit starts from your real numbers for the exact page, looks for their cause on the desktop and mobile screenshots, and only reports a finding when the number and the page agree.
06 Guide
Supported tools and what the audit reads from each
Access is read-only and belongs to one client folder, so an audit only ever reads that client's data.
| Tool | What the audit reads for the page |
|---|---|
| Google Analytics 4 | Visits, engaged visits, active time, entries that leave or reach a key event, channels and devices, last 28 days |
| Google Search Console | Clicks, impressions, click-through rate and position, the searches that show the page, and whether Google indexes it |
| Microsoft Clarity | Scroll depth, active time, rage clicks, dead clicks, quick backs and script errors, per device |
| PostHog | Visits, views, rage clicks, dead clicks, errors, scroll depth and time on page, by device |
| Mixpanel | Page views, rage clicks and dead clicks per 100 page views, by operating system |
07 Guide
Analytics data that cannot mislead the report
Before the audit is written, an analyst model reads the numbers and lists leads: mobile visitors leave twice as often, rage clicks gather on the size buttons, a search query asks a question the page does not answer. Each lead is then checked on the page. Confirmed leads become findings that cite the number and the tool; leads the page cannot explain are dropped instead of guessed at.
If you already use Microsoft Clarity or Hotjar, this is the step that turns their recordings into an ordered list of fixes. For a path across several pages rather than one page, see the Funnel Audit.
08 Plans and cost
On the Pro and Growth plans
5 extra credits per analytics tool and 8 for Microsoft Clarity, on top of the CRO audit. If a tool returns no data for the page, its credits come back automatically.
09 Questions
Analytics integration questions
Start with a CRO audit today
Analytics integrations is an upcoming feature. Your audits run now, and they are what it will build on.
No card · Result in under 5 minutes · Desktop and mobile
