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.
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.
From ad click to measured customer
Ad click
The click ID and UTM fields are stored in a first-party cookie, written by your own server.
Sign-up
The attribution moves onto the new account, so a conversion weeks later still knows its click.
First result
The moment a user first gets value from the product is tracked as its own conversion.
Purchase
Recorded when billing sees the first active subscription, not when a thank-you page loads.
Delivery
A background job sends each conversion to Google Ads and logs the outcome in analytics.
From a clean analytics foundation to a complete server-side setup for your ad platforms.
Conversions recorded in your backend and sent to Google Ads and other ad platforms from there, so blocked scripts can't hide them.
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.
Named events for every step that matters, in PostHog or GA4, routed through your own subdomain so ad blockers don't drop them.
Tests on pages, offers and flows, including adaptive splits that send more visitors to the variant that turns into paying customers.
From first visit to paying customer, per campaign, page and plan, so you see exactly where people drop off.
Google Ads campaigns defined in version-controlled files, checked by Google before they're applied, with a stop rule for every test.
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.
The four conversions we send
Sign-up
When a new user completes onboarding.
First render
When a real user gets their first completed result.
Trial started
When billing sees a subscription in its trial period.
Purchase
When the first subscription becomes active, including a trial that converts.
Give Google the conversions it's missing, so its bidding learns from customers instead of clicks.
Funnels from visit to trial to paying customer, per campaign and per plan, including conversions that happen weeks after the click.
Purchases recorded from your backend, so they count even when a browser blocks scripts.
Measurement designed with consent in mind, email addresses hashed before they leave your server and EU-hosted analytics where possible.
Measure fewer things, but measure them properly.
The handful of events that show real progress: sign-up, first value, purchase and retention.
What's tracked today, what's missing, what's counted twice and what ad blockers hide.
Key events written in your backend, each with its own ID so it's never sent twice.
Click IDs and UTM fields stored first-party and attached to accounts and orders.
Conversions sent to your ad platforms with every outcome logged, plus checks you can run at any time.
A/B tests on the pages and flows that matter, judged on paying customers rather than clicks.
Ad platforms and analytics fed from your own backend, with proxies on your own domain and EU hosting where possible.
A clean setup for one site and one ad platform is a small project. These factors make it bigger:
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.
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.
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.
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.
Yes, as well as PostHog, Google Ads, Search Console and Meta. We pick the tools that answer your questions, not the other way round.
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.
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.
Websites that rank in every language: programmatic landing pages, hreflang, structured data, llms.txt and conversion tracking.
Read moreFrom first version to a profitable product: billing, teams, multilingual UX, hosting and the growth tooling around it.
Read moreCustom web apps and portals that are fast, secure and easy to change, from customer portals to complete platforms.
Read moreTell 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.
Typically a reply within one business day.
Useful to mention