Skip to content
Falconscale Digital
Free plan
All services

Measure

Server-side tracking & Meta Conversions API setup

Browser tracking misses more conversions every year because of ad blockers, iOS privacy features and short-lived cookies. Server-side tracking sends events from your own server, so Meta, Google and other platforms see the leads and sales your ads really bring.

Talk to us about this

What's included

Everything we take care of.

  • Server-side Google Tag Manager on your own subdomain
  • Meta Conversions API with event deduplication
  • Google Ads enhanced conversions and offline conversion import
  • Events for Microsoft Ads, LinkedIn, Snapchat and Pinterest where you advertise
  • Better match quality with hashed customer details, sent only with consent
  • Consent-aware tags with Google Consent Mode
  • Shopify, WordPress, custom website and CRM integrations
  • Testing, documentation and monitoring

Tools we work with

Platforms we know inside out.

  • Tag Manager
  • Google Cloud
  • Meta
  • Google Ads
  • Microsoft Ads
  • LinkedIn
  • Snapchat
  • Pinterest
  • Shopify

We set up and use these tools in your own accounts. Names and logos belong to their owners.

Who this is for

Businesses that spend real money on ads and need the platforms to see their results: online stores, D2C brands, lead-generation businesses like real estate, education and finance, and apps. If your Meta or Google account shows far fewer sales than your store or CRM, this is usually why.

Why browser tracking is losing data

For years, ad platforms counted results with small scripts (pixels and tags) that ran in the visitor's browser. Today a growing share of those scripts never fire or lose their memory:

  • Ad blockers and privacy browsers stop well-known tracking scripts.
  • iPhone and Safari privacy features shorten how long browser cookies last, so a visitor who buys a week later can look like a stranger.
  • Slow pages and in-app browsers (Instagram, Facebook) close before scripts finish.

The ad platform then sees fewer conversions than really happened. It optimises on incomplete data, reports a worse ROAS than the truth, and finds fewer people like your real buyers.

How we set it up

  1. Audit. We compare conversions in your store or CRM with what GA4, Meta and Google Ads report, and find where events are missing or double-counted.
  2. Plan. We agree the events that matter — purchase, lead, add to cart, sign-up — and what data each platform should receive.
  3. Server container. We set up server-side Google Tag Manager on a subdomain of your website (for example data.yourbrand.com), hosted in your own account.
  4. Platform connections. Meta Conversions API, Google Ads enhanced conversions, GA4 and other ad platforms you use — with deduplication, so a purchase seen by both the pixel and the server is counted once.
  5. Match quality. Where customers have agreed, we send hashed details such as email and phone so platforms can match conversions to ad clicks more reliably.
  6. Consent. Every tag respects the visitor's consent choice, using Google Consent Mode and your consent banner. See consent management.
  7. Testing and handover. Test orders and leads end to end, documentation of every tag, and monitoring so you hear about breakages before they cost you.

Offline and CRM conversions

For lead businesses, the real result happens later — a site visit, an admission, a sale closed on the phone. We send those outcomes back to Google and Meta from your CRM, so campaigns learn which leads turn into customers, not just which ones fill a form.

What you get

  • A documented setup in your Google Cloud, Tag Manager and ad accounts — no lock-in.
  • Reports in GA4 and ad platforms that sit much closer to your actual orders.
  • Better data for bidding, which matters most when budgets grow.

Related: GA4 and Google Tag Manager, Meta ads, Google Ads and marketing data and attribution.

What you get

What changes for your brand.

01

More conversions counted

Sales and leads the browser missed are recorded, so reports reflect what really happened.

02

Smarter ad optimisation

Platforms learn from more real conversions, which helps them find more buyers.

03

Data you own

The setup runs in your accounts, documented, with no lock-in to us.

How it works

Clear steps, no surprises.

  1. 01

    Discover

    A free call, then an audit of your business, website, channels and numbers. You get a written plan with priorities, timelines and costs.

  2. 02

    Build

    We build the website, set up WhatsApp, AI calling and tracking, create the ads and book the media — with regular check-ins and a shared project board.

  3. 03

    Launch

    Forms, calls, messages, payments and ads are tested end to end, and every print or outdoor ad is checked before it goes live.

  4. 04

    Grow

    Monthly campaigns, experiments and reporting, reviewed together, so the business keeps growing after launch.

Talk to us about Server-side tracking & Conversions API

Leave your name and number. We'll call to understand your business and send a written plan with costs and timelines — free, no obligation.

Free, no obligation. We only use your number to call you about this.

FAQ

Common questions.

Do we still need the Meta pixel if we use the Conversions API?

Yes. Meta recommends running both, with matching event IDs so the same purchase isn't counted twice. The pixel catches browser signals; the Conversions API fills the gaps.

What is server-side tracking?

Instead of every tracking script running in the visitor's browser, events go first to a server you control (usually a server-side Google Tag Manager container on your own subdomain), which then sends them to GA4, Meta, Google Ads and others. It's harder for blockers to stop, keeps cookies first-party and lets you control exactly what each platform receives.

Does server-side tracking work with ad blockers and iPhones?

It recovers much of what browser-only tracking loses, because events come from your own domain and server, and platforms can match conversions using consented, hashed customer details. It can't — and shouldn't — track people who said no to tracking.

What does server-side tracking cost to run?

Besides our setup, the server container needs hosting — on Google Cloud or a managed tagging host. The monthly cost grows with traffic; for most small and mid-sized sites it's modest. We estimate it before you start.

Is Meta's Conversions API enough on its own?

It's the most important piece for Meta ads, but most businesses also advertise on Google and use GA4. A server-side container feeds all of them from one place, with one set of rules for consent and data quality.

Measure

Works well with

GA4 & Google Tag Manager

Google Analytics 4 and Tag Manager set up properly, so every enquiry, sale and campaign is counted.

Learn more

Product analytics & experiments

PostHog, Mixpanel or Amplitude set up for apps and SaaS: funnels, retention, feature adoption and A/B tests.

Learn more

Consent & privacy-first analytics

Cookie consent, Google Consent Mode and privacy-friendly analytics, set up for India's DPDP Act and global rules.

Learn more

Marketing dashboards & reporting

Looker Studio and Power BI dashboards that bring ads, analytics, sales and CRM data into one view.

Learn more

Marketing data & attribution

BigQuery, data pipelines and attribution models that show lifetime value and profit by channel.

Learn more

Let's build what your brand needs next.

Tell us where you are — idea, launch or scaling — and we'll come back with a clear plan. The first call is free.

Book a free strategy callGet a free plan in 2 minutes