RevOpsXL
GTM Diagnostic Request the audit

HubSpot lead source: why most of your leads say Offline Sources

Alexandra-Emily Kokova

Alexandra-Emily Kokova

Published 16 November 2026 - 7 min read

HubSpot has no lead source property on contacts. It has Original Traffic Source, Latest Traffic Source and Record Source, and when an enrichment tool creates the contact before the person ever visits your site, the first of those says Offline Sources until someone edits it.

In short

Original Traffic Source records how a person first reached your website. Record Source records how the contact was created. Anything HubSpot can’t tie to a tracked visit, including imports, integrations and records typed in by hand, lands in Offline Sources. For how a contact got into the CRM, read Record Source. If the business wants one lead source field, set it once when the contact is created and let nothing overwrite it.

On this page

A B2B marketer at a recruitment agency described the problem on Reddit. The stack was a WordPress site, web analytics, HubSpot and ZoomInfo, all feeding Salesforce. On paper it was fine. In practice a lot of leads arrived as “Direct”, “Other” or blank, and the poster rated the lead source reporting about 70% useless.

The field in that report was filled by whichever system touched the record first, or last, and nobody had chosen which one it should be.

Where HubSpot keeps the source

There is no default lead source property on a HubSpot contact. HubSpot does have a Lead Source property, but it sits on the Leads object, where it holds the analytics source at the moment the lead was created. On the contact, the answer is spread across several fields that do different jobs.

PropertyWhat it answersHow it gets set
Original Traffic Source, with Drill-Down 1 and 2The first known way this person reached your websiteHubSpot’s tracking, from the first visit it can tie to the contact. Editable
Latest Traffic Source, with its drill-downs and dateThe most recent tracked visitEvery new session. An import doesn’t create one
Record Source, with Detail 1, 2 and 3How the contact record was createdHubSpot, at creation: Import, Integration, CRM UI, Forms, Workflow, Salesforce and others
Lead Source, on the Leads objectThe analytics source when the lead was createdHubSpot, at lead creation
A custom “lead source” propertyWhatever the person who made it intendedForms, imports, integrations and people, often all four

Record Source is the newest of these. HubSpot created it in February 2024 and backfilled four years of data, so most portals have it filled in for records older than the property itself. It’s also the one most teams never open.

Original Traffic Source can take ten values: organic search, paid search, email marketing, organic social, referrals, AI referrals, other campaigns, direct traffic, paid social and offline sources. AI referrals is the recent addition, with the AI platform’s domain, such as chatgpt.com, in the first drill-down. How the original and latest source differ in a report is covered in our piece on first-touch vs last-touch attribution.

Why Offline Sources wins

HubSpot describes Offline Sources as a catch-all. It holds anything HubSpot can’t tie to a tracked visit: imports, integrations, records created through the API, contacts typed in by hand, calls, events and untagged links in print.

Enrichment tools are the usual reason the share climbs. When ZoomInfo, Apollo or a list import creates the contact, the record exists before the person has done anything on your site. HubSpot tries to match a new contact to visits it already tracked, so a cookie from an earlier visit can still win. A visit after the record exists is a different case. HubSpot doesn’t document a rule for relabelling the source afterwards, and the answer given in its community is that the contact stays in Offline Sources. Someone who was enriched in March and filled in a demo form in May will read as offline for as long as nobody edits the field.

HubSpot’s own advice is to stop using Offline Sources to track how records were created and to read Record Source for that instead. Record Source separates the import from the integration from the form, and its first detail names the import file, the form or the workflow. The drill-downs on Offline Sources are less reliable. HubSpot doesn’t document what goes into them for offline records, and the values vary by portal and by app, so check what yours holds before you build a report on them.

Why visits land in Other campaigns

With Other campaigns, HubSpot did see the visit. It saw tracking parameters on it too, and they matched none of its rules.

