Skip to content
PromotEdge

Home Glossary Server-side tracking

Glossary · Analytics

Server-side trackingmeaning and examples

Your data, checked first: events go through a server you control.

Since 201565+ in-house team6 cities

Updated 9 Oct 2026

Brands we have worked with

  • Sai Angan
  • Rupa Peekaboo
  • Tea Junction
  • Zandu Vigorex
  • Fox & Mandal
  • Veedol
  • Tata Efee
  • Avadh Sugar & Energy
  • Taj Cement
  • Weichai
  • Rerasathi
  • Honest AI
  • Walton
  • Supertron
  • Balrampur Foundation
  • Fine Organics
  • Kopran
  • Bengal Aerotropolis Projects Limited
  • FIVB
  • Hanumanta Foods
  • Linc
  • Nitya Gold & Diamonds
  • Novozymes
  • PSPL
See all 122 clients
Definition

Server-side tracking sends events from your website or app to a server you control first. That server checks the data and passes it on to tools such as Google and Meta. Client-side tracking sends events straight from the visitor's browser.

Most websites use tags. These are small scripts that load in the browser and report each visit, click or form to a tool. Server-side tracking moves part of that work to a server. It is not a way around a visitor's choice. It is a way to send cleaner data that people have agreed to share.

Server-side and client-side tracking

The facts below come from our guide on server-side vs client-side tracking. We checked its sources on 4 October 2026. They are named at the end of this page.

  • Client-side: tags such as the Google Analytics tag or the Meta Pixel run in the visitor's browser. They send each event straight to their tool. It is quick to set up, but browser limits and ad blockers can stop some data.
  • Server-side: the browser sends events to a server you control, often on a sub-domain of your own site. The server checks and cleans the data, then forwards it. You decide what each tool receives.

Two common routes are Google Tag Manager server-side tagging and Meta's Conversions API. An API (application programming interface) is a way for two systems to send data to each other. Both can send events from your site's back end or your CRM. A CRM (customer relationship management software) is where your leads are kept.

Why businesses use it

  • Safari caps cookies created by page scripts at seven days, according to a WebKit post dated 21 February 2019. A visitor who returns after ten days may not be linked to your ad.
  • Offline results can be sent back to the ad platforms. Examples are a sale closed on the phone or a lead marked as qualified in the CRM.
  • Fewer tags in the browser can make pages lighter.
  • Meta recommends running its Pixel and its Conversions API together. Matching event names and event IDs let it drop duplicates. The second copy must arrive within 48 hours of the first.

A made-up example in rupees

Say a builder in Hyderabad spends ₹1,00,000 on ads in a month. This is a made-up example. The browser tag counts 40 enquiries. The CRM shows 55 real enquiries, because some visitors had blocked tags or used another browser.

  • Cost for each enquiry on the tag count: ₹1,00,000 ÷ 40 = ₹2,500.
  • Cost for each enquiry on the CRM count: ₹1,00,000 ÷ 55 = about ₹1,818.

The ad platform learns from the numbers it receives. If it sees only 40 of the 55, it learns from a smaller picture. A server link that passes on all 55 lets it learn from the whole.

What it does not do

  • It does not remove the need for consent. Our guide notes that India's Digital Personal Data Protection Rules were notified on 14 November 2025. Duties are phased in over 18 months (Press Information Bureau, 17 November 2025).
  • If a visitor says no to tracking, the server should not send their data either.
  • It is not free. Google's guide on its Cloud Run set-up estimates about US$45 a month per server. It recommends at least two. The set-up and upkeep cost more.

Common mistakes

  • Sending the same event from the browser and the server with no shared event ID. Then one sale counts twice.
  • Counting the click on a Submit button, not the confirmed form.
  • Ignoring consent.
  • Setting it up once and never checking it again. A website change can break it.
  • Moving to server-side when ad spend is small. Set up the browser tags properly first.

To tag your campaign links, read about UTM parameters. To set up tracking, see our analytics and tracking service.

Related terms

  • GTM (Google Tag Manager): a free tool that manages tags without editing the site code each time.
  • GA4 (Google Analytics 4): the tool that reports visits and events.
  • Attribution: deciding which source gets credit for a lead or sale.

Sources

  • PromotEdge guide, "Server-side vs client-side tracking" (/blog/server-side-tracking-vs-client-side-tracking/), sources checked 4 October 2026.
  • Google Tag Manager, "Introduction to server-side tagging" and "Cloud Run setup guide" (developers.google.com/tag-platform/tag-manager/server-side/intro), checked 4 October 2026.
  • Meta for Developers, "Deduplicate Pixel and Server Events" (developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events), checked 4 October 2026.
  • WebKit blog, "Intelligent Tracking Prevention 2.1", 21 February 2019 (webkit.org/blog/8613/intelligent-tracking-prevention-2-1/), checked 4 October 2026.
  • Press Information Bureau, "DPDP Rules, 2025 Notified", 17 November 2025, checked 4 October 2026.

Our beliefOur job is to impress your customers, not you.

Keep reading

Related termsand services

The expertise that fits your business, and the places we work.

Related terms
Related services
What people say

In their own words

“An aligned partner is always a welcoming step. Someone who can think deep through lines, understand the matrix of product management. Fortunate enough, PromotEdge has been a partner in progress for me. …”
Bobby SrinivasBobby SrinivasChief Manager Marketing & Brand Marketing at Utkarsh India
“As a progressive and emerging digital marketing company, PromotEdge is doing something right to enhance the experience of companies associated with them. …”
Anish Basu MallikAnish Basu MallikMarketing Executive at Unimark Group
“PRAN & PromotEdge have been working together for last 1.5 years. Throughout, the work experience is good and satisfactory. As a client, we found PromotEdge very professional and dedicated towards any project assigned to them. …”
Sharif Rezwan KabirSharif Rezwan KabirBrand Manager at PRAN RFL Group
Read all 20
No pressure. No sales pitch.

Tell us what’snot working.

Get a free growth plan Call us WhatsApp us

Or leave your number. A strategist calls you in one working day.

We use these details only to call you back. Privacy notice.

Straight answers.

  • It sends website events to a server you control first. The server checks the data and passes it to tools such as Google and Meta.

  • No. It is not a way around a visitor's choice. You still need a lawful reason to collect data, usually consent. If a visitor declines, the server should not send their data either. India's Digital Personal Data Protection Rules were notified on 14 November 2025. Duties are phased in over 18 months.

  • Yes. Meta recommends running its Pixel and its Conversions API together. Matching event names and a shared event ID let it drop duplicates. The second copy must arrive within 48 hours of the first. Without a shared event ID, one sale can count twice.

  • Hosting is the main running cost. Google's guide on its Cloud Run set-up estimates about US$45 a month per server. It recommends at least two. The set-up and upkeep cost more. If ad spend is small, set up the browser tags properly first. Move to server-side later.