What's working. What isn't. What to do next
Most analytics setups answer the wrong questions slowly. I set up event tracking and dashboards designed for the three or four numbers that actually move your business, and write the SQL or BigQuery code when the canned report won't cut it.
- +A documented tracking plan, what fires, where, why
- +A working GA4 (or Plausible) setup with verified events
- +A glanceable dashboard for the three numbers that matter
- +A short written report each month
- ·Access to your site, GTM, and analytics property
- ·A clear sense of what success looks like, even roughly
- ·Time to read the monthly note
What this actually looks like.
Three numbers
I help you pick the three that matter and ignore the rest. Vanity metrics aren't free, they take attention.
Clear dashboards
Looker Studio or Plausible, designed to be glanceable in 30 seconds.
Server-side events
Where ad blockers eat client-side tracking, I move the events to your server.
Custom pipelines
When the off-the-shelf tool doesn't fit, BigQuery + dbt is often a simpler answer than yet another SaaS.
GDPR / PIPEDA-honest
Consent flows that don't lie, retention policies that match what you actually need.
Monthly reading
A short, written paragraph each month, not a chart dump.
How a project moves.
- 01
Inventory
What's already tracked, what isn't, and what's broken. Most setups have ghosts.
- 02
Plan
A tracking plan as a small spreadsheet: event name, when it fires, what it carries.
- 03
Implement
GA4, GTM, server-side, or pipelines, whichever fits.
- 04
Visualize
Dashboards that answer the three questions, plus a way to ask new ones in 10 minutes.
- 05
Review
A monthly written note. Numbers, context, recommendations.
What I usually reach for.
Picked by what fits the project, not what's on the bookshelf.
- GA4
- Plausible
- Google Tag Manager
- BigQuery
- Looker Studio
- dbt
- Segment
- PostHog
Let's build something great.
A short paragraph about what you want to understand is plenty.