# Server-side tracking that sends Google and Meta your real conversions

Server-side tracking sends conversion events from your server to the ad platforms, so they do not depend on the visitor's browser alone. Goldenroz sets up server-side tagging, Meta Conversions API, Google enhanced conversions and offline conversion imports from your CRM. Daniel Rozin defines what to measure and Shai, our CTO, builds it. It is included in the management fee for paid media clients and available standalone as a fixed-price project quoted after a scoping call.

**Included for managed clients. Standalone: fixed price after a scoping call**

Updated: 2026-11-13. By Daniel Rozin.

## Who this is for

- Stores where Google and Meta report noticeably fewer or more purchases than the order system.
- SaaS and B2B companies that want ad platforms to optimize toward qualified pipeline in the CRM.
- Companies that changed platform, checkout or consent banner and have not trusted the numbers since.
- Marketing teams whose tracking requests sit in a developer backlog.

## What is included

- **Tracking audit:** Every tag, pixel and conversion action listed, with duplicates, missing events and wrong values marked, and platform counts compared with real orders or leads.
- **Server-side tagging:** A server-side Google Tag Manager container on your own subdomain, or direct server integrations where they fit your stack better.
- **Meta Conversions API:** Purchase, lead and funnel events sent from the server with event IDs for deduplication against the pixel, plus hashed customer parameters to raise match quality.
- **Google enhanced conversions:** Hashed first-party data sent with web conversions and leads, with consent mode configured to match your banner.
- **Offline conversion tracking:** CRM stages such as qualified lead, opportunity and closed deal sent to Google Ads and Meta with click identifiers and values, on an automatic schedule.
- **Customer Match and audience sync:** Customer lists pushed to the platforms automatically for exclusions, retention and lookalike seeds.
- **GA4 setup:** Event structure, e-commerce schema, key events, cross-domain settings and the BigQuery export, cleaned up so GA4 agrees with the rest.
- **Monitoring and documentation:** Alerts when event volume drops, and a written map of every event, its trigger and its destination.

## How the work runs

1. **Scoping call (30 to 60 minutes):** We review your site platform, CRM, consent setup and which conversions matter. You get a fixed quote with a timeline.
2. **Audit and plan (Week 1):** We document the current state and agree the event plan: names, parameters, values and deduplication keys.
3. **Build in staging (Weeks 2 to 3):** Shai builds the server container, API connections and CRM sync, and tests them against real orders or leads.
4. **Release and verify (Weeks 3 to 4):** The new setup runs beside the old one until counts agree. Then the old tags are removed and bidding switches to the new conversions.
5. **Monitor (Ongoing):** Managed clients get continuous monitoring. Standalone projects end with documentation and alerts handed to your team.

## What server-side tracking changes

Standard tracking runs as JavaScript in the visitor's browser. Ad blockers, browser privacy features, short cookie lifetimes and slow page loads stop some of those events from reaching Google and Meta. The size of the loss varies by audience and device mix.

With server-side tagging, the event goes from your site to a server you control and from there to each platform. First-party cookies set by your own server last longer, fewer requests are blocked and you decide exactly which data each vendor receives. Pages also load fewer third-party scripts.

It does not remove the need for consent. Events are sent according to the visitor's choice, and consent mode passes that choice to Google. Server-side tracking recovers data you are allowed to collect and were losing for technical reasons.

## Meta Conversions API and Google enhanced conversions

The Meta Conversions API, also called the Facebook Conversions API, lets your server report events directly to Meta. Run together with the pixel, each event carries a shared ID so Meta counts it once. Meta scores how well events match to user accounts as event match quality, and hashed email, phone and click ID raise that score.

Google enhanced conversions do a similar job. Hashed customer data is sent with the conversion so that Google can match it to a signed-in user when the cookie is missing. Enhanced conversions for leads extends this to form submissions that close later.

Platform plug-ins for common store systems cover the basics. They often miss refunds, subscriptions, custom checkouts and margin-based values. Those cases are where an engineer is needed.

## Offline conversion tracking from your CRM

For any business that closes sales after the click, the form fill is a weak signal. Offline conversion tracking tells the ad platforms which leads became qualified opportunities and customers, and what they were worth.

The setup captures the click identifier with each lead, stores it in the CRM and sends it back when the lead changes stage. We build this as an automatic sync, with retries and logging, so no one uploads spreadsheets. Bidding then targets the stage that predicts revenue. See how this applies to [SaaS](https://goldenroz.com/ppc/saas/) and [B2B](https://goldenroz.com/ppc/b2b/).

Conversion tracking setup is also the base for reporting. Once events are right, [marketing analytics](https://goldenroz.com/marketing-analytics/) can compare platform numbers with the truth.

## What backs this up

- **Built by a named engineer:** [Shai](https://goldenroz.com/about/shai/), our CTO, builds the tracking. He has put offline conversions and Customer Match for Google Ads, Meta Conversions API, TikTok Events API, GTM and phone-call attribution into production.
- **Defined by the media buyer:** Daniel Rozin specifies which events and values the bidding needs, so the build serves campaign performance.
- **Fixed price before work starts:** Standalone projects are quoted as a fixed price with a timeline after the scoping call. Managed clients pay nothing extra.
- **You own the setup:** Server containers, cloud project, tags and code are created in your accounts, with documentation.

## What it costs

Tracking is part of paid media management. As a standalone project it is fixed price. Server hosting is billed by the cloud provider to your own account.

- Tracking setup and upkeep for managed clients: Included (Part of the $5,000 a month or 5% fee)
- Standalone tracking project: Fixed price (Quoted after a scoping call)
- Server hosting: At cost (Paid to the cloud provider from your account)
- Scoping call: $0 (Free)

## Who it is not for

- Attempts to track people who declined consent. We build within consent rules.
- Sites with too little traffic for the platforms to use the added signal.
- Legal advice on privacy law. We implement what your counsel approves.

## Questions buyers ask

### What is server-side tracking?

Server-side tracking sends conversion events from a server you control to platforms such as Google and Meta. Browser-only tracking sends them from the visitor's device. The server route is less affected by ad blockers and browser privacy limits and gives you control over what data is shared.

### Do we still need the pixel with the Conversions API?

Meta recommends running both. The pixel captures browser signals and the Conversions API fills the gaps from the server. A shared event ID makes sure each conversion is counted once.

### How much does a server-side tracking setup cost?

For clients on our paid media management it is included in the fee. As a standalone project we quote a fixed price after a scoping call, based on your platform, number of events and CRM integration. Hosting for the tagging server is a separate, usually small, cloud bill in your own account.

### How long does it take?

A typical web store or lead generation setup takes about three to four weeks from access to verified data. CRM integrations with custom objects or several sales stages can take longer. The quote states the timeline.

### Is server-side tracking compliant with privacy rules?

It can be, when events respect the visitor's consent choice and customer data is hashed before sending. We configure consent mode and build to the policy your legal counsel sets. Server-side tracking is not a way around consent.

### Does it work with Shopify, WooCommerce and custom sites?

The approach works on any platform, and the method differs for each. Hosted stores limit what can run in checkout, so events often come from webhooks or the order API. Custom sites allow direct server integrations.

### Will our reported conversions go up?

Usually the platforms see more of the conversions that already happened, and duplicates are removed, so counts can move in either direction. The aim is agreement with your order or CRM data. Better data then improves bidding over the following weeks.

---
Page: https://goldenroz.com/conversion-tracking/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
