Analytics12 min read19 February 2026

Measurement plans for a privacy-first web

Consent mode, modelled conversions and server-side tagging changed what your dashboard is really showing you. A grounded look at what still holds up.

By Daniel Okonjo

Consent mode, modelled conversions, browser privacy defaults and cross-device gaps have all changed what your dashboard is showing you. Most reporting has not caught up, which is why so many marketing reviews now descend into an argument about whose number is right.

The reports did not break — the assumptions did

The measurement stack most teams are running was designed for a world where a cookie followed a user reliably across a session, a device and a fortnight. That world ended gradually, and then all at once, and nobody sent a memo.

What has changed, concretely:

  • Consent gates collection. A meaningful share of your visitors are not measured at all, and the share varies by country, device and how your banner is worded.
  • Modelling fills the gap. Platforms estimate the conversions they cannot observe. This is reasonable and it is not the same as counting.
  • Cross-device linkage is weaker. The phone research session and the desktop purchase are, increasingly, two different people as far as your analytics is concerned.
  • Attribution windows shortened. Which systematically undercredits long consideration cycles — that is, exactly the purchases content marketing supports.

Start from the question, not the tool

The most common failure in a measurement setup is that it was built by starting with the platform. Someone installed GA4, accepted the defaults, added twenty events because events are free, and produced a property that measures a great deal and answers nothing.

Build it in this order:

  1. What decisions does the business need to make? "Should we keep investing in organic?" "Which pages should we rewrite first?" "Is the new onboarding flow working?"
  2. What would answer that? Specific comparisons, specific cohorts, a specific number with a specific baseline.
  3. What events and dimensions does that require? Usually far fewer than you have.
  4. Now open the tool.

A measurement plan built this way is typically half the size of the one it replaces, and it produces reports people read.

Definitions before dashboards

Almost every reporting dispute we are called into is a definitions dispute in disguise. Marketing counts a lead at form submission. Sales counts it after qualification. Finance counts it when it becomes an opportunity. All three are correct, all three are different, and the meeting is now forty minutes long.

Write the definitions down. Put them in the dashboard, next to the number, so that nobody has to remember. This one intervention has saved more client time than any technical work we have done.

Label what is modelled

If forty per cent of your conversion figure is modelled, say so on the slide. Stakeholders handle disclosed uncertainty far better than marketers fear. What destroys credibility is not the uncertainty — it is discovering the uncertainty afterwards, from someone else.

Our reporting views mark figures as observed, modelled or estimated, and give a rough sense of the split. It looks less impressive. It survives scrutiny, which is a better property for a number to have.

Server-side tagging: useful, not magic

Server-side tagging improves data quality and control, gives you a place to enforce consent properly, and reduces reliance on browser conditions you do not control. It also costs money, needs engineering time, and does not restore data from users who declined consent — which is a claim we hear made and which is not true.

It is warranted when data quality materially affects a decision worth more than the implementation. For a large e-commerce operation, that is usually. For a fifteen-person B2B firm with forty leads a month, it usually is not, and we will say so.

Rebuild the review, not just the reporting

The final piece is the monthly meeting itself. A report nobody can interpret is not a measurement problem; it is a communication problem, and it is fixed by a human being sitting with the stakeholders and explaining what changed, what we did about it, and what we are uncertain about.

We do that every month on every engagement. It is the least technical part of an analytics practice and, on most accounts, the part clients say they value most.

What you can still say with confidence

Plenty. Direction of travel is reliable. Relative comparisons between similar things measured the same way are reliable. Controlled experiments are reliable. Cohort analysis on your own first-party data — the data you own, in your own systems — is reliable, and is now more valuable than it has been in a decade.

What is no longer available is the illusion of precise, complete, deterministic attribution. It was always partly an illusion. The difference is that now we have to admit it, and the teams that admit it early end up trusted.

A note on claims. Nothing in this article should be read as a guarantee of results. Marketing outcomes depend on your market, product, budget, timing and team. We describe methods we use and what we have seen them do — not predictions of what would happen for you.

Written by

Daniel Okonjo

Head of Analytics. Most likely person in the agency to tell a client that a number they like is not reliable.

Keep reading

Related insights

Analytics11 min read

What content ROI actually measures

Attribution models disagree with each other by design. A practical way to talk about content value without overstating what the data can prove.

Editorial Strategy9 min read

The editorial calendar that survives Q4

Most content calendars fail in the fourth quarter. Here is the planning structure we use to keep publishing steady when everything else gets busy.

Start with a conversation

Tell us what is not working, and we will tell you what we would do about it.

A 45-minute review of your content, search and reporting setup. You leave with three prioritised recommendations, whether or not you work with us.