Digital analytics you can make decisions with.

Digital analytics, tracking and reporting built properly: measurement plans, GA4 and Tag Manager, server-side tagging, dashboards and modelling. This is the work other agencies bring me in for.

You might be here because

  1. GA4 was “set up” once and nobody has trusted a number since.

  2. Conversions dropped the week the cookie banner went live.

  3. Three reports give three different answers to how many leads you got last month.

  4. Your tag container is a decade of other people’s experiments.

  5. Someone on the board asked what the TV spend actually did, and the room went quiet.

What I can do

Most data work starts with an audit or a measurement plan. It’s the cheapest step, and it stops you paying to implement the wrong thing well.

Try the free tracking checker first

Analytics audits

A check of what you’re collecting and what’s broken, duplicated or missing. You get a short report with the fixes ranked, and a straight answer on which numbers to trust.

Analytics audits

  • GA4 and Tag Manager review
  • Ad platform tracking review
  • Consent and privacy configuration
  • Ranked fix list

Measurement plans

A tracking specification that starts from the decisions you need to make and works back to events, parameters and reports. Developers can build from it and marketers can read it.

Measurement plans

  • Business questions and KPIs
  • Event and parameter specification
  • Naming conventions
  • Developer handover notes

GA4 and Tag Manager implementation

A clean build or a rebuild of your analytics and tag setup, tested against the plan and documented so the next person can understand it.

GA4 and Tag Manager setup

  • GA4 property configuration
  • Tag Manager container build
  • Ecommerce and lead tracking
  • QA and documentation

Server-side tagging and Conversions API

Moving tracking from the browser to a server you control. It recovers data that ad blockers and browser restrictions throw away, speeds up your pages and gives you a say in what each platform receives.

Server-side tracking

  • Server-side Tag Manager on Stape or Google Cloud
  • Meta, Google and other Conversions APIs
  • First-party setup
  • Before and after comparison

Dashboards and reporting

Reports people open more than once. Built in Looker Studio on clean sources, designed around the questions your team asks every month.

Dashboards and reporting

  • Looker Studio dashboards
  • BigQuery data sources
  • Blended ad, web and CRM data
  • A one-page view for the boss

Marketing mix modelling

For businesses spending across several channels, including ones you can’t click on. Using Google’s open-source Meridian, I model what each channel contributes and where the next dollar should go.

Marketing mix modelling

  • Data collection and preparation
  • Model build and validation
  • Budget scenarios
  • Refreshes as new data arrives

Pipelines and automation

Getting data from where it lives to where it’s useful: feeds, scrapers, scheduled exports and workflows that replace the spreadsheet somebody updates by hand every Monday.

Marketing automation and AI workflows

  • Data pipelines between platforms
  • Web data collection
  • Workflow automation
  • Validation and monitoring

How it usually runs

Audit or plan

A fixed scope with a written report and a walkthrough.

Implementation

Build, test and document, with a handover to your team at the end.

On call

A small monthly range of hours for changes, new campaigns and questions.

Tools I work in

  • Google Analytics 4
  • Google Tag Manager
  • Server-side GTM
  • Stape
  • Conversions API
  • BigQuery
  • Looker Studio
  • Google Meridian
  • Python

Fair things to ask.

Something else on your mind? Ask me directly.

What is server-side tracking, in one paragraph?

Normally a visitor’s browser sends data straight to Google, Meta and the rest, and ad blockers now stop a good share of it. With server-side tracking the browser talks to a server on your own domain, which passes on what you choose. Data is more complete, pages load faster and you decide what each platform sees.

Is this compatible with consent and privacy rules?

Yes. Tracking respects the consent choices your visitors make, and server-side setups make it easier to control what is shared. Legal wording stays with your lawyer.

Do we need a developer?

Sometimes, for changes to the site itself. I write the specification, work with your developer and test what they ship. Most tag and analytics work needs no developer.

Who owns the setup when you’re done?

You do. Everything is built in your accounts or transferred to them, with documentation and a list of who owns what.

Something driving you mad?

Tell me what’s going on. I’ll come back with questions or a scoped proposal, and I’ll say so if I’m not the right person for it.