These two HubSpot properties sound similar, but they answer different questions. Treating them as interchangeable can make a clean report look authoritative while mixing two separate events.
The short version
Answers: “What was this contact's first known online interaction source?”
Answers: “Which HubSpot tool or process originally created this CRM record?”
A contact can have Organic search as its Original Traffic Source and Forms as its Record Source. Both values can be correct: one describes an interaction, the other record creation.
What Original Traffic Source supports
HubSpot describes Original Traffic Source as the first known online source through which a contact interacted with the business. Its broad categories include organic and paid search, email marketing, social, referrals, direct traffic, campaigns, and AI referrals.
The related drill-down properties can add a domain, campaign, URL, or content detail. HubSpot sets those drill-down values automatically. Manually changing the main traffic-source value can clear supporting drill-down evidence, so a cosmetic “cleanup” can remove context.
Traffic evidence also has limits. Anonymous activity must be matched to a known contact, and browser or tracking restrictions can affect what HubSpot observes. A blank does not automatically prove that the process failed.
What Record Source supports
Record Source identifies the CRM creation mechanism and applies across HubSpot objects. Depending on the record, values can point to a form, import, workflow, integration, mobile app, or user-created record. Record Source Detail properties can identify the specific form, import, or workflow involved.
HubSpot says the Record Source property was introduced in 2024 and backfilled for a limited historical period. Older records can therefore be blank. Preserve that limitation rather than inventing a creation path.
Record Source does not explain the first marketing interaction. It also does not describe every later property update. For later changes, inspect property history and the applicable change source.
Why the values can disagree without being wrong
Original Traffic Source and Record Source use different taxonomies. “Organic search” is a channel category; “Import” is a record-creation mechanism. Comparing them as if they should match asks one field to answer the other field's question.
Start every source report by writing the business question in one sentence. Then choose the field that can support it:
- Use traffic-source properties for first-known or latest-known online interaction analysis.
- Use Record Source and its details for ingestion, integration, and CRM creation analysis.
- Use a separately documented operational field for business classifications such as partner referral or sales-created opportunity.
A practical evidence review
- Write the question. Decide whether you are explaining interaction, record creation, or an internal business classification.
- Keep the raw system properties visible. Review Original Traffic Source, its drill-downs, Record Source, and Record Source Details together.
- Sample recent and legacy records separately. A historical blank may have a different cause from a current blank.
- Trace evidence before editing. Check record history, form or import details, and the public entry path where available.
- Preserve uncertainty. Use `Unknown / legacy` when the evidence cannot support a more specific value.
- Document the reporting definition. Name the exact property, population, date field, filters, timezone, and exclusions.
Three mistakes to avoid
- Overwriting Original Traffic Source to make an executive report look consistent.
- Treating a record-creation mechanism as proof that a channel caused a sale.
- Replacing missing history with an inferred value that cannot be reproduced from evidence.
Operating rule: preserve HubSpot's system-source evidence, define any custom business-source layer separately, and label unsupported history as unknown.