CRM leads showing as Direct traffic, Offline or no source
Paid campaigns are producing leads, but in HubSpot or GoHighLevel the contacts show Direct traffic, Offline sources or no source at all, so the CRM cannot say which campaign they came from.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
A lead shows as Direct when the CRM's tracking saw no referrer, UTM or click ID at the moment the session started, which usually means the parameters were lost on a redirect or a jump to another domain. Click a live ad, watch whether the UTMs survive to the page with the form, then submit a test lead and check the contact's source properties.
1. UTMs and click IDs are lost before the form
Redirects that drop the query string (http to https, www to non-www, vanity URLs, link shorteners) remove UTMs before the tracking code reads them. GoHighLevel also says that for UTMs to be recorded, a visitor who lands from an ad must convert on that landing page rather than moving to another page.
How to check
- 1Click the live ad or its preview URL with test UTMs added and watch the address bar after the page finishes loading.
- 2In the browser developer tools, open the Network tab with
Preserve logon and check each redirect keeps the query string. - 3Note whether the visitor has to navigate to another page to reach the form.
How to fix
- 1Set the ad's final URL to the exact page that loads, so no redirect is needed, and fix redirects to pass the query string through.
- 2Put the form on the landing page, for example as an embedded section or pop-up, which is GoHighLevel's suggested workaround.
- 3If the form must sit on a later page, store the UTMs in a first-party cookie or session storage on landing and populate hidden form fields from there.
2. The visitor crosses to another domain before converting
Agency funnels often move visitors from the main site to a booking subdomain, a funnel domain or a checkout on another domain. HubSpot says that without cross-domain linking, a visit that moves to a different domain can be categorised as Direct traffic because the cookies cannot be linked.
How to check
- 1Map the journey from ad click to form submission and list every domain involved.
- 2In HubSpot, go to settings,
Tracking & Analytics>Tracking Code>Advanced Trackingand check theAdditional site domainstable and theAutomatic cross-domain linkingswitch. - 3In GoHighLevel, check the External Tracking script is installed on any external site that hosts forms.
How to fix
- 1In HubSpot, add each domain with
+ Add domain, turn onAutomatic cross-domain linkingand save. Make sure the HubSpot tracking code is on every domain. - 2In GoHighLevel, copy the script from
Settings>External Trackingand paste it before the closing</body>tag on every page of the external site. - 3Where possible, keep the landing page and form on the same domain.
3. The form or booking widget sits in an iframe from another domain
The page's tracking cannot read inside an iframe served from another domain. HubSpot's collected forms feature does not capture forms in an iframe, and GoHighLevel's External Tracking says forms embedded via iframes or third-party widgets are not supported.
How to check
- 1Right-click the form and inspect it. If it sits inside an
<iframe>from another domain, page-level tracking cannot see it. - 2Submit a test lead through the widget and check the contact's source fields.
How to fix
- 1Replace the widget with the CRM's native form or calendar where you can. GoHighLevel forms, surveys, calendars and order forms capture attribution when completed in the same session.
- 2If you must keep a third-party widget, check whether the vendor accepts UTMs in the embed URL and maps them to fields, and pass them through from the parent page.
4. Hidden fields are empty, or a custom form does not pass the tracking cookie
Hidden UTM fields are often added but never filled, because the script that populates them runs before the form loads or reads the wrong parameter names. HubSpot also warns that forms submitted server-side or through a proxy that do not pass the HubSpot tracking cookie may not link the visit to the contact.
How to check
- 1Land on the page with test UTMs, open the developer tools and inspect the hidden field values just before submitting.
- 2Submit a test lead and compare the hidden field values with the contact's source properties.
- 3For custom forms posting to HubSpot through an integration or API, check whether the submission includes the visitor's HubSpot tracking cookie.
How to fix
- 1Populate hidden fields after the form has rendered, using the exact parameter names in your URLs.
- 2For custom integrations, pass the HubSpot tracking cookie with the submission so the visit history links to the contact.
- 3Note that HubSpot's collected forms feature does not capture forms with hidden fields, so a custom form with UTM fields needs a HubSpot form or a proper integration.
5. The consent banner blocks the tracking code
With an opt-in consent banner, HubSpot's cookies should not load until the visitor accepts (HubSpot's banner FAQ says a banner that lets cookies load first is probably set to notification only). HubSpot says that if a visitor converts without accepting cookies, you will not see activities such as page views on their record, so no session source is recorded.
How to check
- 1In a private window, land with test UTMs, accept cookies and submit a test lead. Repeat in a new window and decline.
- 2Compare the two contacts. If only the accepted one has a source, the banner is working as designed.
- 3If neither has a source, check whether the tracking code loads after acceptance on the same page.
How to fix
- 1Make sure tracking starts as soon as the visitor accepts, on the current page.
- 2Expect some contacts without a web source from visitors who decline, and report them as a separate group rather than as Direct.
- 3Capture UTMs in hidden form fields only where your consent policy allows it.
6. The contact was created outside a tracked web session
HubSpot uses Offline sources for records created through imports, integrations, the API or manually, and Direct traffic when there is no referring domain or tracking URL. Links in emails, SMS, apps and PDFs without UTMs, and lead ad integrations, all produce this.
How to check
- 1Open the contact and check how it was created. In HubSpot, the
Record Sourceproperty shows the creation method. - 2Check the
Traffic source drill-downproperties; for Direct traffic, drill-down 1 shows the entrance URL. - 3In GoHighLevel, open the contact, go to the
Activitytab and check the first and latest attribution.
How to fix
- 1Add UTMs to every link you control: emails, SMS, bios, QR codes and partner links.
- 2For integrations and lead ads, map the campaign into a CRM field at sync time rather than relying on web source.
Stop it happening again
- Use one written UTM naming convention for all clients and check it before campaigns launch.
- Run a test lead from a live ad click through to the CRM after every site, form, domain or consent change.
- Keep a map of every domain in each client's funnel and confirm tracking is installed on all of them.
- Agree with the client whether reports use first-touch or latest-touch source, and label it in every report.