View as Markdown

TL;DR

  • HubSpot keeps the oldest Original Traffic Source when contacts merge.
  • If someone changed the value by hand, that rule doesn't apply.
  • Page views and other analytics totals are added together.
  • Duplicates split attribution before the merge, so reports change after a cleanup.
  • Dedupely follows HubSpot's own merge for these values and logs every original in Merge History.

Original Traffic Source tells you how a contact first found you: organic search, paid social, a referral. When the same person exists twice, each record has its own source, and your attribution reports count the person twice. Merging fixes that, but only one source can survive.

Here's what HubSpot keeps, why, and what to check in your reports after a cleanup.

What HubSpot keeps

Property After a merge
Original Traffic Source The value from the oldest record, unless it was updated by hand
Create date The oldest record's create date
Page views and visits Added together from both records
Lifecycle stage The stage furthest down the funnel
Number of form submissions Added together
Most other properties The primary record's value, or the other record's when the primary is blank

The logic is simple: the oldest record shows how the person first arrived. A contact created from an ad in March and again from a webinar in July first came from the ad.

When the rule doesn't apply

If someone edited Original Traffic Source by hand on one of the records, HubSpot doesn't apply the oldest-value rule to it. Teams sometimes do this to fix a misattributed lead, or after an import set every source to "Offline Sources". After a merge, check a sample of contacts where the source was edited.

How duplicates distort attribution

Before the merge, duplicates make attribution look better than it is:

  • One person counts as two new contacts, often from two channels.
  • The later channel gets credit for someone the earlier channel already brought in.
  • Conversion rates drop, because one of the two records never converts.

What to check after a cleanup

  1. Compare source reports before and after the cleanup for the same date range.
  2. Expect new-contact counts to drop for the channels that created the second records.
  3. Explain the change to the team that owns attribution, so it isn't read as a drop in performance.
  4. Check hand-edited sources on a sample of merged contacts.

How Dedupely handles source data in HubSpot merges

Dedupely merges HubSpot contacts through HubSpot's own merge, so HubSpot's rules apply to Original Traffic Source and the analytics totals. Merge Rules decide the other fields, like owner, phone or lead status. Merge History keeps every original record's values, so you can see each record's source before the merge and export it as a CSV.

Clean up HubSpot contacts without losing attribution

The first source survives

When HubSpot contacts merge, the oldest Original Traffic Source is kept unless it was edited by hand, and analytics totals are added together. Reports change after a cleanup because duplicates were double-counting people, so compare before and after and let the attribution owner know what to expect.

Frequently asked questions

What happens to Original Source when you merge HubSpot contacts?

HubSpot keeps the value from the oldest record, unless the property was updated by hand.

Are page views lost when contacts merge?

No. HubSpot adds the page views and visits of both records together.

Why did my source report change after a cleanup?

Duplicates counted one person twice, often under two channels. After the merge, each person counts once, under their first source.

Can I choose which Original Source to keep?

HubSpot's merge keeps the oldest value. If it's wrong, edit Original Traffic Source on the merged contact.

Which create date does the merged contact keep?

The oldest record's create date.