Without SourceLoop
Untagged
Kayden Floyd
- SourceUnknown
- MediumUnknown
- CampaignUnknown
- Landing pageUnknown
Journey
No touchpoints captured
Conversion sync
Server-side conversion tracking that ad platforms actually trust
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 CAPI, and LinkedIn CAPI, with the attribution credit you decide is right.
Free 7-day trial. No credit card required.
Used by 750+ marketing teams, agencies, and SaaS companies
What you get
Reclaim the conversions your ad pixel is missing
First-party data, server-side delivery, and you choose the credit model.
-
Capture the conversions ad platforms can't see
Pixel-based tracking misses 30-50% of conversions thanks to iOS 14 ATT, Safari ITP, ad blockers, and cross-device journeys. SourceLoop tracks every visit first-party from your domain, so the data is already complete before the ad platform asks for it.
-
Pick the credit you send: first, last, or multi-touch
Most tools blast last-click conversions to every platform. SourceLoop has the full attribution picture, so you choose: train Google Ads on first-touch credit, Meta on last-touch, LinkedIn on revenue-weighted multi-touch. Per-platform, per-event.
-
Server-side via Conversions API, iOS-proof
Server-to-server delivery through Meta CAPI, LinkedIn CAPI, and the Google Ads API. Hashed email and phone identifiers where supported. ATT, ITP, and ad blockers don't sit in the way.
-
No GTM, no DIY CAPI, five minutes to live
OAuth your ad accounts, map conversion actions, you're done. No Google Tag Manager gauntlet, no server-side container, no Cloud Function or DIY CAPI endpoint to babysit.
Connected ad accounts · 6
Server-side, every platform
Conversions API for every ad platform you spend on
Google Ads (Enhanced Conversions + the Ads API), Meta CAPI, LinkedIn CAPI, Microsoft, TikTok, Pinterest, and Reddit. OAuth in once and we handle delivery, retries, dedupe, and identifier hashing per platform spec.
- Real-time delivery, automatic retries
- Per-platform dedupe and identifier hashing
You pick the credit
Send first-touch, last-touch, or any model, per platform
Most CAPI tools only know last-click. SourceLoop already tracks every touch on the visitor's journey, so you choose what each platform learns from. Train Google Ads on first-touch credit, Meta on last-touch, LinkedIn on revenue-weighted multi-touch, all from the same dataset.
- First-touch, last-touch, linear, U-shaped, custom
- Revenue, MRR, and LTV-weighted values supported
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 src="https://cdn.sourceloop.ai/sl.js" defer></script>
01Install the snippet
We capture GCLID, Wbraid, Gbraid, fbclid, and li_fat_id on the visitor's first landing.
- 02
Connect your ad accounts
OAuth into Google, Meta, LinkedIn, Microsoft, TikTok. Map conversion actions in five minutes.
-
Live conversion sync
- Google Ads 2,140 sent
- Meta CAPI 1,820 sent
- LinkedIn CAPI 624 sent
03Conversions sync in real time
Server-to-server delivery, automatic retries, identifier hashing where supported.
FAQ
Conversion sync, 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, LinkedIn CAPI, Google's Enhanced Conversions, etc.) 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 choose which attribution touch gets sent to each ad platform?
Yes. Because SourceLoop already tracks first-touch, last-touch, and the full multi-touch journey, you decide what credit each platform learns from. Train Google Ads on first-touch, Meta on last-touch, and LinkedIn on a U-shaped multi-touch model on the same dataset, per-event if you want.
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 (with Enhanced Conversions and the Google Ads API), Meta (Conversions API), LinkedIn (Conversions API), Microsoft Ads, TikTok Ads, Pinterest Ads, and Reddit Ads. The same SourceLoop snippet captures the click identifier; we handle the per-platform schema, hashing, and delivery.
Paid Social
