Category: Agency resources | Reading time: 7 min
Your clients don’t think about tracking infrastructure. They think about leads, revenue, ROAS and whether last month was better than the month before. That’s their job.
Your job is to make sure the numbers behind those conversations are real.
If your clients are running paid media without server-side tracking, a meaningful portion of their conversion data is missing. Their campaigns are optimizing on incomplete signals. Their reported performance is partly a measurement artefact. And every recommendation you make – on creative, budgets, channels, audiences – is built on a foundation that has cracks in it.
The good news: server-side tracking provides an antidote and is definitely one of the easier sells in an agency’s toolkit. Your clients just need to understand what’s at stake without it – and what changes with it. Here’s what your client needs to know.
Why agencies often don’t bring this up
Before getting into the pitch, it’s worth being honest about why this conversation doesn’t happen more often.
Some agencies don’t raise it because the client relationship is scoped tightly to campaign management and implementation work sits outside the brief. Some don’t raise it because they’re not sure how to explain it without getting into technical territory that loses the room. Some don’t raise it because fixing it requires a bit of setup work and the short-term benefit to the agency isn’t obvious.
All of those are understandable. None of them are good reasons to leave a client running on broken measurement.
The agencies that do raise it tend to find it strengthens the relationship. You’re identifying a problem the client didn’t know they had. You’re solving it. And the performance improvements that follow – more visible conversions, better optimization, cleaner attribution – make your mutual campaigns look better too.
The explanation that lands in every client meeting
If you need to explain the core issue/solution, this framing works well across most client types:
“Your tracking still relies on code running inside a visitor’s browser. The problem is that browsers, ad blockers and privacy restrictions increasingly stop that code from firing properly meaning a significant portion of real conversions never make it back to Google or Meta.
So while campaigns may be driving results, the platforms are often optimizing from an incomplete picture.
That affects your reporting – and more. It impacts attribution, audience building, optimization quality and ultimately the confidence behind marketing decisions.
Server-side tracking changes where that measurement happens. Instead of relying entirely on the browser, conversion events are processed server-to-server, making the data significantly more resilient to blockers and browser restrictions.
The result is more reliable conversion tracking, stronger optimization signals and reporting you can stand behind with greater confidence.”
And once clients understand that, the next question is usually:
“How much data are we currently missing?”
How to answer “how much are we missing?”
You probably can’t give them a precise figure before implementation – but you can give them a credible range and a way to find out.
The honest answer is: it depends on your audience. Factors that increase data loss include:
- High iPhone/Safari usage – common in consumer-facing brands, fashion, lifestyle, premium retail.
- Technically sophisticated audiences – B2B, SaaS, developer-facing products, finance.
- Younger demographics – higher ad blocker adoption rates
- Markets with strong privacy culture – Australia, Germany, Scandinavia, UK.
A useful benchmark to share: ad blockers alone are estimated to affect 25–40% of desktop users. Safari ITP and iOS ATT add further losses on top of that – the combined effect varies by audience, but for many advertisers a third or more of conversions are going uncounted.
The most compelling thing you can do is pull their GA4 data and show them the browser breakdown. If Safari represents 30%+ of their sessions, that’s a meaningful population operating in a near-opaque measurement environment under client-side tracking alone.
You can also frame it financially. If a client is spending $5,000 a month on paid media and you suspect 25% of their conversions are invisible, the algorithm is optimizing on 75% of its available signal. Even a 10% improvement in bidding efficiency from better data quality represents $500 a month in recovered value – and at that spend level, that’s meaningful. This recovered value basically pays for a year of server-side tracking. That framing lands.
The creative conversation
This is one of the most immediately persuasive angles for clients who are actively managing creative production.
Ask them: “In the last six months, have you paused or replaced any creative based on underperformance?” Almost every active advertiser has. Then ask: “How confident are you that the performance data behind that decision was complete?”
The reality is that creative decisions made on incomplete conversion data are unreliable. A video ad that looks like it’s underperforming might be converting well among Safari users whose conversions aren’t being tracked. A campaign that appears to have fatigued might still be driving results for a segment that’s invisible to the reporting.
The cost of this isn’t just the wasted creative spend on the replacement. It’s the lost performance from pulling something that was working. Server-side tracking doesn’t make creative decisions for you – but it ensures that when you make them, you’re looking at the full picture.
For clients who run regular creative production cycles, this argument alone can justify the implementation.
Handling the common objections
“We’re already using GA4, so we should be fine.”
GA4 is the destination for your data, not the mechanism for collecting it. Even a perfectly configured GA4 property receives incomplete data if the events are being fired client-side and intercepted before they arrive. GA4 server-side collection is a separate layer – it’s how events get to GA4 reliably, not what happens once they’re there.
“We have a cookie consent banner, so we’re compliant.”
Compliance and measurement completeness are different problems. A consent banner handles your legal obligations. It doesn’t fix the fact that consenting users – ones who clicked “Accept” – may still have their events silently dropped by an ad blocker or ITP before they reach your analytics platform. Server-side tracking fixes measurement for consenting users. Consent still governs who gets tracked.
“It sounds complicated (and expensive) to set up.”
It used to be. Setting up a Google Tag Manager server container, provisioning cloud infrastructure and wiring up API connections to Meta and Google manually is a significant technical undertaking. Tiide reduces that to adding one DNS record and connecting your accounts – typically live within 10–30 minutes. No sGTM experience is required and often your developer doesn’t need to be involved.
“What about privacy compliance?”
Server-side tracking doesn’t bypass consent or circumvent privacy law – it operates within exactly the same consent framework your client already has in place. If a visitor declines tracking, they aren’t tracked. What server-side tracking does is ensure that visitors who have consented are actually tracked successfully, rather than having that consent rendered meaningless by a browser silently blocking the pixel.
“What if something breaks between the switch to server-side tracking?”
Nothing switches – that’s the important distinction. Server-side tracking is additive. It runs alongside your existing client-side tracking, not instead of it. There’s no cutover, no downtime and no moment where data collection stops. If anything, the redundancy improves reliability. Campaigns stay live, pixels keep firing and the server-side layer quietly fills in the gaps. The only thing that changes is that more data arrives.
“How do we know it’s actually better?”
The improvement is visible quickly. Clients typically see reported conversion volumes increase – not because results have improved, but because previously invisible conversions are now being counted. Tiide’s dashboard makes this easy to show: you can see exactly how many events were captured server-side that would have otherwise been lost, and compare conversion counts before and after implementation in one place.
“We don’t have budget right now.”
The honest response is that the budget is already being spent – on campaigns producing results that aren’t being counted. Every month without server-side tracking is another month of incomplete conversion data feeding into bidding algorithms, another month of creative decisions made on a partial picture and another month where reported results understate what campaigns are actually producing. The share of visitors using ad blockers isn’t shrinking. Browser privacy restrictions aren’t loosening. Apple isn’t reversing ATT. Tiide starts from a low monthly cost – in most cases, the recovered bidding efficiency it enables will more than offset it. The question isn’t whether the client can afford to implement it. It’s whether they can afford not to.
How to package it as a service
There are two primary ways agencies typically structure server-side tracking commercially:
As a setup fee with ongoing management. Charge for the initial implementation, then include Tiide’s monthly cost as part of a measurement infrastructure retainer. You may choose to pass the monthly cost through directly, or mark it up to cover your time in managing the platform. Tiide offers an Enterprise Plan for agencies that includes a tiered discount structure, meaning there’s some margin available without passing unreasonable costs on to clients. This works well for agencies that want to build recurring revenue around technical services.
As part of onboarding for new clients. Make server-side tracking a standard part of your onboarding process rather than an optional add-on. Frame it the same way you’d frame pixel installation or GA4 configuration – it’s just part of how you set up properly. Again, the Enterprise Plan Tiide offers makes it straightforward to build this into a standard onboarding fee without the economics feeling stretched.
The bigger picture for your agency
There’s a broader reason to care about this beyond individual client outcomes.
The performance results your agency produces are only as good as the measurement they’re built on. If you’re reporting CPA and ROAS figures to clients based on partial data, you’re in a vulnerable position – you could lose clients who conclude the campaigns aren’t working (when they actually are, but the results aren’t visible).
Agencies that get measurement right have a structural advantage. Their recommendations are more reliable. Their results are more defensible. And their future campaigns are more impactful.
Server-side tracking is a relatively small investment – in time, in cost, in client conversation – for the measurement quality it produces. For agencies managing significant paid media budgets, it’s not really optional. It’s just a question of when you make it standard practice.
Tiide is built to make that transition as simple as possible. A single plan covers GA4, Google Ads and Meta CAPI and is live in less time than it takes to pitch a new creative idea.
