Server-side tracking

Server-side conversion tracking you can trust

Ad blockers, cookie limits and browser privacy features hide a growing share of what happens on your site. When Google Ads only sees part of your sign-ups, it learns from the wrong people. We record conversions where they actually happen, in your own backend, and send them on from there.

  • Conversions sent to Google Ads from your server, matched on hashed email
  • Click IDs and UTMs kept in a first-party cookie for 90 days
  • Every conversion logged, so you can see what was sent and why

From ad click to measured customer

  1. Ad click

    The click ID and UTM fields are stored in a first-party cookie, written by your own server.

    • gclid
    • utm_source
    • utm_campaign
  2. Sign-up

    The attribution moves onto the new account, so a conversion weeks later still knows its click.

  3. First result

    The moment a user first gets value from the product is tracked as its own conversion.

  4. Purchase

    Recorded when billing sees the first active subscription, not when a thank-you page loads.

  5. Delivery

    A background job sends each conversion to Google Ads and logs the outcome in analytics.

The conversion setup we built for Twelve Lumens.
What we can build

What we set up

From a clean analytics foundation to a complete server-side setup for your ad platforms.

Server-side conversion tracking

Conversions recorded in your backend and sent to Google Ads and other ad platforms from there, so blocked scripts can't hide them.

First-party attribution

Click IDs and UTM fields stored on your own domain and attached to accounts and orders, with the first touch kept and the latest click updated.

Product analytics

Named events for every step that matters, in PostHog or GA4, routed through your own subdomain so ad blockers don't drop them.

Experiments and A/B tests

Tests on pages, offers and flows, including adaptive splits that send more visitors to the variant that turns into paying customers.

Funnels and dashboards

From first visit to paying customer, per campaign, page and plan, so you see exactly where people drop off.

Ad campaigns as code

Google Ads campaigns defined in version-controlled files, checked by Google before they're applied, with a stop rule for every test.

Proof, not promises

The measurement setup behind our own products

Twelve Lumens records four conversions in its own backend: sign-up, first render, trial started and purchase. Each one is written to a ledger, delivered to Google Ads by a background job through the Data Manager API, matched on the click ID and a hashed email address, and mirrored to analytics with the outcome. Nothing reaches Google without that record.

Its Google Ads campaigns are YAML files: validated by Google in a dry run, synced to the live account and given a stop rule when they're a test. Postcrest runs adaptive experiments that shift traffic towards whichever variant brings in paying customers, and tests its search titles against Search Console data.

  • A conversion ledger with one row per event, so nothing is counted twice
  • Attribution cookies written by the server, which keeps the full 90 days in Safari too
  • Analytics routed through a Cloudflare Worker on a first-party subdomain
  • No Google tag or tag manager needed for the ad conversions
  • Bandit experiments that optimise for paying customers, not clicks

The four conversions we send

  1. Sign-up

    When a new user completes onboarding.

  2. First render

    When a real user gets their first completed result.

  3. Trial started

    When billing sees a subscription in its trial period.

  4. Purchase

    When the first subscription becomes active, including a trial that converts.

Server-side conversions for Twelve Lumens. Renewals aren't uploaded, and admin accounts never count.
server-side conversions per journey
4
of first-party attribution
90 days
ad campaigns defined as code
7
tag managers needed for ad conversions
0
Who it's for

Who we set this up for

Companies running Google Ads

Give Google the conversions it's missing, so its bidding learns from customers instead of clicks.

SaaS and subscription businesses

Funnels from visit to trial to paying customer, per campaign and per plan, including conversions that happen weeks after the click.

Webshops

Purchases recorded from your backend, so they count even when a browser blocks scripts.

Privacy-conscious teams

Measurement designed with consent in mind, email addresses hashed before they leave your server and EU-hosted analytics where possible.

How it works

How we set it up

Measure fewer things, but measure them properly.

  1. 1

    Define what matters

    The handful of events that show real progress: sign-up, first value, purchase and retention.

  2. 2

    Audit what's there

    What's tracked today, what's missing, what's counted twice and what ad blockers hide.

  3. 3

    Record events on the server

    Key events written in your backend, each with its own ID so it's never sent twice.

  4. 4

    Attribute properly

    Click IDs and UTM fields stored first-party and attached to accounts and orders.

  5. 5

    Deliver and verify

    Conversions sent to your ad platforms with every outcome logged, plus checks you can run at any time.

  6. 6

    Experiment

    A/B tests on the pages and flows that matter, judged on paying customers rather than clicks.

Tooling we use

Ad platforms and analytics fed from your own backend, with proxies on your own domain and EU hosting where possible.

  • Google Ads API
  • Data Manager API
  • GA4
  • PostHog
  • Google Search Console
  • Meta Pixel
  • Cloudflare Workers
  • Ruby on Rails
  • Solid Queue
  • Sentry
Cost & timeline

What does a conversion tracking setup cost?

A clean setup for one site and one ad platform is a small project. These factors make it bigger:

Number of platforms
Google Ads, Meta and analytics tools each need their own events, matching and checks.
Server-side work
Sending events from your backend means changes in your application, not just a script in the page.
Current state
Untangling an existing setup with duplicate or broken tags takes time before anything new is added.
Dashboards and experiments
Standard reports, or custom funnels and an experiment setup on top.
Consent and privacy
Consent signals and data rules for each country you advertise in.
FAQ

Questions about server-side tracking

What is server-side conversion tracking?

Instead of relying on a script in the visitor's browser, your own server tells the ad platform that a conversion happened. Ad blockers and browser privacy features can't block that, so your reports and the platform's bidding see more of what really happened.

How much does server-side tracking cost?

It depends on the number of platforms, how much has to happen in your backend and the state of your current setup. After a free intro call you get a written scope and estimate.

How long does it take to set up?

Tracking works the moment it's live. Ad platforms need some conversions before their bidding adjusts, so the effect on campaigns follows in the weeks after. The estimate after the intro call includes a timeline per phase.

Is server-side tracking allowed under the GDPR?

It can be, with the right consent and data handling. Server-side tracking gives you more control over what is sent, for example by hashing email addresses before they leave your server. Have your setup checked against your privacy policy and the rules in your markets.

Do you work with GA4?

Yes, as well as PostHog, Google Ads, Search Console and Meta. We pick the tools that answer your questions, not the other way round.

Can you fix our existing tracking?

Yes. We start with an audit of what's tracked, what's missing and what's counted twice, then fix the gaps in order of impact.

Why do conversions in Google Ads differ from our own data?

Usually because the browser tag misses visitors with ad blockers or strict privacy settings, or because conversions are counted twice. Recording conversions on the server, once per event, closes most of that gap.

Not sure which ads actually work?

Tell us which platforms you use and what counts as a conversion for you. You'll get an honest view on what you're missing and how to measure it properly.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to