HubSpot's source properties quietly answer one of the most important questions in marketing: where did this contact come from? Source properties record how a contact first found you and how they most recently engaged — and using them well lets you filter, report, and prove which channels actually produce customers. Most teams either ignore them or misread them, and end up crediting the wrong channel. Here's the practitioner's read on updating and filtering contacts with source properties.
Before filtering on them, make sure you know what original and latest source actually mean.
What are source properties in HubSpot?
They're the properties that record a contact's origin — most importantly the original source and the latest source — set automatically by HubSpot. Original source captures how a contact first arrived (organic search, paid, referral, direct, email, and so on). Latest source captures the most recent way they re-engaged. HubSpot also stores supporting detail like the specific drill-down behind each. The key thing to understand is that original source is meant to be permanent — it's the first touch — while latest source keeps changing. Confusing the two is where most source-based reporting goes wrong, because they answer two completely different questions.
How do you filter contacts by source?
Build an active list or filter on the source property that matches the question you're asking — original for acquisition, latest for current engagement. If you want to know which channel acquires the most customers, filter on original source. If you want to re-engage people whose most recent touch was a specific campaign, filter on latest source. Worked example: an active list of contacts whose original source is "organic search" and who became customers tells you what your SEO investment is actually worth — while filtering the same group by latest source would mix in everyone who happened to click an email last week, answering a different question entirely. Pick the property that matches the question, not the one that's handy.
Can you update source properties — and should you?
Original source is set by HubSpot and best left alone; you can update it manually, but doing so usually corrupts your acquisition reporting. The pull to "fix" a source — say, recategorizing a batch of imported contacts — is strong and almost always a mistake, because original source is the one stable record of first touch. The safer move is to use additional custom properties to capture extra context (like a campaign or a list-import tag) and leave the system source properties intact. Imported contacts are the one common exception worth thinking through: they often land as "offline source," and deciding how to tag them at import time is better than overwriting source later, when you've already lost the clean version.
How do you use source data to make decisions?
Segment and report by original source to see which channels produce revenue, not just leads — then point your budget at what converts. The payoff of clean source data is honest channel attribution: which source brings contacts that actually become customers, at what rate. Filter your customer list by original source and the picture often surprises teams — the channel with the most leads isn't always the one with the most customers. This is the order we follow with clients: keep source properties clean, segment by original source for acquisition questions, and let that data steer spend. Dirty or overwritten source data quietly sends budget to the loudest channel instead of the best one.
What are the common mistakes to avoid?
The three big ones: reading latest source as if it were original, overwriting source in a cleanup, and trusting source data on a messy portal. Reading latest source for an acquisition question credits whatever channel last touched the contact, badly inflating your email or retargeting numbers. Overwriting original source to make it "cleaner" destroys the only first-touch record you have. And trusting any of it on a portal full of duplicates means a single buyer counted as three contacts with three different sources, smearing the picture. Avoiding these is mostly discipline: understand which property answers which question, resist the urge to edit the system fields, and keep the underlying records clean enough that the source data means something.
The IV-Lead take
Source properties are a small feature with an outsized influence on where your marketing budget goes. Used carefully — original source for acquisition, latest source for engagement, custom properties for the rest — they turn vague channel debates into a clear answer about what produces customers. Used carelessly, or overwritten in a well-meaning cleanup, they send money to the wrong place. The discipline is simple: understand what each property means, and resist the urge to "fix" the one that's already telling the truth.
Not sure your source data is telling you the truth about your channels? Book a 30-minute portal audit — we'll check your source properties and attribution and tell you straight which channels actually produce customers. For the bigger picture, see how we approach revenue operations.
Frequently asked questions
What's the difference between original source and latest source in HubSpot?
Original source records how a contact first found you and is meant to stay fixed. Latest source records their most recent way of re-engaging and changes over time. Use original for acquisition questions, latest for engagement.
Can I change a contact's original source?
You can edit it manually, but it's best left alone — it's the one stable record of first touch, and overwriting it corrupts your acquisition reporting. Use custom properties for extra context instead.
How do I filter contacts by where they came from?
Build an active list or filter on the source property that fits your question — original source for acquisition, latest source for current engagement — and combine it with lifecycle stage to see which channels produce customers.
Why do imported contacts show as offline source?
HubSpot tags contacts added by import as an offline source by default. Decide how you want to tag them with custom properties at import time rather than overwriting their source property afterward.
