Tax and accounting
54% better lead quality after using LeadJourney for marketing
Karsten Guhr
Managing Director
Read the storyServer-side tracking
Server-side tracking that counts every conversion, not just the browser's.
Every event goes from your own server to Meta, Google, LinkedIn and Microsoft, deduplicated against your pixel and matched to your CRM.
- Runs on your own tracking domain
- 95%+ of conversions captured
- Live in 21 minutes, no developer
Rated by teams that stopped losing conversions
- Trustpilot4.9 out of 5 on Trustpilot
- G25.0 out of 5 on G2
- Capterra5.0 out of 5 on Capterra
Server-side tracking at
Same site, same 30 days, two ways of counting
Your workspace
Capture by eventBrowser pixel against the first-party server-side layer, last 30 days
What the pixel counted
316ad blockers, iOS and a declined banner took the rest
316ad blockers, iOS and a declined banner took the restWhat the server recorded525conversions, first-party and deduplicated
Recovered+209 conversions
EventPixelServer-sidePixel missed
PixelServer-sidePixel missedPageView8,42012,96035%
Lead23638839%
Booked call6110441%
Purchase193342%
Conversions are the Lead, Booked call and Purchase rows. The further from the click, the more the pixel lost, so the algorithm optimises on four conversions in seven.
The definition
What is server-side tracking?
In short
Server-side tracking sends conversion events from your own server to the ad platforms and analytics tools, instead of from the visitor's browser. The events are collected on a first-party domain (a subdomain of your own site), so ad blockers, iOS and Safari cookie limits and a blocked pixel no longer decide which conversions Meta, Google and your CRM get to see.
Run on your own domain
The tracking request goes to a subdomain you own, so the browser treats it as first-party and neither blocklists nor third-party cookie limits apply to it. The glossary entry has the longer version.
Record the event on the server
The conversion is written when the request reaches the server, not when a script finishes in the browser, so a blocked pixel or a declined cookie no longer decides whether it exists.
Forward it server to server
Events leave through the Meta Conversions API, Google Enhanced Conversions, the LinkedIn Conversions API and Microsoft Ads offline conversions, with an event ID that deduplicates them against your pixel.
Keep the person behind the event
A server-side event that cannot be joined to the deal is still only a count. The layer has to hold the click ID until the deal closes and send the outcome back.
Why the browser pixel loses conversions
The pixel counts conversions in the one place that has learnt to stop it: the browser.
A browser pixel has to survive an ad blocker, a consent banner, Apple's tracking prevention and its own JavaScript before it counts anything. Together these can take up to 40% of conversions out of the picture.
- Ad blockers stop the script before it runs. A large share of B2B visitors browse with one, and for them the pixel never loads, so their conversions never exist in the platform.
- Safari and iOS cap the cookie at seven days. A visitor who clicks on Monday and books a call the week after looks like a new, unattributed person.
- The consent banner holds the pixel until the visitor agrees, and a share of visitors decline or leave the banner unanswered.
- App Tracking Transparency blinds Meta on iOS. An opted-out iPhone sends the platform nothing it can match the click to.
- A third-party request fails quietly. A slow script, a strict content security policy, a browser extension, a dropped connection: each one loses the event with no error anywhere.
- The events that do arrive carry less to match on. Stripped of identifiers, a pixel event reaches Meta or Google with a low match quality, so even a counted conversion earns partial credit.
The platform then reports fewer conversions than you got and optimises on the ones it saw. The CPA that climbs is a data problem, not an ad problem.
Watch it
What the browser never sent you
Why iOS and the ad blockers hide a large share of conversions, and what server-side tracking puts back.
45 secondsAll videos
Case studies
What changes once the attribution is right
One measured result per customer, with the person, the role and the company behind it.
SEO agency
€500k MRR reached profitably, scaling an SEO agency on performance marketing
Nikita Yatsun
Managing Director
Read the story
Klickkraft GmbH
Business coaching
€10-20k in monthly Meta spend, tied to qualified leads and revenue per ad
Florian Buck
Managing Director
Read the story
LinkedIn growth agency
2x customer retention, once every LinkedIn touchpoint was tracked to revenue
Marc Richard
CEO
Read the story
Digital publishing
Which article produced the lead and the revenue, across AI and organic search
Andreas Malkow
CEO & Head of PR
Read the story
SEO and GEO agency
Proven ROI on every retainer, from organic and AI search leads through to revenue
Philipp Nessmann
Managing Director
Read the story
Getreach
Backlinks marketplace (SaaS)
How the data moves
The click comes in first-party. The conversion goes out server to server.
The browser talks to your own subdomain, so the event is recorded before an ad blocker or a cookie limit can touch it. From there it is deduplicated against your pixel, matched to the person in your CRM, and sent back through each platform's API.
Ad platforms and your website
- Meta Ads
- Google Ads
- LinkedIn Ads
- Microsoft Ads
- Your website
LeadJourney
Recorded on your own server
What reaches the platforms and the CRM
- Form leads
- Booked calls
- Qualified deals
- Closed revenue
Matched to the record in your CRM
and 100+ more by webhookLeads, booked calls and closed deals returned through the conversion APIs
Integrations
Every source and every CRM, connected.
The ad platforms and channels a touchpoint can come from, and the CRMs the outcome is read back from. Open any tile for what exactly moves between LeadJourney and that tool.
Ad platforms
Spend, campaign structure and click IDs come in. Closed deals go back out as offline conversions.
- Meta Ads
- Google Ads
- LinkedIn Ads
- Microsoft Bing Ads
TikTok AdsSoon
Pinterest AdsSoon
Reddit AdsSoon
X AdsSoon
ChatGPT AdsSoon
AI search engines
The traffic your analytics still files under direct. No setup, the tracking script separates it.
CRM and sales
Lead stage and deal value flow in. Every campaign sees the revenue it actually produced.
- HubSpot
- Salesforce
- Pipedrive
- Attio
- Close
GoHighLevel
ActiveCampaign
Odoo
Patch Retention
Podium
monday.comSoon
What the layer does
Everything server-side tracking has to do, without the container.
Your own tracking domain
Tracking runs on a subdomain you own, such as track.yourdomain.com. To the browser it is a first-party request to your own site, which is why blocklists and third-party cookie limits do not apply to it.
Events recorded on the server
The event is written the moment the first-party request arrives, and the consent state travels with it, so a blocked script or a declined cookie no longer decides whether the conversion exists.
Conversions API for every platform
Events leave the server through the Meta Conversions API, Google Enhanced Conversions and offline conversions, the LinkedIn Conversions API and Microsoft Ads offline conversions. No platform tag to build per event.
Deduplication with your existing pixel
Keep the pixel running. Browser and server events share an event ID, so a conversion both of them saw is counted once and the server fills in the ones the pixel dropped.
Hashed parameters on every event
Email, phone and click ID travel hashed with each event, next to the first-party identifiers the platform matches on, which is what lifts event match quality above what a bare pixel achieves.
Matched to the deal in your CRM
A server-side event is joined to the contact and the deal in HubSpot, Pipedrive, Close or Attio natively, Salesforce and 100+ others by webhook, so the closed amount can go back to the ad.
Consent is part of the design
Server-side tracking is not a way around consent. It is a cleaner way to respect it.
Moving the request to your own server does not change what you are allowed to collect, only how reliably you collect it. First-party by default, no personal data before consent, hosted in Frankfurt, Art. 28 agreement signed.
Inside the layer
What server-side tracking looks like once it is running.
Your workspace
Event match qualityLead event, Meta Conversions API
8.9/10Event match quality5.6 before, pixel only
- Click ID (fbclid) on the event
- Hashed email
- Hashed phone
- First-party browser ID (fbp)
- IP and user agent from the server
- Event ID shared with the pixel
The pixel sent the same event with the click ID alone. Every hashed field the server adds is one more way to match.
Event match quality
Every event arrives with the parameters the platform matches on.
Open any event and see what the platform received: the click ID, the hashed email and phone, the first-party identifiers and the shared event ID. The score next to it is what Meta reports back.
- Click ID, hashed email and hashed phone on every event
- First-party identifiers set on the server, not in a cookie
- Event ID shared with the pixel for deduplication
- Match quality per event, next to the pixel-only score it replaced
Your workspace
Server event logLeaving the server, last hour
Live- LeadForm on /pricing, pixel blockedRecorded server-sideRecovered
- LeadSame form, pixel fired tooSent to Meta CAPIDeduplicated
- Booked callCalendly, Lena Vogt (Fintory)Sent to Google AdsEnhanced conversion
- Qualified leadHubSpot stage change, BuildRightSent to LinkedIn CAPIMatched
Every row carries the click ID and the hashed first-party fields, so the platform can match it to the ad.
Server event log
Watch every event leave your server and land in the platform.
A live log of every event as it leaves the server: what happened, where it came from, which platform it went to and whether the platform matched it.
- Recovered events marked as such, next to the deduplicated ones
- Source, destination and match status on every row
- CRM stage changes arriving as their own conversions
- Full logs for clicks, conversions and postbacks on every plan
Your workspace
Capture by visitor stateSame 30 days, pixel against server-side
525Server-side
316Pixel only
+66%Lift
Visitor stateBrowser pixelServer-side
Consent acceptedFull eventFull event, deduplicated
Consent declinedNothingRecorded, no personal data
Ad blocker activeNothing, script blockedFull event, first-party
iOS Safari, day 8New visitor, no click IDSame person, click ID kept
A declined banner stays declined. The server still records that a conversion happened, without the person.
Consent states
What gets recorded in each visitor state, pixel against server-side.
What each visitor state does to the count, side by side. The pixel needs a loaded script and a cookie that held, the server-side layer needs a first-party request. See GDPR compliant tracking.
- Consent accepted: the full event, deduplicated with the pixel
- Consent declined: a first-party event with no personal data until consent
- Ad blocker: a first-party request that is on no blocklist
- iOS and Safari: the click ID lives on the server, not in a seven-day cookie
Live in 21 minutes
Server-side tracking set up in three steps
No container to host, no tag manager project, no engineering ticket.
- 1About 5 minutes
Point a subdomain, add one script
Point a subdomain such as t.yourbrand.com at LeadJourney and paste one script into your site header. From that moment every event is recorded first-party on the server, on WordPress, Webflow, Shopify, Wix or a custom build alike.
- 2About 15 minutes
Connect the platforms and the CRM
Connect Meta, Google, LinkedIn and Microsoft Ads by OAuth for the conversion APIs, and your CRM for the outcomes. Native for HubSpot, Pipedrive, Close and Attio, a webhook for Salesforce and the rest.
- 3Same day
Map the events
Choose which events and CRM stages go where: the form lead to Meta, the booked call to Google, the closed deal to all of them. The existing pixel keeps running and the events are deduplicated against it from the first hour.
How it compares
The browser pixel, a container you host, and a managed first-party layer.
| What you need | Browser pixel |  Self-hosted server-side GTM (Stape) | LeadJourney |
|---|---|---|---|
| Where the event is recorded | No: In the browser, if the script loads | Yes: In a server container you host | Yes: On a managed first-party layer |
| Survives ad blockers and Safari ITP | No: Blocked, or expired within days | Yes: With a custom domain you set up | Yes: First-party subdomain, out of the box |
| Who builds and maintains it | Yes: One tag per platform | No: Container, clients, tags, triggers and updates: you or a developer | Yes: 21 minutes, no developer |
| Deduplication with the pixel | No: One count, nothing to reconcile it against | Partly: Event IDs you configure on both sides | Yes: Event ID shared automatically |
| Knows which lead became a deal | No: Stops at the browser event | Partly: Only with a CRM webhook and offline tags you build | Yes: CRM stages and closed revenue, natively |
| Hosting, consent and DPA | No: Third-party and cookie-dependent | Partly: Region you choose, custom DPA on the top plan | Yes: Frankfurt, first-party, Art. 28 DPA |
What changes
What changes once the conversion is counted on the server.
Conversions the platform can see
The leads, calls and purchases the blocked pixel dropped arrive through the conversion APIs, so the platform learns from the whole picture instead of the part that survived the browser.
Event match quality
Hashed email, phone and click ID on every event lift the match score, and a matched event is one the platform can credit and optimise on.
Cost per result
More signal per euro spent means faster learning and better targeting, which is where a lower cost per lead usually comes from.
Numbers that agree with the CRM
The platform, the report and the pipeline count the same events, so the reporting call is a decision rather than a debate about the data.
Nothing to host or patch
No server container, no cloud bill, no tag update waiting on a developer. The layer is managed and the subdomain is yours.
A vendor review that passes
Frankfurt hosting, first-party tracking and a signed DPA answer the questions legal asks first. The security page lists the controls.
Original reviews
What our customers wrote, word for word
4.9 out of 5 across 11 public reviews. Quoted as they were left, shortened only by dropping whole sentences.
- 5 out of 5 starsGoogle
“Before LeadJourney, we had no reliable tracking concept for our five-figure ad spend. We were manually building spreadsheet and CRM reports, inaccurate and time-consuming. Within two days, everything was set up. For the first time, I know exactly what I pay per lead and which campaigns actually bring in the best-qualified prospects.”
Florian BuckCEO, Klickkraft GmbH “With LeadJourney we are able to track all our leads and connect them with sales and attribution data to make better decisions. In the first month of using it we scaled from 0 to 100k revenue from paid ads only.”
GetreachBacklinks Marketplace (SaaS)- 5 out of 5 starsG2
“LeadJourney finally fixed my Marketing Analytics. It goes way beyond basic Ad Tracking Software. The Customer Journey Report saves hours of digging, and capturing everything from Offline Conversions to AI Search Tracking makes it the Best B2B Attribution Platform available.”
Sascha LenzMarketing Manager
- 5 out of 5 starsTrustpilot
“Connected LeadJourney for 2 clients, setup took literally 20 minutes each. The data became more accurate, the reports actually make sense. Now clients look at the dashboard and the 'why don't the numbers match?' questions are gone.”
Alexander SamarPerformance Marketing Agency - 5 out of 5 starsGoogle
“With LeadJourney, we have finally found a tool that provides us with the data we need to scale our performance marketing campaigns. The most important KPI is no longer lead price but cost per qualified lead.”
Steffen SiesingCEO, Bilanzmanufaktur GmbH
- 5 out of 5 starsG2
“The ability to track both online and offline conversions in one unified dashboard has given us insights we never had before. Our ROI has improved dramatically since we started integrating LeadJourney with our CRM. We're finally able to see the full customer journey, and it's been a game changer for our strategy.”
Andre WitzelFounder, Trading.de - 5 out of 5 starsTrustpilot
“The ability to seamlessly integrate data from multiple channels and see real-time insights has significantly improved our campaign results. We now focus on metrics that truly matter, like ROI and qualified leads.”
Nikita YatsunCEO, RLV Media GmbH
Read the reviews where they were left
Common questions
Server-side tracking, the questions buyers ask
What marketers want to know before they move the conversion off the browser.
What is the difference between server-side tracking and server-side tagging?
Server-side tagging is Google's name for running a Tag Manager container on a server you host, so tags fire there instead of in the browser. Server-side tracking is the broader practice: recording events on a server and forwarding them to the platforms. A self-hosted container is one way to get it. A managed layer such as LeadJourney is another, with the CRM match and the reporting included.
Does server-side tracking get around cookie consent?
No, and it should not. Moving the request to the server changes how reliably you collect data, not what you are allowed to collect. LeadJourney tracks first-party and records no personal data until consent is given, so a declined banner is respected rather than worked around. The GDPR page and the guide to GDPR compliant conversion tracking go through the details.
Do I need a developer or a server-side GTM container?
No. You point a subdomain at LeadJourney, add one script and connect the ad accounts and the CRM by OAuth. There is no container to host, no cloud project to pay for and no tag update waiting on a sprint. Most teams are live in about 21 minutes, on a call with us if you want it.
Will it double count against my existing Meta pixel or Google tag?
No. Browser and server events share an event ID, so a conversion the pixel also saw is counted once. You keep the pixel running, and the server-side layer fills the gaps rather than adding a second count on top.
What does first-party tracking mean, and why does the subdomain matter?
First-party tracking means the browser talks to a domain you own, such as track.yourdomain.com, rather than to a third-party tracking domain. Ad blockers work from lists of known third-party domains, and Safari and Firefox limit third-party cookies, so a first-party request avoids both. The subdomain is yours, the identifiers are set on the server, and the click ID is kept for months rather than days.
Which platforms receive the server-side events?
Meta through the Conversions API, Google Ads through Enhanced Conversions and offline conversions, LinkedIn through its Conversions API and Microsoft Ads through offline conversions. Every event carries the click ID and hashed first-party fields, and CRM stages such as qualified lead and closed won can be sent as events of their own.
How long does setup take, and does it work on my website platform?
About 21 minutes: the subdomain, one script, the connections and the event mapping. The script goes in the site header, so WordPress, Webflow, Shopify, Wix and custom builds all work the same way, with or without a tag manager in between.
How does LeadJourney compare with other server-side tracking tools?
Most tools in the category are infrastructure: a container or a gateway that moves events, which you configure yourself and read somewhere else. LeadJourney is the layer plus what sits on it: the CRM match, the reports, the attribution models and Atlas. The ranked guide puts the options side by side, LeadJourney included.
See it on your own domain
See what your pixel drops, on your own traffic.
Book a demo and we connect one of your domains live: what the pixel reports, what the server records, and the gap between them.
Your workspace
One conversion, server-sideWhat happened between the click and the ads manager
MSMira SchulzNorthwind LogisticsSent to 3 platforms
- Google AdsClick recorded on track.yourdomain.com with gclid09:41:02
- BrowserPixel blocked by an ad blocker. Nothing lost.09:41:03
- ServerLead event written, hashed email and click ID attached09:46:10
- Conversion APIsSent to Google, Meta and LinkedIn, deduplicated09:46:11
Visible in the ads manager3 of 3
The browser saw nothing. The server saw everything.
