Server side tracking for Meta CAPI and ad platforms.
Ad platforms optimise on what you feed them. Feed them browser pixels and you feed them whatever survived an ad-blocker. Server-side delivery sends the conversion you recorded, from your server.
No credit card required · Under 5 minutes to install
Integrations
ATTRIBUTION STACK
Everything behind every server-side conversion, delivered from your server.
SourceTrack captures the source on the first visit and keeps it tied to the lead all the way through to your CRM.
Traffic, conversions, and revenue by channel.
Know which channels drive qualified deals, not just empty clicks.
See every touch that led to the conversion.
Audit the full multi-touch discovery path before the conversion.
HOW IT WORKS
Three steps to track server-side conversions with full attribution
One script tag, no complex setup, first-party tracking.
Install the snippet
Drop one lightweight script tag in your <head> or install via Google Tag Manager. Five minutes, no engineer required.
Every visit is classified
Source, campaign, click IDs and AI referrers are recorded on the visitor’s first-party session.
Conversions keep their origin
Payments, bookings and chat leads you connect are credited back to the session that produced them.
HOW IT FITS TOGETHER
Server-side conversions end to end.
One script tag on the left, your existing stack on the right, nothing to rebuild in between.
Conversions from
Delivered server-side to
The conversion leaves your server rather than the browser, carrying a shared event id so the ad platform counts it once whether or not your pixel also fired.
WORKS WITH
Tools that pair with server-side conversions.
The tools this feature is built around.
THE DIFFERENCE
The same conversion, before and after.
Without SourceTrack
- Pixel blocked, conversion never arrives
- Platform optimises on partial data
- Browser and server events double-count
With SourceTrack
- Event sent from your server
- Optimisation runs on what converted
- Shared event id de-duplicates
FAQ
UTM and lead source tracking FAQ
Does this replace my pixel?
It does not have to. Server-side events are de-duplicated against the browser pixel using a shared event id, so you can run both and count each conversion once.
Why does server-side matter?
Ad platforms optimise on what you feed them. A browser pixel feeds them whatever survived the visitor’s ad-blocker, which is a biased sample. An event that leaves your server does not depend on the browser cooperating.
Which platforms are supported?
Meta CAPI, Google Ads, LinkedIn, TikTok, Pinterest, Microsoft and Snap.
EXPLORE PLATFORM
The rest of the SourceTrack platform.
Attribute every deal back to the click, AI referral, or ad that earned it.
SourceTrack connects your forms, bookings, and payments to first-party session journeys — so your team sees the source behind each conversion with no third-party cookies and no broken UTM fields.