Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Specialist service · server side tracking setup

Server-side tracking & CAPI

On Google Cloud Run in an Indian region such as asia-south1 (Mumbai) or asia-south2 (Delhi), or on a managed host like Stape, mapped to a first-party subdomain such as track.yourbrand.in.

Performance Marketing practice: abstract red and ink artwork from the Red Balloon reel

A server side tracking setup moves your tags out of the visitor's browser and into a container you control, which usually improves how well Meta, Google and other platforms match conversions. This page is for D2C brands and lead-generation businesses seeing doubled purchases in Ads Manager, missing events on Safari, or weak Event Match Quality scores. We design the event list, consent handling and hosting, build and test the container, then monitor uptime, latency and cost. The most common silent failure is a site release that renames dataLayer values, so we alert on it. Server side tracking setup cost depends mainly on event volume, hosting choice and the number of destinations, and the container sits in your own cloud account.

When server-side tracking is not worth it yet

Server-side tagging is not the right first step for every business. If your browser tags are still broken, with duplicate purchases or missing events, moving them to a server copies the mess to a new place. If you have low traffic and spend little on ads, the platform gains may not justify the hosting and maintenance. And if nobody on your side or ours will watch the container, it will drift.

We check these conditions before recommending a server side tracking setup. Often the right order is to fix browser tags and GA4 first, add Meta's Conversions API or Google's enhanced conversions through a simpler integration, and move to a full server container once volume and budget make it pay. We would rather tell you to wait than sell you a container that nobody will maintain.

Sending CRM outcomes back to the ad platforms

For lead businesses, the most valuable server events often happen after the website. A form fill becomes a qualified lead, a site visit or a sale days or weeks later, inside your CRM. Sending those stages back to Meta through the Conversions API and to Google Ads as offline conversions lets bidding optimise for leads that turn into revenue rather than for anyone who submits a form.

This needs a shared identifier, such as a click ID or hashed contact details captured with consent at the form, stored in the CRM and sent with each later stage. We map your pipeline stages, decide which ones the platforms should optimise for and automate the upload from CRMs such as HubSpot, Zoho CRM, LeadSquared or Salesforce.

What your developers and platform need to provide

The server container is only as good as the data your site sends it. We give your developers a short contract: which events fire, which values each carries, and which names must not change without notice. For custom sites that is a dataLayer spec. For Shopify, Shopify now expects checkout tracking to run through its Customer Events and web pixels rather than custom scripts on checkout pages, so the design starts there.

Your team also provides the infrastructure pieces: a cloud billing account in your name, DNS access to create the tracking subdomain and a contact who approves consent wording. Everything is documented in your repository or shared drive, so a new developer can understand the setup without calling us.

Where this works

Real-world situations we're built for

Illustrative · not a client
D2C apparel (Delhi)

Pixel and Conversions API both send purchases; Ads Manager shows doubles

What we'd do
event_id deduplication, server-side GTM Meta tag, Event Match Quality fixes
What moves
Duplicate purchases down, Event Match Quality up; tracked as duplicate purchase rate before and after, over a fixed period
Real estate portal (Gurugram)

Lead events go missing on Safari and some browsers

What we'd do
Server-side GTM on a first-party subdomain, consented server lead events
What moves
Gap between recorded leads and CRM count down
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Design

1 week

Events, consent, hosting choice, cost estimate

You get: Architecture

We need: Cloud billing account, DNS access

Build and test

2–3 weeks

Container, tags, deduplication, QA

You get: Live server container

We need: Developer for the dataLayer

Run

Ongoing

Monitoring, updates, cost reviews; most common silent break: a site release renaming dataLayer keys, so Event Match Quality drops

You get: Health report

We need: Advance notice of site changes

A typical engagement

From first call to result

Illustrative · not a client

Bengaluru D2C nutrition brand on Shopify with GA4, Meta pixel and Google Ads tag, ₹20 lakh/month on ads

