Tracking

Server-side conversions so ad platforms optimise on real sales

Send every purchase and lead from your server to nine ad platforms, with hashed customer data and the pixel's event id for deduplication.

Get started More features

Flat monthly price, no revenue tax
No annual contract
Tracking starts the minute the snippet is live

Browser pixels miss conversions: ad blockers, closed tabs, consent banners and payment pages that never load the pixel. When the platform sees fewer sales, its algorithm optimises on less data and your cost per result rises.

BrainyMetrics sends purchases and leads server-side about 30 seconds after they happen, once per integration. Events carry hashed email, phone and name where the platform accepts them, IP and user agent, the platform's click id from the person's journey, and the order value net of refunds. tracko.js watches your existing pixels, so when the browser pixel already fired the same event its event id is reused and the platform deduplicates.

The problem

What it costs to go without server-side conversions

Ad platforms optimise toward the conversions they can see. When their pixel misses purchases to blockers, cross-domain checkouts or delayed payments, the algorithm learns from a partial picture and spends your money finding the wrong people.

Phone sales, booked calls and refunds are invisible to a browser pixel entirely. Unless real outcomes are sent back from the server, the platform can never learn what a valuable customer looks like for your business.

Feed ad algorithms the sales they keep missing

Create your account, install one snippet and see it on your own leads and sales.

Flat monthly price, no revenue tax
No annual contract
Tracking starts the minute the snippet is live

Create your account

What you get with Server-side conversions

Nine platforms

Meta, Google Ads (with enhanced conversions), TikTok, Microsoft, Reddit, Snapchat, Pinterest, LinkedIn and X.

Real revenue

Sales from Stripe, Shopify, funnels and your server are sent, not just what a pixel saw.

Pixel deduplication

Event ids observed from your pixels are reused so nothing is counted twice.

Click ids from the journey

The most recent gclid, fbclid, ttclid or msclkid from the person's journey is attached, even weeks later.

Test modes

Use Meta test codes, Google validate-only, and test modes on Reddit, Snapchat and Pinterest before going live.

Activity log

Every send and its result is listed under Conversion API activity.

See server-side conversions working on your own data.

Start using Server-side conversions

Use cases

Server-side conversions in practice

Better optimisation signals

Send real purchases and leads to each platform's conversion API so bidding learns from what actually happened.

No double counting

Events are deduplicated with the browser pixel, so turning on server events doesn't inflate reported results.

Offline outcomes count

Sales closed on the phone or by invoice reach the ad platform as conversions, attached to the right click.

Start using Server-side conversions

Flat monthly price, no revenue tax
No annual contract
Tracking starts the minute the snippet is live

Why BrainyMetrics

Marketing without guesswork

What changes when every lead, call and sale is tied back to the ad that started it.

Without BrainyMetrics

With BrainyMetrics

Meta, Google and TikTok each claim the same sale, so platform totals add up to more than your bank account.

Each sale is counted once, from your own checkout data, and reconciled against what each platform claims.

Analytics gives the last click all the credit, so the ads that start journeys look like they lose money.

Seven attribution models are computed for every conversion, so you can compare first click, last click and everything between.

Phone calls and booked calls are a black box. You know they happened, not which ad caused them.

Calls and bookings are matched to the visitor's session and the ad behind it, then tracked through qualified and closed.

Ad blockers, Safari and cross-domain checkouts quietly break your data.

A first-party tracking subdomain, server-set cookies and cross-domain linking keep journeys intact.

Spend lives in one tab, revenue in another, and ROAS is a spreadsheet you rebuild every Monday.

Spend syncs hourly and sits next to attributed revenue, so ROAS, CPA and profit are on every row, down to the ad.

Ad algorithms optimise on the few conversions their pixel happens to see.

Real purchases and leads are sent back to the ad platforms' conversion APIs, deduplicated against the pixel.

Stop guessing which marketing pays.

Start using Server-side conversions

Getting started

Live on your site in four steps

No migration project and no agency retainer. Here is the whole path from sign-up to your first attributed sale.

1
Create your account
Sign up, name your workspace and pick the plan that fits. Your tracking snippet is waiting under Settings → Install.
2
Install tracko.js
Paste one snippet into your site's head, or add it with Google Tag Manager, WordPress or your funnel builder's tracking code box.
3
Connect revenue and ads
Connect Stripe, Shopify, your funnel builder or calendar, then Meta, Google or TikTok for hourly spend. Most connections take a click.
4
Watch the first sale land
The setup checklist ticks itself off as data arrives. Your next lead or sale shows up with its full journey and the ad that earned it.

Create your account

Flat monthly price, no revenue tax
No annual contract
Tracking starts the minute the snippet is live

One account

Everything else that comes with it

Tracking, attribution, calls, spend and revenue analytics share one data model, so each feature makes the others more accurate.

Multi-touch attribution

Seven models side by side, down to the ad.

First-party tracking

Your own subdomain and server-set cookies.

Call tracking

Dynamic numbers matched to the click behind each call.

ROAS and profit

Hourly spend sync joined with real revenue.

Customer journeys

Every visit, ad, order and call per person.

LTV and cohorts

Lifetime value by the channel that acquired them.

Funnels

Drop-offs and cost per step, by ad.

Revenue reconciliation

Actual vs tracked vs claimed, side by side.

Create your account and start tracking today.

Create your account

Frequently asked questions

Common questions about Server-side conversions, setup and pricing.

The fastest answer is your own data

Create an account, install the snippet and see how BrainyMetrics handles your real traffic.

Get started

Do I still need the browser pixel?

Keeping it is recommended. The server event and the pixel event share an event id, so the platform counts the conversion once and gets the most complete data.

Are offline and phone sales sent?

Yes. Any order or lead BrainyMetrics records, including ones from your payment processor, CRM or the API, can be sent.

How old can a conversion be?

Events older than 7 days are skipped for most platforms (90 days for Google Ads and LinkedIn), because the platforms reject them.

How long does setup take?

The basics take minutes: paste the snippet, connect your checkout or funnel builder, and connect your ad accounts. The setup checklist in your dashboard ticks each step off as data arrives, so you always know what's left.

Do I need a developer?

Usually not. The snippet can go in through Google Tag Manager, WordPress or your funnel builder's tracking code settings, and most revenue sources connect with a click or a webhook URL you paste. The developer guide covers the JavaScript and server API if you do have a developer.

Does the price go up as I grow?

No. Plans are a flat monthly or yearly price. We never bill a percentage of revenue or ad spend, and you can switch, pause or cancel from the Billing page without a call.

Does tracking stop if I hit a plan limit?

No. Plans limit dashboard modules and things like integrations or workspaces; tracko.js, webhooks and syncs keep collecting data, so nothing is lost if you upgrade later.

Is it privacy friendly?

Yes. BrainyMetrics supports consent modes, works with your consent banner, respects Global Privacy Control and handles sensitive form fields strictly. Data is first-party: it belongs to your workspace, not an ad network.