CRM sync
Every lead lands in your CRM with the source attached
Connect HubSpot, Salesforce, and Pipedrive natively, or any other CRM via webhook. SourceLoop writes lead source, the full journey, and lead score onto your standard fields. Choose one-way push, or two-way sync so deals and revenue flow back for closed-loop attribution.
Free 7-day trial. No credit card required.
Trusted by teams running HubSpot, Salesforce, and Pipedrive
CRM sync stack
Source, journey, and revenue, written straight into your CRM
Native CRMs over OAuth, any other CRM via webhook, mapped onto your standard fields, one-way or two-way, with deals syncing back to the campaign that earned them.
Everything else via webhook, Zapier, n8n, and Make.
Source maps cleanly to your standard CRM fields.
Push only, or full two-way sync, your call.
Deals and revenue flow back to the campaign that earned them.
Connected CRMs · 3
Native CRM integrations
OAuth into HubSpot, Salesforce, and Pipedrive
Authorize once and SourceLoop writes first-touch, last-touch, the full journey, and lead score straight into your standard contact, lead, and deal properties. No middleware, no custom-field sprawl, and nothing for your reps to maintain by hand.
- Live sync into standard contact, lead, and deal fields
- First-touch, last-touch, journey, and lead score written in
One-way or two-way, your call
Push attribution in, or sync the whole loop
One-directional push keeps your CRM clean with attribution only, ideal when you just want source on every record. Bi-directional sync keeps deal stage and revenue flowing back into SourceLoop, so your reports close the loop instead of stopping at the lead.
- One-way push for attribution-only, clean and simple
- Two-way sync reads deal stage and revenue back
Deals and revenue, closed loop
Tie closed-won revenue back to the channel
When a deal moves stage or closes, the amount and stage sync back, and SourceLoop ties that revenue to the original source and campaign. You get true closed-loop attribution and revenue per channel, not just a pile of lead counts that never reconcile with the CRM.
- Deal stage and amount sync back automatically
- Revenue attributed to the original source and campaign
Any CRM via webhook and automation
Not on a native CRM? Fire a webhook instead
Not on HubSpot, Salesforce, or Pipedrive? Fire a webhook, or connect through Zapier, n8n, or Make, and every lead still lands with source, journey, and lead score. It's the same payload we send natively, so your attribution stays consistent across every tool you run.
- Webhook plus Zapier, n8n, and Make support
- Same source, journey, and score payload everywhere
Webhook destinations · 4
How it works
Three steps from connect to closed-loop sync
No middleware to run, no custom fields to wrangle, no engineering ticket to file.
-
01Connect your CRM
OAuth into HubSpot, Salesforce, or Pipedrive, or point a webhook at any other CRM.
-
Field mapping
- utm_source Lead Source
- first_touch First Touch
- lead_score Lead Score
02Map your fields
Source, first/last touch, journey, and score map onto your standard properties.
-
Two-way sync live
- Leads pushed 6,022
- Deals synced 418
- Revenue tied $1.2M
03Choose one-way or two-way
Data syncs in real time. Turn on two-way and deals and revenue flow back.
FAQ
CRM sync FAQ
Which CRMs do you integrate with natively?
HubSpot, Salesforce, and Pipedrive connect natively over OAuth. You authorize once, pick the objects and properties to write to, and the sync is live in minutes. No middleware, no engineering tickets, no API keys to rotate by hand.
My CRM isn't on the list. Can I still sync?
Yes. Point a webhook at any other CRM, or connect through Zapier, n8n, or Make. The payload is the same one we send to native CRMs (source, first-touch, last-touch, full journey, and lead score), so every lead still lands with attribution attached no matter where it goes.
What data do you write into my CRM?
First-touch and last-touch source, the full multi-touch journey, lead score, campaign, and click identifiers like gclid and fbclid. Everything maps onto your existing standard properties on the contact, lead, or deal, so you avoid custom-field sprawl and your reps see clean, familiar fields.
What's the difference between one-way and two-way sync?
One-way sync pushes attribution into the CRM and leaves your deal data untouched, which keeps your CRM clean if you only want source on each record. Two-way sync also reads deal stage and revenue back into SourceLoop, so your reporting closes the loop end to end.
Can I attribute closed-won revenue back to the channel?
Yes. With two-way sync on, deals sync back with their stage and amount. When one moves to closed won, SourceLoop ties that revenue to the original source and campaign, so you see true closed-loop attribution and revenue per channel, not just lead counts.
Will this create duplicate contacts or field sprawl?
No. We dedupe on email so you don't get duplicate contacts, and we map onto your existing standard fields rather than spraying new custom properties. You control the field mapping, so nothing writes anywhere you didn't approve.