Two people decide, one gets tracked
The student browses on a phone and the parent researches costs on a laptop. Your analytics sees two unrelated visitors and credits whichever converted.
What's different here
Enrolment measurement has a structural problem no vendor solves: the decision involves at least two people on separate devices, and the cycle from first interest to enrolment runs well over a year. Standard attribution windows expire long before the outcome, so the channels that created interest are invisible and the ones present at application get all the credit. That is how institutions end up over-funding the bottom of a funnel they are not filling.
Education & EdTech clients
What analytics & measurement looks like for education providers.
These are the plays that wouldn't appear on a generic analytics & measurement page — they only make sense in education & edtech.
Extend the window to match the cycle, then stop trusting it
A ninety-day window on a fourteen-month decision measures almost nothing. Extending it helps, but the honest position is that last-touch attribution cannot work at this timescale — which is why holdout testing matters more here than in almost any other sector.
Connect enquiry to enrolment through the student record
The outcome lives in the student information system, not in analytics. Matching applicants back to their original enquiry — with consent and with care about what crosses the FERPA boundary — is what lets you evaluate a channel on enrolments rather than on form fills.
Treat the household as the unit where you legitimately can
Student and payer are separate sessions and often separate people. Where a declared relationship exists you can reason about the household; where it does not, do not infer it. Being explicit about that distinction is both the compliant position and the accurate one.
Report on cohort progression, not monthly enquiries
Enquiry volume in October tells you nothing without knowing what share of last year's October cohort enrolled. Cohort reporting is the only view that makes a long cycle legible, and it is what surfaces melt between deposit and arrival.
What holds education providers back
The buying window is fixed and narrow
Application deadlines are set externally. A campaign that hasn't stabilised by the time the window opens has effectively failed for a year, which makes the usual 'launch and optimise' rhythm unworkable.
The decision maker isn't the user
Parents fund, students attend, and for corporate training an L&D lead buys for people who didn't ask. Content aimed at one of three loses the other two.
Outcomes data is the buying criterion
Completion rates, employment outcomes and salary uplift decide enrolment far more than campus photography. Most providers hold that data and don't publish it.
Student data carries real restrictions
Education records are regulated, and tracking that ties a prospective student to a specific programme page is more sensitive than most marketers assume.
The full scope.
Everything in a analytics & measurement engagement, applied to education & edtech.
Measurement audit and event map
Every event, where it fires, what it means and whether it correlates with revenue. Most accounts are optimising toward an event chosen because it was easy to implement rather than because it predicts money.
Server-side collection with deduplication
Events sent from your own infrastructure with a shared identifier so browser and server transmission cannot double-count. Running both without that identifier inflates conversions by a large margin, and teams celebrate it.
Consent-aware implementation
Collection that respects consent state by design rather than by a banner bolted on afterwards. This is a legal requirement in several markets and, done properly, recovers more usable signal than the non-compliant version most sites are running.
One revenue number, from your own systems
Blended efficiency calculated from your actual revenue and total spend. It cannot be double-counted or inflated by a platform, which is why it is the only paid metric that has not degraded.
Geo holdout test design and analysis
Switch a channel off in matched regions, run it past the purchase cycle, compare against control. It costs real revenue in the test markets and it is the only method here that answers the causal question.
Reporting a finance team will sign
A single view reconciling marketing-reported performance against booked revenue, with the methodology written down so nobody can quietly change models between quarters.
How this runs.
Audit and reconcile
Week 1–2We map every event and compare summed platform-claimed revenue against what your finance system actually recorded. The size of that gap is usually the moment the project gets prioritised.
Rebuild collection
Week 2–4Server-side transmission, deduplication, consent handling, and re-pointing optimisation at the event that correlates with revenue rather than the one that fires most often.
Validate against reality
Week 4–5A parallel run comparing new collection against your order data, because a tracking implementation nobody reconciled is a hypothesis rather than a measurement.
Design the holdout
Week 5–6Matched test and control regions, a run length set by your purchase cycle, and a pre-registered analysis so the result cannot be reinterpreted afterwards.
Read the result and reallocate
Post-testThe incremental figure usually differs sharply from the attributed one, most often on brand search and remarketing. That difference is the budget decision.
Hand over the documentation
OngoingEvent map, methodology and test protocol written down and yours. If you leave, the implementation does not stop making sense.
Education & EdTech results, in detail.
Full case studies with the numbers, the mistakes, and the recommendations clients didn't want to hear.
Scoped like the core service, no surcharge.
Every engagement is quoted from your actual brief. There's no vertical surcharge for this combination — request a quote and we'll scope it properly.
Audit
Teams who suspect the numbers are wrong and need to know how wrong.
Scoped to your brief
- Full event and tag audit
- Platform vs actual revenue reconciliation
- Consent and compliance review
- Prioritised remediation plan
- Findings session with your team
- Documentation yours to keep
Rebuild
Companies acting on data they cannot currently defend.
Scoped to your brief
- Everything in Audit
- Server-side collection implementation
- Deduplication and consent handling
- Conversion event re-mapping
- Parallel validation against order data
- Blended efficiency reporting
- 60 days of post-launch support
Measurement partner
Accounts where testing needs to be continuous rather than a project.
Scoped to your brief
- Everything in Rebuild
- Quarterly geo holdout programme
- Ongoing reconciliation and QA
- Incrementality-informed budget guidance
- Board-ready reporting pack
- Named analytics lead
All engagements start with a free audit. Prices exclude media spend, which you pay directly to the platforms on accounts you own.
Education & EdTech questions, answered straight.
It makes individual-level attribution inappropriate rather than measurement impossible, and the distinction matters. Aggregate cohort analysis, geo holdout tests and channel-level reporting all work without tracking any individual across the cycle — and they answer the budget question better than last-touch attribution would even if you were permitted to run it. The constraint pushes you toward the method you should be using anyway.
Let's talk about your growth constraint.
The student browses on a phone and the parent researches costs on a laptop. Your analytics sees two unrelated visitors and credits whichever converted.
Our commitment: The audit is fixed-fee and the findings are yours regardless — including if the conclusion is that your measurement is fine and you should spend the money elsewhere.