Week 1DesignEvent list, consent rules, hosting (GTM server container on Cloud Run with minimum instances above zero, or a managed host), first-party subdomainArchitecture note
Weeks 1–3BuildServer container, GA4 client, Meta Conversions API and Google Ads tags, event_id deduplicationServer container live
Weeks 3–4ValidateBrowser and server counts compared for 7 days; shared event_id checked in Events Manager Test Events; Event Match Quality; latencySign-off
OngoingMonitorUptime, cost and error logsMonthly health note
Where it startsGA4 records 82% of Shopify orders, Meta Event Match Quality rated OK, no server container
Where it endsThe brand has consent-aware server-side events. Weekly it watches GA4-to-Shopify order match, Event Match Quality and duplicate rate.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Duplicate event rateEvents sharing an event_id that were counted twice ÷ total eventsRule of thumb: under 1% of purchases double-counted; any rise after a release is rolled backMeta Events Manager and GA4Weekly
Event Match QualityMeta's 0–10 score per eventA 'Good' or better rating on key eventsMeta Events ManagerWeekly
Endpoint uptime and latencySuccessful responses ÷ requests; 95th percentile response time99.9% monthly or better (about 43.8 minutes downtime a month); p95 latency under 500 ms (rule of thumb)Google Cloud Monitoring or host dashboardWeekly
Hosting cost per million eventsMonthly hosting cost ÷ events processed, in millionsSet from month one; review as traffic growsCloud billingMonthly
Order match rateServer-recorded purchases ÷ backend ordersWithin an agreed toleranceGA4 + backendWeekly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Each releaseDeploymentVersioned container publishes with change notes; hosting defined in Terraform or the host's templatesRemoves: Repeatable, reviewable changes
When: Endpoint downUptime alertsGoogle Cloud Monitoring or UptimeRobot on the tagging endpointRemoves: No silent data loss
When: Every eventConsent enforcementConsent Mode signals passed to the server; tags gated on themRemoves: No processing without consent
Rules we work to

Standards and regulations

MeitYDPDP Act 2023

Server-side tracking does not remove consent duties; process only what your notice covers. Main duties apply from 13 May 2027.

MetaMeta Business Tools Terms

Send only permitted, hashed customer data through the Conversions API; no sensitive categories.

GoogleGoogle Ads customer data policies

Enhanced conversions data must be collected with notice and hashed.

What's changing

Platform and policy updates that affect this work

We track: Google Tag Manager server-side documentation and release notes, Meta for Developers: Conversions API changelog.

GoogleGoogle tag gateway for advertisers launched, serving Google tags from your own domain through a CDN or load balancer.

A lighter first-party option than a full server container for Google tags.

GoogleChrome kept third-party cookies instead of phasing them out.

Server-side value is data control and durability, not only cookie loss.

Before you hire anyone

Questions to ask any agency, including us

Which events will move server-side, and which stay in the browser?

Why ask

Not everything needs to move

A good answer

Event-by-event plan with reasons

How will you test that server events match browser events?

Why ask

Silent mismatches skew bidding

A good answer

Test plan, count comparisons, dedupe checks

Who maintains the container after launch?

Why ask

Tags break when sites change

A good answer

Support plan, monitoring, documentation

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How do you avoid double-counting when browser and server events both fire?

Send the same event ID with the browser and server versions of each event so platforms deduplicate them, then confirm in each platform's diagnostics that deduplication and match rates look healthy.

  • Meta deduplicates when event_name and event_id match within 48 hours. Google Ads deduplicates purchases by transaction ID, which means passing the order ID in every purchase tag.
  • Server events can carry SHA-256 hashed email and phone plus click IDs, raising match rates on Google, Meta and LinkedIn. Recheck Events Manager diagnostics a week after launch.
Does server-side tracking let us bypass consent or ad blockers?

No: server-side tagging changes where data is processed, not your legal duties. Tags still follow each visitor's consent choice under the DPDP Act and, for EEA users, GDPR.

  • It does recover events lost to ad blockers and browser limits, which is legitimate only for visitors who consented.
  • The server container can strip IP addresses, user agents and URL parameters before data reaches Google or Meta; confirm it in the outgoing requests shown in Preview mode.
  • Never forward health, financial or children's data; from May 2027, the DPDP Act requires verifiable parental consent before processing children's data.
What drives server side tracking setup cost?

Server side tracking setup cost depends on how many events and platforms are involved, whether CRM stages are sent back to Meta and Google, how much developer work the dataLayer needs, and the hosting choice. Hosting is a separate monthly cost that grows with traffic and is billed to your own cloud or host account. Ongoing monitoring is scoped separately. A Growth Audit gives you a fixed quote.

  • Events and destinations
  • CRM offline conversions
  • Developer effort
  • Hosting billed to your account
Do you provide server side tracking setup in India for lead-generation sites, not just ecommerce?

Yes. Server side tracking setup in India is just as useful for real estate, education, finance and B2B lead businesses as for online stores, because their key outcomes happen in the CRM after the form. We set up consented server events for form fills and calls, then send qualified stages back to the ad platforms, so bidding learns from leads that become customers.

  • Form and call events
  • Qualified stages from the CRM
  • Bidding on lead quality
Keep exploring

Related pages

Related

Back to the service

Analytics & attribution →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.