The rules are short. A source or medium containing cpc, ppc or adword, or a gclid on the URL, counts as paid search. Paid social needs paid, ppc or cpc in the medium plus a social network as the source. HubSpot’s own marketing emails count as email marketing. A link from any other tool needs the word email somewhere in its parameters. A medium of social with a known network is organic social. Everything else with parameters on it is Other campaigns, which is where a newsletter tagged utm_medium=newsletter or a banner tagged utm_medium=display ends up.

Most of it goes away with a written list of allowed mediums, each matching one of HubSpot’s rules, and someone checking new campaign links against the list before they go out.

When Salesforce is in the loop

Salesforce has a standard Lead Source field, and it’s a picklist. HubSpot’s Salesforce integration lists Lead Source among its default mappings. Original Traffic Source isn’t sent across unless someone creates a custom mapping for it.

Each mapping has a sync rule: Prefer Salesforce unless blank, Always use Salesforce, Two-way, or Don’t sync. In the setup from the Reddit thread, ZoomInfo writes into Salesforce, HubSpot writes into Salesforce, and the rule on the field decides which one wins. If the rule is Always use Salesforce and the enrichment tool fills Lead Source first, every later answer from HubSpot is overwritten. A picklist also needs a home for values it doesn’t contain, so look at what the integration does with a source the list doesn’t have before trusting the Other bucket.

Decide which system owns the field and set the rule to match it. On a two-way rule, the last system to write wins.

Source on companies and deals

The contact’s source travels. A company copies the original source of the associated contact with the earliest activity. A deal uses the associated contact with the earliest activity and falls back to the company if there isn’t one.

So one enriched contact, imported months before anyone at the company engaged, can label the company and every deal on it as Offline Sources. The person who filled in the form, booked the call and signed is a different contact on the same company. Their source never reaches the deal report.

A setup that holds

Read Record Source when the question is how a contact got into the CRM, and read Original Traffic Source when the question is how a person first reached the website.

Original Traffic Source can be changed by hand, by bulk edit, or with a workflow on Professional and Enterprise. Changing it clears the drill-downs and the first referring site, and the drill-downs can’t be put back by hand. Decide who is allowed to edit it, and keep a record of anything changed in bulk.

If the business wants one lead source field for reporting, make it a custom property and set it once, when the contact is created, with a workflow that reads Record Source and Original Traffic Source and only writes when the field is empty. After that nothing overwrites it, including the integration.

Tracking can’t see a podcast, a recommendation or a private Slack group. A required “how did you hear about us” field on the demo form can, and it belongs next to the tracked source rather than in place of it. It is the subject of self-reported attribution.

The ad side of the same problem, sending a qualified contact back to Google, LinkedIn or Meta so they learn which clicks became pipeline, is in HubSpot offline conversions.

Alexandra-Emily Kokova

Hands-on practitioner, ecosystem architect and GTM strategist, in and around HubSpot since 2014, building the systems B2B revenue runs on across the EU, UK, Nordics, the Gulf and North America.

Published 16 November 2026

Contact me on LinkedIn

Common questions

Not on contacts by default. Contacts carry Original Traffic Source, Latest Traffic Source and Record Source. Lead Source is a default property on the Leads object, where it holds the analytics source at the time the lead was created.

It is the catch-all for anything HubSpot cannot tie to a tracked website visit: imports, integrations, records created through the API, contacts added by hand in the CRM, calls and events. HubSpot recommends Record Source for tracking how records were created.

The visit had UTM or source parameters that matched none of HubSpot’s rules. A medium such as newsletter or display lands there, because email marketing needs the word email and paid search needs cpc, ppc or adword.

Yes. By hand, by bulk edit, or with a workflow on Professional and Enterprise. Editing it clears the drill-downs and the first referring site, and the drill-downs cannot be edited by hand.

A deal takes the original source of the associated contact with the earliest activity, and falls back to the company if there is none. The company copies the associated contact with the earliest activity.

Get the next field note by email

New field notes twice a month. One short email when one goes up, nothing else.