
Measurement
Part of How to build measurement and reporting for content agencies
Content agencies measurement mistakes buyers should check before signing
The content agencies measurement mistakes buyers see most, with symptoms, evidence to request, practical fixes and what to check before signing a reporting contract.
What to take away
- Consent is the biggest recent shiftmarketing cookies sit under PECR rules, so third-party tracking may not be lawful evidence.
- Google documents its crawlers, so agencies should explain how Googlebot and other user agents reach a page rather than assume indexing.
- Accessibility is a practical measurement input because W3C standards shape how content is built and audited.
- Inclusion criteriamistakes that appear in England client briefs, are visible in reporting, and can be fixed without replacing the agency.
- Scotland, Wales and Northern Ireland share the PECR and ICO framework, though devolved public sector reporting duties differ.
Reporting reach as if it were engagement
Impressions and sessions measure delivery, not effect. A reader who leaves in four seconds counts the same as one who reads to the end.
Distribution vs outcome metrics
Distribution
- Question
- Delivered?
- Examples
- Impressions, sessions
- Risk
- Four-second bounce counts
- Evidence
- Raw data export
Outcome
- Question
- Did it work?
- Examples
- Time on page, scroll depth
- Risk
- Effect invisible
- Evidence
- Named client question
Ask the agency to separate distribution metrics from outcome metrics. If they cannot name which figure answers which client question, the reporting is decorative. Ask for the raw data export behind each chart rather than a screenshot of a dashboard.
The wider content agencies measurement and reporting guide 2027 sets out how to structure that split across a year.
Ignoring how search engines actually crawl
Some agencies promise indexing without describing the mechanism. Google publishes its crawler documentation, and Googlebot is only one of several user agents that may fetch a page.
How a page gets indexed
- User agent fetches asset
- Robots directives allow or block
- JavaScript renders content
- Page enters index
- Traffic report shows result
Robots directives and JavaScript rendering both affect what gets indexed, and neither appears in a traffic report.
A useful test is whether the agency can explain which user agent fetches which asset. The Google crawler user agent overview is the reference to work from.
Treating accessibility as optional
The W3C publishes accessibility standards that shape inclusive content and are referenced in UK public sector duties. Content that fails them is harder to measure, because assistive technology users behave differently in analytics.
Ask for a sample page audited against those standards, not a policy statement. Build accessibility checks into the measurement plan rather than a separate audit. The W3C accessibility standards overview explains the conformance levels a brief can reference.
Using tracking that consent rules do not allow
Analytics and marketing pixels that rely on cookies need a lawful basis. The ICO publishes guidance on electronic marketing, consent and cookies under PECR. A dashboard built on data collected without valid consent is not evidence you can rely on.
Ask which tools fire before consent and what happens to that data. A privacy notice on its own does not make a marketing pixel lawful. The ICO guidance on direct marketing and privacy is the starting point.
Building dashboards nobody opens
A dashboard that restates platform numbers adds no decisions. Good reporting answers a question the client already has, then shows the next action. Three views usually cover acquisition, engagement and outcomes, plus a short note on what changed.
The content agencies reporting dashboard in England covers how to choose views people actually use.
Comparing the mistakes
Each row shows the symptom, the evidence to request and the fix. None of these need a new platform to resolve.
How it shows up
- Reach as engagement
- Impressions in the headline
- Crawl assumptions
- Indexing promised, not explained
- Accessibility ignored
- No conformance level named
- Consent gaps
- Pixels firing before consent
- Unused dashboards
- Nobody logs in
Evidence to request
- Reach as engagement
- Time on page, scroll depth
- Crawl assumptions
- User agent and robots notes
- Accessibility ignored
- Audit against W3C levels
- Consent gaps
- Consent mode and tag list
- Unused dashboards
- Named decisions per view
Fix
- Reach as engagement
- Split distribution from outcome
- Crawl assumptions
- Document fetching per asset
- Accessibility ignored
- Add checks to the plan
- Consent gaps
- Review against ICO guidance
- Unused dashboards
- Cut to three views
What to check before signing
Ask for one worked example of a past client's reporting pack, redacted if needed, and trace each figure to its source.
What to check in month three
Review whether the dashboard has changed any decision. If not, the measurement plan needs rewriting rather than more data.
Common questions
Do these mistakes apply outside England?
The ICO and PECR framework covers the whole UK, so the consent and cookie points apply in Scotland, Wales and Northern Ireland too. Public sector accessibility duties differ by nation, so check devolved rules.
Should I pay more for an agency with better measurement?
Not automatically. Compare what each supplier will report and how they will evidence it. A higher fee is only justified where reporting changes decisions.
How many metrics should a monthly report carry?
Few enough that someone reads them. For example, a team paying £400 a month for reporting might track three outcome measures and one distribution measure.
Can we fix these mistakes without changing agency?
Often yes. Ask for the evidence in the table and set a review date. If the agency cannot supply traceable sources after that, the brief is the problem.



