Analytics and Measurement
Server-side tagging
This is the narrowest useful unit of Analytics and Measurement: recover the measurement that browser restrictions take away, where the loss is worth the cost.
What are you buying when you buy server-side tagging?
Recover the measurement that browser restrictions take away, where the loss is worth the cost. In practice that means an honest assessment of whether your data loss justifies the build and the running cost, and then the harder half: container architecture and the decision about where it runs.
Why this work exists
It is the kind of thing that gets a line in a plan and no time in a calendar.
Analytics and Measurement is the wider programme; this is the piece that gets scoped first more often than any other.
The nearest piece of work to it is finding the tracking that broke during the last release. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
Working well means the decisions downstream get made faster, because the argument about what is true has already been had.
The gap between that and where most accounts start is why this is scoped as server-side tagging rather than as a line inside something larger. Separating what a channel caused from what it merely witnessed is the usual second step once it is in place.
When this is the right work
The symptoms that point at this rather than something else:
- Measured conversions sit well below what the platforms report
- Cookie lifetimes are cutting attribution windows short
- Bidding is being fed partial data and performing accordingly
If none of those is true, something else is probably the constraint, and the Analytics and Measurement overview maps the alternatives. The usual neighbours are building a definition of a lead that both sales and marketing accept and running the holdout that tells you what attribution will not.
What the work covers
What is in scope:
- An honest assessment of whether your data loss justifies the build and the running cost. Usually quick; occasionally the thing that reopens the whole scope.
- Container architecture and the decision about where it runs, usually the first thing to show a result, so it goes early.
- Consent handling preserved server side, which is where many implementations quietly break the law. Slow, unglamorous, and the reason the rest holds up.
- Platform connections rebuilt so conversions and audiences keep working. Slow, unglamorous, and the reason the rest holds up.
How it runs
It runs in three passes. The order is not interchangeable.
Handing back the keys
Access, documentation and whatever was built end up with the client in a form they can use without us, which is the only honest definition of finished.
Before anything is changed
Nothing moves until the current position is written down and agreed. That takes days, not weeks, and it is the only defence against arguing about whether something improved.
The first pass
The obvious problems get fixed first, in one batch, so the picture clears before the harder judgement calls have to be made against a noisy background.
What each part runs into
The specific resistance each part meets:
- An honest assessment of whether your data loss justifies the build and the running cost – in Melbourne, complicated by the fact that a decision made by somebody who never visits the site
- Container architecture and the decision about where it runs, which in Ajmer runs into a procurement step nobody accounted for
- Consent handling preserved server side, which is where many implementations quietly break the law: the Pune version of this has to deal with a measurement baseline that was never taken
- Platform connections rebuilt so conversions and audiences keep working, where a Ahmedabad engagement contends with a language mix the content has to match rather than assume
What goes wrong first
Selling it as a privacy solution. It changes where data is processed, not whether you were allowed to collect it.
It is worth stating because it is the version of this work that gets sold most often, and it fails in a way that looks like the discipline not working rather than the execution being wrong.
How it is measured
Conversion capture rate against baseline, and the quality of signal reaching your bidding platforms. That is the number the work is judged on, reported alongside whatever the business already tracks rather than instead of it.
One number, agreed, beats four that each tell a slightly different story.
What you end up with
Specifically: a working server-side setup with consent preserved, and a before and after on conversion capture.
Comes with a date and a next review, so it ages visibly instead of quietly.
How it differs by sector
What this becomes in practice depends on who it is for:
- SaaS and technology brings its own limit: product-led companies where the buyer self-educates and the trial is the sales call.
- Home and trade services, constrained by the fact that emergency intent, service-area geography, and a phone that has to be answered.
- Travel and hospitality: Aggregators hold the demand, so direct booking depends on being the specific named property. so this work has to account for that before anything else.
The industry pages carry the rest of that detail. SaaS and technology and Home and trade services are the two where this piece of work most often decides the outcome.
Common questions
Is server-side tagging worth the cost?
Where data loss is measurably hurting bidding on real spend, usually yes. Below that it is infrastructure for its own sake.
Does it get around consent requirements?
No, and implementations that behave as though it does are the ones that create problems. Consent still governs what you may collect. Anyone scoping this ends up comparing Agentic Commerce for Healthcare and clinics against AI Automation and Workflows for Healthcare and clinics sooner or later.
How do we know this is the right piece of work?
The signals above are the test. If none of them describes your situation, something else is the constraint, and saying so is more useful than selling this. For the decision, Lifecycle and Email in Bengaluru. For the implementation, Local SEO in Bengaluru.
What happens if it does not work?
We report that it did not, with the reason. Conversion capture rate against baseline, and the quality of signal reaching your bidding platforms agreed before the work starts makes that an honest conversation rather than an argument. This connects directly to Meta Ads management, and less obviously to Retargeting and audience systems.
Who does the work on server-side tagging?
A practitioner rather than an account manager, and the same person throughout. Conversion capture rate against baseline, and the quality of signal reaching your bidding platforms is their number, which is the only arrangement under which the reporting stays honest. Surat is written for the practitioner, Sydney for whoever is paying.
Ask about server-side tagging
Describe the gap between what the site does and what it should. We will name the likely cause.
See the gaps before you spend against them
Give us the context and we will give you the order of work, including the parts you can do yourself.