In this guide
- Most objections are about legality, cost, risk and proof. Answer each with a number, a limit and a next step.
- Show the client's own gap between platform and store before you explain anything.
- Be clear about what it cannot do. That earns trust.
Pitching server-side tagging to a business owner is easier if you start from their numbers and harder if you start from the technology. This page lists the objections that come up again and again and short, honest answers. It pairs with how to pitch server-side tracking and the pitch template.
Start with their numbers
Before any meeting, compare last month's orders in the shop with the purchases in Meta and Google Ads. Put both on one slide. If the gap is 20 percent or more, you already have a reason to talk. If it is 5 percent, server-side tagging may not be the priority, and saying so builds trust.
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
The objections
- "Is it legal?"
- Server-side tracking is a technical set-up, not a way around privacy law. It still needs consent where required, and it gives you control over what each vendor receives. We set it up with your consent banner and record what we send. See GDPR and server-side tracking.
- "Is it expensive?"
- There are two costs: our fee and hosting. Hosting depends on the plan, and small sites can start on a free plan. We compare the cost with the value of recovered data after a week. See how much a server GTM costs.
- "Will it break our tracking?"
- We build it next to what you have, on a test subdomain, and compare before we switch. Tracking keeps running during the change. We also keep a backup of your containers.
- "What do we actually get?"
- More of your sales reach the ad platforms, with better matching data, so they can optimise on a more complete picture. We measure the change against your orders. We cannot promise a percentage.
- "Our last agency already did our tracking."
- Good, then we will audit what is there. Many set-ups work in the browser only. We check whether purchases also go from the server and whether they are counted once. See Google Tag Manager audit.
- "Why now?"
- Browser limits and consent rules keep reducing what browser tags see. The cost of waiting is data your ad accounts never receive. See Safari ITP.
- "Will our numbers go up?"
- Platform numbers usually rise as lost events return. That is mostly the data catching up, not the campaigns improving. We explain that before launch. See attribution with server-side tracking.
- "Who owns it?"
- You do. The domain, accounts and containers are yours, and you can export them at any time.
What not to say
- "It will increase your ROAS by 30 percent." You cannot know.
- "It removes the need for consent." It does not.
- "Nobody else does this." Others do, and the client may check.
- "It is simple." It is manageable, and it needs care.
Works with your stack
Grab a logo and throw it. These are the tools Open Tracked already talks to.
Close with a small step
Offer a one-week test on a subdomain for one platform, with a clear comparison at the end. A small, low-risk first step is easier to agree to than a project. If the test shows a gain, the larger scope follows. If it does not, you have saved the client money and kept their trust.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Frequently asked questions
What objections do clients raise about server-side tagging?
Legality, cost, risk of breaking tracking, proof of value and whether it is already done.
Should I promise an uplift?
No. Promise a measured comparison.
How do I answer "is it legal"?
It is a technical set-up that still needs consent where required, and it gives control over data.
How do I show value?
Compare platform purchases with store orders before and after.
What is a good first step?
A one-week test on a subdomain for one platform.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Blog · 5 min read