Ad platforms
Server-side conversion tracking software
Server-side conversion tracking with Conversions API sync
Pixel-based tracking misses 30-50% of conversions thanks to iOS 14, Safari ITP, and ad blockers. SourceLoop sends complete first-party conversion data to Google Ads, Meta, and ChatGPT Ads, including the leads your team marks Good and the deals that actually close.
Free 7-day trial. No credit card required.
Used by 750+ marketing teams, agencies, and SaaS companies
Why pixels miss conversions
Your ad platforms only bid on the conversions they can see
Pixels live in the browser, and the browser keeps getting locked down. By the time Google or Meta record a sale, 30-50% of conversions are gone, so Smart Bidding optimizes on a partial signal. Server-side conversion tracking syncs first-party conversions straight to each ad platform via the Conversions API (CAPI).
30-50%
Conversions hidden in the browser
iOS 14 App Tracking Transparency and Safari ITP drop the pixel events Google Ads and Meta rely on to learn.
~40%
Visitors blocking the pixel
Ad blockers and cookieless browsers stop the pixel from firing, so the conversion never reaches the platform. Server-side delivery does.
Cookieless
Third-party cookies deprecating
The identifiers pixels depend on are going away. First-party, server-side CAPI syncing is the durable way to keep measuring.
Conversion sync stack
Reclaim the conversions your ad pixel is missing
First-party, server-side conversions delivered to every ad platform past iOS 14, Safari ITP, and ad blockers, with the credit model you choose.
Recover lost data
First-party events survive iOS 14, ITP, and ad blockers.
Conversions sent
Track delivery and match rate by platform, in real time.
Score by value
Send deal value, not just a generic conversion event.
Click IDs preserved
GCLID, fbclid, and more, matched to every conversion.
Ad platforms · 3 live
Google Ads 2,140 Live 
Meta CAPI 1,820 Live 
ChatGPT Ads 312 Live 
LinkedIn CAPI Coming soon 
TikTok Events API Coming soon Server-side, no code
Conversions API for the platforms you spend on
Google Ads, Meta's Conversions API, and ChatGPT Ads today, with LinkedIn and TikTok on the way. Connect once and we handle delivery, retries, dedupe, and identifier hashing per platform.
- Real-time delivery, automatic retries
- Per-platform dedupe and identifier hashing
Choose what counts
Send Good leads, won deals, and paying customers, not form fills
Pick what each ad account learns from, and send it with its real value. Bidding then chases buyers, not spam.
- Templates for every lead, Good leads, SQLs, and won deals
- Deal value, lead value, and revenue for value-based bidding
paid_subscription
+ $1,188 gclid CjwKCAj…7-Aw
conversion_action paid_subscription
conversion_value 1188.00
currency_code USD
user_email_sha256 e3b0c44…b855
conversion_date_time 2026-04-27 14:32:08
How it works
Three steps from snippet to live conversion sync
No GTM, no server container, no DIY CAPI endpoint to maintain.
-
<script async src="https://t.sourceloop.ai/tracking-v3.js"></script>
01Install the snippet
We capture GCLID, wbraid, gbraid, and fbclid on the visitor's first landing.
-
02Connect your ad accounts
Connect Google Ads, Meta, or ChatGPT Ads, then pick a template like Good leads or won deals.
-
Live conversion sync
- Google Ads 2,140 sent
- Meta CAPI 1,820 sent
- ChatGPT Ads 312 sent
03Conversions sync in real time
Server-to-server delivery, automatic retries, identifier hashing where supported.
Customer stories
Teams feeding better conversions back to their ad platforms
From agencies and SaaS companies to clinics and law firms, teams use SourceLoop to trace every lead and every dollar back to the campaign that earned it.
ploomly B2B SaaS
We started sending only qualified demos back to Google Ads as conversions. Within six weeks, paid search was filling our calendar with buyers who fit our ICP, and close rates followed.
- SQLs from paid search
- +38%
- Demo-to-close rate
- 2.1x
Halden & Wright Agency
We run paid media for 14 clients. Every lead now lands in their CRM with the campaign, keyword and ad behind it, so we can prove our impact with numbers clients can check for themselves.
- Lower cost per lead
- 41%
- Client accounts tracked
- 14
Cedar Row Dental Clinics
Half our new patients book by phone. Multi-touch attribution on every call showed us which ads start a booking and which ones close it, so we cut the two channels that did neither.
- Of bookings now attributed
- 63%
- Monthly spend reallocated
- $9k
Fernhill Legal Professional services
Most of our leads showed up as Direct in the CRM. SourceLoop now gives us the full journey behind every inquiry, chat and call, from the first search to the booked consultation.
- More consults per dollar
- 27%
- Lead channels in one report
- 4
FAQ
Server-side conversion tracking FAQ
Why don't my Google Ads or Meta conversion numbers match my CRM?
Pixel-based conversion tracking sits in the browser, where iOS 14 App Tracking Transparency, Safari ITP, ad blockers, and cookieless visitors all cut into what gets reported. Most teams lose 30-50% of conversions before the ad platform ever sees them. SourceLoop captures every conversion first-party, then pushes it server-side to your ad accounts so the numbers actually reconcile with your CRM.
What is the Conversions API (CAPI) and why does it matter?
The Conversions API is a server-to-server channel for sending conversion events to ad platforms (Meta CAPI, Google's Enhanced Conversions, ChatGPT Ads, and others) instead of relying on the browser pixel. It's resistant to iOS 14, Safari ITP, and ad blockers, and the platforms reward CAPI events with higher event-match-quality scores, which makes Smart Bidding more accurate.
Can I send only qualified leads to Google and Meta?
Yes. Each sync sends one moment you choose: every lead, only leads marked Good by your lead quality rules or team, contacts who reach a stage like SQL, won deals, trials, new paying customers, or every payment. Spam is never sent, and a lead that stops being Good is withdrawn.
How does iOS 14, Safari ITP, and ad blockers affect tracking?
iOS 14's App Tracking Transparency, Safari's Intelligent Tracking Prevention, and consumer ad blockers all restrict third-party cookies and pixel calls in the browser. SourceLoop's snippet runs as first-party JavaScript on your own domain, then delivers conversions server-to-server via Conversions API, so none of these restrictions break attribution.
How is this different from setting up Meta CAPI or Google Enhanced Conversions manually?
DIY CAPI means writing a server endpoint, hashing identifiers (email, phone) per platform spec, deduping browser pixel and server events, retrying failures, and updating schemas every time a platform changes. SourceLoop ships all of that. Map a conversion action once, we handle delivery, retries, identifier hashing, and per-platform dedupe.
Will this work with Smart Bidding (tCPA, ROAS, Maximize Conversions)?
Yes. Smart Bidding strategies need a steady, complete conversion signal to learn from. Server-side first-party events are exactly that signal. Send revenue value alongside the conversion and Maximize Conversion Value / tROAS bidders learn what actually pays, not what the form-fill volume looks like.
Which ad platforms do you support?
Google Ads (offline conversions with Enhanced Conversions), Meta (Conversions API), and ChatGPT Ads (Conversions API, set up for you). LinkedIn and TikTok are coming soon. The same SourceLoop snippet captures the click identifier, and we handle each platform's format, hashing, and delivery.
What is the difference between client-side and server-side conversion tracking?
Client-side tracking fires from the visitor's browser, so an ad blocker, a privacy browser, or a failed script means the conversion never leaves the page. Server-side tracking sends the event from a server you control, after the conversion is confirmed. The browser can no longer drop it, and you can attach information the browser never had, such as the deal value your CRM assigned it later.
What is the difference between the Conversions API and the Meta pixel?
The pixel is browser-side and reports the moment something happens on the page. The Conversions API is server-side and reports the same event from your infrastructure, including events that never touched a browser. Meta recommends running both and deduplicates them by event ID, which SourceLoop sends automatically so the same purchase is not counted twice.
How do I track offline conversions in Google Ads and Meta?
Offline conversions are the ones that happen after the click and away from your site: a deal marked closed-won in your CRM, a sale taken over the phone, a subscription that finally converted. SourceLoop keeps the original GCLID or fbclid attached to that person, so when the deal closes we upload it as an offline conversion with its real value, and the ad platform learns to bid for buyers rather than form fills.
Do I need a Conversions API Gateway or server-side Google Tag Manager?
No. Both exist to give you a server you control between the browser and the ad platforms, which means provisioning cloud infrastructure and maintaining it. SourceLoop already is that server, so the events, the identity matching, and the delivery to each platform are handled without a Gateway instance or a server-side GTM container to run.
