Privacy-First Analytics, Built Into Your CMS
Why we build privacy-first analytics into the Craft sites we manage — no cookie banner, real Core Web Vitals from actual visitors, and AI crawler tracking, all inside the CMS.
Most sites we take on arrive with the same setup: Google Analytics bolted on, and a cookie banner nobody clicks "accept" on willingly. The owner can see a visitor count, but not much they trust or act on — and the data that would help has been suppressed by the very banner that's there to collect consent for it.
We've taken a different approach on the sites we look after, and it's worth explaining why.
The trouble with the usual setup
Google Analytics is powerful, but for most site owners it's the wrong tool:
- It's built for marketing analysts, not the people running a business. The questions you actually have — how many people came, which pages they read, how fast the site felt, where they came from — are buried under configuration.
- It ships your visitors' data to a third party. That's what triggers the cookie banner, and it's a GDPR question you'd rather not have to answer.
- The banner itself costs you data. Every visitor who declines (or ignores it) is invisible, so the numbers you're working from are incomplete anyway.
You end up with a compromise: a privacy liability bolted to your site, collecting partial data, presented in a dashboard you rarely open.
What "privacy-first" actually means
The analytics we build in don't use cookies, so there's no banner to show, and no consent to chase. The data is gathered on your own server and stays there — nothing about your visitors is sent to anyone else.
Let's be straight about the trade-off: you give up some of the cross-site tracking and demographic guesswork that Google layers on. For the vast majority of sites, that detail was never reliable or actionable anyway. What you keep is the part that matters — an honest, complete picture of how your site is doing, without the legal baggage.
The numbers that actually matter
Inside the CMS you already log into, you get the figures worth acting on:
- Real visitor and page data — how many people, which content is pulling its weight, and which pages quietly do nothing.
- Core Web Vitals from real visitors — not a lab score from a testing tool, but how fast the site actually felt to the people using it, broken down by page. That tells you exactly what's worth fixing.
- Where people arrive from — search, referrals, direct, and increasingly AI tools (more on that below).
Seeing AI in your traffic
A growing share of the activity on a modern site comes from AI: crawlers reading your content, and people arriving from tools like ChatGPT and Perplexity. Most analytics packages filter bots out entirely, so you'd never know. Ours surfaces which AI crawlers are visiting and which are sending you traffic — an early signal of how visible you are as search shifts towards AI.
It comes to you
The best analytics are the ones you don't have to remember to check. A short digest lands in your inbox each week — traffic, your top content, performance, and anything flagged — so you stay across how the site is doing without opening a dashboard at all.
Where this sits
Built-in analytics is one part of Mutual One, the managed service and toolset we run on the Craft sites we look after. If you're tired of a cookie banner, a half-empty Google Analytics account, and numbers you don't trust, this is the alternative — and we're happy to walk you through it. Email us at hello@mutual.agency.
Andrew is Technical Director at Mutual, a Craft CMS Partner agency. He has been building with Craft CMS since its public beta in 2012 — working through every major version from Craft 1 to Craft 5 — and has delivered over 100 sites for clients including Apple, Transparency International, and Arts University Bournemouth.
He writes about Craft CMS on the Mutual blog and has contributed to net Magazine. At Mutual, he leads development of Mutual One, a marketing platform built on Craft CMS as its foundation.
He has spoken about Craft CMS to undergraduate students at the University of Brighton and Canterbury Christ Church University, and appeared on the Devmode.fm podcast. He has also trained development teams at other agencies in working with the platform.
