CRM lead source compatibility, field by field.
Every CRM has a lead source field. They are not the same, and they do not connect the same way. This is how each major CRM captures source, how Lead Source connects to it, and what each setup can and cannot write. Verified data only; unknowns are marked as such.
The capture does not change. The connection does.
Whatever CRM you run, Lead Source captures the same three things on every form submission: the real source and campaign, the landing page, and the full page journey ending on the page that converted them. What differs is which field the source can land in once it reaches your CRM, through Zapier or a signed webhook. Five CRMs have a page of their own; six more are covered by a verified Zapier connector.
Salesforce, HubSpot, Pipedrive, Keap, Close
- Source lands on the record through Zapier or a signed webhook
- On the field you choose, built-in or custom
- Runs alongside the CRM’s own source field
Copper, Zoho, monday, Freshsales, Dynamics 365, Insightly
- Connects via the CRM’s Zapier connector
- Creates or updates the relevant record
- Maps source into the fields the connector exposes
Not sure what your form records today?
You can check before you change anything. Paste a URL and see what a submission would carry.
The compatibility matrix.
Native field names are stated only where they are a standard, documented field. Connection type and what can be written are from the verified data. “Not verified” means exactly that. We did not confirm it. So we do not claim it.
| CRM | Native source field | How Lead Source connects | What it can write | Last verified |
|---|---|---|---|---|
| Salesforce | Lead Source picklist | Zapier or a signed webhook | The field you choose, beside the picklist | Zapier or webhook |
| HubSpot | Original Source property | Zapier or a signed webhook | The property you choose, alongside Original Source | Zapier or webhook |
| Pipedrive | Source field on the lead | Zapier or a signed webhook | The lead or person field you choose | Zapier or webhook |
| Keap | Lead Source field | Zapier or a signed webhook | Built-in Lead Source field or a custom field | Zapier or webhook |
| Close | Lead source custom field | Zapier or a signed webhook | The Lead field you choose | Zapier or webhook |
| Copper | Standard Source field | Zapier: Create or Update Lead | Standard Source field and Tags (verified) | Zapier, 30 Jun 2026 |
| Zoho CRM | Lead Source picklist | Zapier (Premium): Create or Update Module Entry | Module entry fields; custom-field write not verified | Zapier, 30 Jun 2026 |
| monday | None native (board column) | Zapier: Create Item, Update Item | Board column values, including custom columns | Zapier, 30 Jun 2026 |
| Freshsales | Lead source field | Zapier (Suite): Create or Update Contact / Deal | Contact or deal fields; custom-field write not verified | Zapier, 30 Jun 2026 |
| Dynamics 365 | Lead Source option set | Zapier (Premium): Create or Update Lead / Contact | Lead or contact fields; custom-field write not verified | Zapier, 30 Jun 2026 |
| Insightly | Lead Source field | Zapier: Create or Update Record (object-driven) | Object record fields; custom-field write not verified | Zapier, 30 Jun 2026 |
Every row captures the same source, landing page and full journey. The matrix only differs on the connection and the destination field. For the why behind all of it, read the CRM lead source pillar.
Three things the table is telling you.
- 01Native field is a single value. Every native source field, picklist, option set or column, holds one channel value. None of them hold the campaign, landing page or journey. That gap is identical across CRMs.
- 02The destination field is the difference. For the five CRMs with their own page, the source can land on the field you choose. The Zapier connectors for the other six create or update the record; only Copper’s verified setup writes a standard source field. Where a custom-field write is not verified, the table says so.
- 03The capture is the constant. No matter the row, Lead Source captures source, landing page and journey at submission and stores every lead in your own dashboard, independent of the CRM. The CRM write is the last step, not the only copy.
Questions, answered.
Which CRMs does Lead Source connect to directly?
Salesforce, HubSpot, Pipedrive, Keap, and Close connect directly via webhook or REST and write the source and journey into a custom field. Copper, Zoho, monday, Freshsales, Dynamics 365, and Insightly connect through their own Zapier connector instead.
Does Lead Source write to a custom field in every CRM?
No, and the matrix is honest about that. For the five CRMs with their own page, the source lands on the field you choose. The Zapier-connected CRMs create or update the record; Copper additionally writes its standard Source field, which is verified. Where a custom-field write on a standard record was not verified, the table says so rather than implying it works.
How current is this compatibility data?
The Zapier connector details were verified against zapier.com on 30 June 2026. The five CRMs with their own page are covered by our own Zapier app and signed webhooks. Anything we did not confirm is marked not verified rather than guessed, so the table stays trustworthy.
See where your CRM stands.
Lead Source captures the source, landing page, and journey on every form, whichever CRM you run.
Track your lead sources free →Free to start · no card