What is client-side tracking?
Client-side tracking is the usual way websites measure visitors. For help with set-up, see our analytics and tracking set-up service. "Client" here means the visitor's browser on their phone or laptop. Small scripts called tags load with your page. When someone views a page, clicks a button or fills in a form, each tag sends that event straight to its own tool. Examples are Google Analytics 4 (GA4), Google Ads, the Meta Pixel and LinkedIn.
Most businesses manage these tags through Google Tag Manager (GTM), a free tool that adds and changes tags without a developer editing the website code each time.
Key attributes of client-side tracking
- Easy to start. Most tools give you a tag to paste, or a ready template in Google Tag Manager.
- Rich browser detail. Tags see the page, the screen size, the button clicked and the ad the visitor came from.
- Depends on the browser. If the browser blocks a tag, deletes a cookie early or the visitor leaves before the tag loads, the event is lost.
- Each tool takes its own copy. Every tag sends data to its own company, and you have little control over what each one collects.
What client-side tracking misses
Browsers have become stricter. Apple's Safari, through a feature called Intelligent Tracking Prevention, caps cookies created by page scripts at seven days (WebKit, February 2019). So if someone clicks your ad, leaves, and comes back after ten days to enquire, the enquiry may not be linked to the ad. Ad blockers also stop many common tags.
Chrome is different. In April 2025, Google said it would not roll out a new prompt for third-party cookies, and users keep choosing in Chrome's settings. So the change is not one big switch-off. It is many smaller gaps that add up, browser by browser. We look at what this means for marketers in adapting to a cookieless future.
What is server-side tracking?
Server-side tracking moves part of the work from the browser to a server. The browser sends one stream of events to a server you control, usually on a sub-domain of your own website such as data.yourbrand.com. That server checks the data, removes what shouldn't be shared, adds what's missing, and then forwards it to Google, Meta and other tools.
The most common way to do this is Google Tag Manager's server-side tagging. Google describes it as processing data "on a server you control, rather than in the user's browser." The other common route is a direct server connection to an ad platform. Examples are Meta's Conversions API (an API, or application programming interface, is a way for two systems to send data to each other) and Google Ads offline conversion imports. Both send events from your website's back-end or your CRM.
Key attributes of server-side tracking
- You control the data. Google notes that only you have access to the data in the server until you choose to send it on. You decide what each tool receives.
- More complete key events. Purchases and form submissions recorded by your own system don't depend on a tag loading in time.
- Offline events. Your sales team marks a lead as qualified, or closes a sale on the phone. That result can be sent back to Google Ads and Meta, so they learn what a good lead looks like.
- Lighter pages. With fewer tags in the browser, pages can load faster.
- More work. You need a server, a domain set-up, testing and someone to look after it.
Server side tracking vs client side tracking: when to use which
Three questions decide it: what you need to measure, who will run it, and how you handle consent. What is server side tracking? It sends your data first to a server you control, which checks and cleans it before passing it to tools such as Google and Meta. Client-side tracking sends it straight from the visitor's browser. Server side tagging vs client side tagging trades control and completeness against cost and set-up effort. (PromotEdge, 6 November 2026.)
Analytics objectives
If you mainly want to know which pages people read, client-side GA4 is enough. Now say you spend a lot on Google and Meta ads and judge them on leads or sales. Then the ad platforms need complete conversion data, and server-side tracking starts to pay for itself. It matters most when your real result happens later, such as a site visit for a flat, a test drive or a meeting with a business buyer.
Engineering resources
Client-side tags can be managed by a marketer in Google Tag Manager. Server-side tracking needs someone who can set up the server, the sub-domain and the consent rules, test every event, and keep it running. If nobody will look after it, a broken server set-up is worse than a working browser set-up.
Privacy concerns
Both methods need a lawful basis, usually consent, before you collect and use personal data. Server-side tracking can make privacy easier to control. You can strip phone numbers or emails before data leaves your server, or send them only in hashed (scrambled) form where the platform supports it. It must respect the visitor's choice. If someone declines tracking, the server shouldn't send their data either.
| Your situation | What we'd suggest |
|---|---|
| Small website, little or no ad spend | Client-side GA4 and Google Tag Manager, set up properly |
| Steady Google or Meta ad spend, judged on leads | Hybrid: browser tags plus Meta Conversions API and Google enhanced or offline conversions |
| Online store with many daily orders | Server-side tagging for purchases and key events, with deduplication |
| Long sales cycle (real estate, selling to businesses, automotive) | Send qualified leads and sales from your CRM back to the ad platforms |
| Healthcare, finance or other sensitive data | Server-side, so sensitive fields can be removed before anything is shared; take legal advice |
How does Meta's Pixel work with the Conversions API?
Meta recommends using both together, which it calls a "redundant setup". The Pixel sends events from the browser; the Conversions API sends the same events from your server. To stop one purchase counting twice, both must carry the same event name and the same event ID. Meta then keeps one and drops the duplicate, as long as the second copy arrives within 48 hours of the first.
Getting this right is most of the value. A set-up that double-counts makes your ads look better than they are; one that drops events makes them look worse. Either way, money goes to the wrong ads. This is core work for our Meta ads and Google Ads teams.
What makes most companies shift to server-side tracking?
- Lost conversions. Browser limits and ad blockers mean some enquiries never reach the ad platforms.
- Numbers that don't match. GA4, Google Ads, Meta and the CRM all show different lead counts.
- Ad platforms that learn from bad data. Automated bidding works only as well as the conversions it is fed.
- Offline sales. Many Indian businesses close deals on the phone, on WhatsApp or at a showroom. Only a server or CRM connection can report those back.
- Privacy rules. With the DPDP Rules notified on 14 November 2025 and phased in over 18 months, companies want more control over what personal data leaves their systems.
If your lead numbers don't match across tools, the fix usually starts with one source of truth, often your CRM. Our marketing automation and CRM work connects the two.
Is server-side tracking worth it?
It is worth it when the extra accuracy changes how you spend money. A rough test: if you spend enough on ads that a 10% better conversion signal would save more than the server and upkeep cost each month, it is worth doing. If you spend very little on ads, fix the basics first.
The running cost is mostly hosting. Google's Cloud Run guide estimates about US$45 a month per server and recommends running at least two, to reduce the risk of losing data if one fails. Busy sites need more. Set-up and upkeep fees depend on how many events, platforms and websites are involved, and whether your CRM needs connecting.
When you compare quotes, ask each provider four things. Which events will be sent, and to which platforms? How will duplicates be removed? How will consent be handled? Who fixes it when a website change breaks tracking?
Server-side tracking vs cookies: does it replace them?
No. Server-side tracking still uses cookies, but the difference is who sets them. A cookie set by your own server, on your own domain, is treated differently by browsers from one created by a script in the page. Server-side tracking also lets you send data that doesn't depend on a cookie at all, such as a confirmed order from your database. It does not remove the need for consent.
Common mistakes
- Counting the button click, not the confirmed submission. Track the thank-you step or the server's confirmation, not the click on "Submit".
- No deduplication. Sending the same event from the browser and the server without a shared event ID doubles your conversions.
- Ignoring consent. Sending data from the server for visitors who declined tracking breaks both the law and their trust.
- Set and forget. A website update can break a tag or a server event without anyone noticing. Check key events every month.
- Judging ads on the wrong number. Platforms each claim credit in their own way. Judge performance marketing on enquiries and sales in your own records.
Want this set up and tested properly? See our analytics and tracking service.
