Most teams leave attribution to HubSpot’s automatic fields, then find paid leads with an Original Source of Direct traffic. The ads worked and the deals closed, but the campaign data never made it onto the contact, so the report credits nobody.
Nothing in the ad account is broken. The leak sits between the ad click, the cookie banner and the form, and one decision closes it: where campaign data is stored on the contact.
Why HubSpot shows paid leads as Direct traffic
As of November 2026, HubSpot buckets a visit as Direct traffic when the referring URL is empty. Either the visitor typed the address, or the referring information was lost on the way. HubSpot’s own guide to higher than expected direct traffic lists the causes, and several of them hit paid leads specifically:
- The visitor declined cookies or ignored the consent banner, then submitted a form.
- The form sits on a page without the HubSpot tracking code.
- No user token was passed with the submission, for example when the form posts through the Forms API or cookie tracking is turned off on the form.
- The referrer was lost, for example when the referring site uses HTTPS and yours does not.
The UTM tags on the ad were probably fine. HubSpot’s source fields depend on the tracking cookie, so for an untracked visitor the campaign data stays in the landing page URL and never reaches the contact.
How Original Source is set, and why fixing it by hand backfires
Original Traffic Source is the first known web source of a contact, set automatically from tracking cookies. The drill-down fields carry the campaign detail, per HubSpot’s traffic source properties reference. For Paid search, drill-down 1 holds the utm_campaign value; for Paid social, drill-down 2 does.
Manually editing Original or Latest Traffic Source clears the source drill-down and First Referring Site properties, as HubSpot’s article on updating traffic source values states. Relabeling Direct contacts as Paid search fixes the chart and deletes the campaign name in one step.
Who this matters for
Heads of marketing who report cost per lead by channel feel it first, because paid spend looks worse than it is. Founders feel it when a budget decision rests on that report. Teams with a lot of EU traffic should expect a larger Direct bucket.
What to check in your portal
- Open a paid lead marked Direct traffic and view all of its properties. Check Original Traffic Source, both drill-downs and First Referring Site.
- Check that the landing page carries the HubSpot tracking code and that the form does not post through the Forms API without a user token.
- Check that the Use cookies switch is on in your site tracking settings, and that Add source tracking tags to all URLs is selected for HubSpot emails.
- Look at your cookie banner. Every visitor who does not click Accept arrives as Direct traffic, by design.
- Open your paid landing page forms and see whether any hidden field stores UTM values in a contact property you own.
What to decide before the next campaign
Attribution is a data decision made before the first ad runs, not a report repaired afterwards. Three decisions cover it:
- Who owns UTM naming. One person keeps the list of allowed source, medium and campaign values, and every new ad uses it.
- Which properties keep campaign data. Create contact properties for the UTM values and add them to paid landing page forms as hidden fields. HubSpot’s hidden form fields guide confirms hidden fields can store values such as
utm_campaignon submission; a hidden field cannot also be required. - What the report counts. Decide whether the channel report reads Original Traffic Source, your own UTM properties, or both side by side, and write that down.
Our take
A HubSpot portal mirrors the process behind it. When nobody owns campaign naming and nobody decided where campaign data lives, Direct traffic is the honest result.
Our rule: map UTM values from the form into your own contact properties through hidden fields, and do not rely only on HubSpot’s automatic source fields. The automatic fields depend on the tracking cookie, and visitors who decline cookies arrive with no source at all.
The setup is small: a few properties, hidden fields on each paid form, and a naming list. The real cost is ownership. Someone has to keep the naming list clean, or the properties fill with many spellings of the same campaign. If nobody can own that, start with the banner and tracking code checks.
Process first
Your HubSpot mirrors your process
If stages, handoffs or reports keep breaking, the fix starts with the process.
FAQ
Why are my paid HubSpot leads showing as Direct traffic?
Paid leads show as Direct traffic when HubSpot cannot read a referrer or tracking URL for the visit. Common causes are a declined cookie banner, a form on a page without the tracking code, or a form submitted without a user token.
Does declining cookies affect HubSpot attribution?
Declining cookies affects HubSpot attribution directly. HubSpot lists a visitor who did not accept cookies, or ignored the banner, as a cause of Direct traffic on form submissions.
Can I fix the Original Source of existing contacts?
Yes, but carefully. Manually editing Original or Latest Traffic Source clears the source drill-down and First Referring Site properties, so copy the campaign detail somewhere else first.
This week, open five paid leads marked Direct and find out which cause applies to each. Then name the person who owns UTM naming and add hidden UTM fields to your main paid form. If your lifecycle and source fields already disagree, read our notes on lifecycle stage vs lead status and on choosing a source of truth for HubSpot data.
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.