Attribution
Lead Source Tracking: Set Up Sources So Your Reports Tell the Truth
A source report is only as honest as the list reps pick from. Here is a picklist to copy, the rules that keep it stable, and the monthly check that catches drift before budget season.
Key takeaways
- Lead source records the one channel that created the record; campaigns and UTM values go in a second field, never in the picklist.
- Keep the picklist between eight and twelve mutually exclusive values, each with a written “pick it when” and “not when.”
- The original source is set once and never overwritten; a separate latest source field records the channel that brought a buyer back.
- UTM parameters describe a click in your analytics; they reach the CRM only if a form or an import writes them to the record.
- A seven-question monthly check on blanks, Other, spot checks, edits and imports catches drift before it reaches a budget decision.
Lead source tracking means recording, on every lead, the one channel that first brought the buyer to you, and keeping that value as the lead becomes a contact and a deal. It takes a picklist with written definitions, a rule that the original source never changes, and a monthly check. In Senitix CRM, every lead carries a source.
Source reports rarely fail loudly: they drift. A rep picks “Website” because it’s first in the list; an import stamps a whole batch with one value; a returning buyer’s source gets overwritten by last week’s ad. This guide gives you a list to copy, the rules that keep it stable, and the check that catches drift.
What is lead source tracking?
It is a data discipline, not a tool: every new lead gets one value from a fixed list answering a single question: which channel created this record? Whoever creates the record sets it, and the value travels through qualification into the contact, account and deal it becomes. The guide to how a CRM database divides leads, contacts and deals covers which record holds what.
Three terms get mixed up; separating them fixes half the problems:
- Lead source is the channel (paid search, event, partner), a picklist field on the record.
- Source detail is the instance: which trade show, partner or campaign. A second field, so the picklist stays short.
- UTM parameters are tags on a link that web analytics reads. They describe a click, not a buyer, and reach the CRM only if something copies them there.
Why do lead source reports stop telling the truth?
- Too many values. Nobody reads 30 definitions, so a long list gets used inconsistently.
- No definitions. Is a webinar attendee who clicked a LinkedIn ad “Event” or “Paid social”? Unwritten, each rep decides.
- A catch-all value. “Website” says where a form was filled in, not what brought the buyer to it.
- Overwriting. A rep updates the source to the latest touch, and the channel that created the relationship loses the credit.
- Imports with a default. A conference list arrives with an empty source column, and whatever the import fills in becomes the truth.
A lead source picklist you can copy
Keep the list between eight and twelve mutually exclusive values, each a channel rather than a campaign. Classify the channel, not the contact method: a call, a form and a chat are how the buyer reached you, not what brought them. Here is a twelve-value list for a US B2B team, with the rule for when two values seem to fit.
| Value | Pick it when | Not when |
|---|---|---|
| Organic search | The buyer found you through an unpaid result on Google, Bing or another search engine. | They clicked an ad on the results page. |
| Paid search | They clicked a search ad, branded or not. | The ad ran on a social or display network. |
| Paid social and display | They clicked a paid ad on LinkedIn, Meta, YouTube or a display network. | The post they saw was unpaid. |
| Organic social | They came from an unpaid post, profile or community thread, yours or an employee’s. | A rep messaged them first. |
| Email marketing | They responded to a marketing email sent to a list, such as a newsletter. | The email was a rep’s one-to-one message. |
| Outbound | A rep or SDR contacted them first, by cold call, cold email or social message. | They reached out before anyone contacted them. |
| Customer referral | An existing customer recommended you, and the buyer says so. | The person who referred them is a paid partner. |
| Partner | A reseller, agency, consultant or integration partner introduced them. | You only met the partner and the buyer at the same event. |
| Event | You first met them at a trade show, a conference or a webinar you ran or sponsored. | They registered after clicking an ad; the ad created the record. |
| Review site | They came from a software directory or review listing, such as G2 or Capterra, paid or unpaid. | A customer or partner made the introduction and the review only confirmed it. |
| Direct or word of mouth | They typed your address or heard of you in conversation, with no search, ad, customer or partner behind it. | A named customer or partner sent them. |
| Other | Nothing above fits. Source detail is always filled in. | You are torn between two values; use the definitions and pick one. |
Adapt the values to your motion (a distributor-only team might split Partner in two and drop Review site), but keep the “not when” column; the edge cases are where reports split apart.
Original source vs. latest source: why the original never changes
The original source answers one question: which channels create new demand? Edited to reflect a later touch, it answers a different question, and the report can’t tell which. So the rule is short: set it once, at creation, and change it only to correct a mistake, with a note saying why.
Returning buyers still matter, so give them their own field: a latest source, using the same list, records the channel that most recently brought the buyer back, overwritten each time. HubSpot’s help article “Understand Original and Latest traffic source properties” describes the same pair: an original source for the first known touch, a latest one for the most recent.
Example, not a real company. A 12-rep B2B SaaS team in Austin scans a buyer’s badge at a trade show in Dallas. Three months later the same buyer clicks a paid search ad and books a demo, and the rep changes the source to Paid search. At budget time, the show seems to have produced 30 leads and no deals, and it is cut. With the rule in place, the deal keeps Event as its original source and Paid search as its latest, so both channels get the credit they earned.
How do UTM parameters relate to the lead source field?
UTM parameters tag a link so analytics can tell which campaign a click came from. Google’s guide “URL builders: Collect campaign data with custom URLs” says to always use utm_source, utm_medium and utm_campaign, and warns that values are case sensitive: “google” and “Google” count as two sources. Organic search and direct visits carry no UTM; analytics infers them from the referring site, or the lack of one.
A CRM sees none of this unless something writes it to the record, usually a web form with hidden fields, or an export from your form tool. Once the values arrive, map them to the picklist with one written rule per medium:
- utm_medium = cpc, search engine source: Paid search.
- utm_medium = paid_social or display: Paid social and display.
- utm_medium = email, list send: Email marketing.
- utm_medium = partner: Partner, partner’s name in source detail.
- utm_campaign: always source detail, never the picklist.
Lowercase every value and keep the convention documented. If “LinkedIn” becomes “linkedin” next week, the mapping breaks before the CRM is involved.
What should you do with “Other”?
Treat Other as an unanswered question. Four rules keep it small:
- No Other without a note. Source detail names what happened, in a few words.
- Read every Other lead monthly. Reclassify where a definition fits: a correction, not overwriting history.
- Promote a pattern. A recurring note, such as a podcast, is a channel; add it and retire one nobody uses.
- Set a ceiling. If more than one lead in twenty is Other, the list is missing a value or reps don’t know the definitions.
How do you set up lead source tracking?
Six steps, each with an owner and a written output.
- Pull current values. CRM admin: every source value used in the last twelve months, with a lead count.
- Write the list. Marketing lead, with the sales manager: the picklist, with a “pick it when” and a “not when” per value.
- Map old to new. CRM admin: a two-column mapping, such as “Google Ads,” “adwords” and “PPC” to Paid search.
- Update the records. CRM admin: a corrected export, re-imported. Where an old value resists mapping, set a cutoff date and compare sources only for leads created after it.
- Agree the capture rule. Sales manager: one sentence in your lead management process: whoever creates the record sets the source at creation, asking “How did you hear about us?” when the channel is unknown.
- Save the reports and book the check. CRM admin: the three reports below, plus a recurring monthly task.
What should a lead source report show?
Lead count alone rewards the channel that produces the most names. Save three views, grouped by original source:
- Volume: new leads by source, this month against the last three.
- Conversion: leads that became deals, over all leads from the same creation month.
- Revenue: won deal amount by source over two to four quarters, since B2B cycles outlast a month.
Example with illustrative numbers. Over two quarters, paid search produces 120 leads, 6 deals and $36,000 won; events produce 40 leads, 8 deals and $50,000; customer referrals produce 15 leads, 6 deals and $81,000. Revenue per lead (won amount ÷ leads) is $300 for paid search, $1,250 for events and $5,400 for referrals. The volume chart crowns paid search; the revenue view starts a different budget conversation.
The monthly lead source check: seven questions
One owner, usually the CRM admin or marketing ops, runs this in the first week of the month on the prior month’s new leads, recording answers in a dated note.
- How many new leads have no source? Target zero; fix each and find who created it.
- What is in Other? Read every note and decide whether a pattern deserves a value.
- Do ten random leads match their definitions? Two mismatches out of ten is a training problem.
- Did anyone change an original source? Check the field history; every change needs a reason.
- Did an import give a whole batch one value? Right for a trade show list; a red flag if nobody chose it.
- Did any source jump or fall sharply? Usually a tagging problem before it is a marketing result.
- Do new deals carry a source? Converted leads inherit it; hand-typed deals often don’t.
Lead source tracking in Senitix CRM
In Senitix CRM, every lead carries a source, a status and an owner, and an administrator edits the picklist values, so your definitions become the options reps see. Qualifying a lead creates the contact, account and deal in one step and copies the source onto both. The leads section of the feature catalog lists what the record holds.
- Latest source and source detail are custom fields you add for that purpose.
- Field history shows who changed an overwritten original source, and when.
- Reports by source exist on every plan, and a lead list filters by source for the monthly check: see the reporting section of the feature catalog.
- An Other reminder: an automation can task the owner whenever a lead saves with Other as its source.
- Imports of CSV or Excel files run on every plan, including Free: how the cleanup in step four gets done.
Two limits to plan around: Senitix CRM doesn’t read UTM parameters or website visits itself, so import them into custom fields if your form tool records them; and web forms that turn an inquiry into a lead are coming soon, so today a lead is entered by hand or imported. To try the picklist on real records, compare plans and start on Free.
Frequently asked questions
What is the difference between lead source and lead status?
Lead source says where the buyer came from and never changes after creation. Lead status says where the lead stands today (new, working, qualified, disqualified) and changes as reps work it. Grouping status by source shows which channels produce leads your team can qualify.
Should lead source be stored on the contact, the deal or both?
Both. The contact keeps the original source for as long as the relationship lasts, and each deal records the source that created it, the same value for a first deal. For a second deal from an existing customer, decide in advance whether it inherits the original source or takes the channel that reopened the conversation, and write that rule down.
How do you track the lead source for phone calls?
Ask. On the first call, the rep asks “How did you hear about us?”, maps the answer to the list, and writes the buyer’s words in source detail. Heavy inbound call volume can justify a tracking number per channel instead. The call itself is never the source: it’s how the buyer reached you.
Is lead source tracking the same as marketing attribution?
No. Lead source is a single value: the channel that created the record. Marketing attribution spreads credit for a deal across several touches, using a model such as first-touch or W-shaped. Get a clean original source working first: every attribution model depends on it, as the guide to marketing attribution models explains.
Keep reading
Reporting & Forecasting
What a Sales Dashboard Should Show: A Layout for Sales Managers
The six-tile sales dashboard layout for reps and managers, what each tile answers, and the drill-down rule that keeps every number checkable.
How-To Guides
How to Set Up Your First Sales Pipeline in Senitix CRM
The five-step setup for your first sales pipeline in Senitix CRM: exit criteria, stages, key fields, your deals, then a second pipeline.
Logistics & Transportation
Freight Broker Sales: A Follow-Up System for Spot Quotes and Lane Bids
A follow-up system for freight broker sales: a shipper account record, a spot-quote log and a weekly review, with a Chicago-Dallas example.
Ready to grow with Senitix?
Connect with customers, win more deals and grow repeat business, all on one platform.
No credit card required.
