Your sales team closed 14 deals last month. Your marketing team wants to know which campaigns drove them. But your CRM shows "direct" or "unknown" for nine of those contacts.
That's not a data gap. It's a connection problem.
When your HubSpot website and CRM don't talk to each other correctly, you lose the thread between what a visitor did on your site and what they eventually signed. Fix that connection, and the questions that matter become answerable: which pages convert, which campaigns generate pipeline, and where qualified leads drop out before they ever reach sales.
This post walks through how to connect HubSpot website data to your CRM, what gets tracked when you do, and how to build the attribution reporting that RevOps teams rely on.
Most B2B buyers visit a website 6 to 10 times before filling out a form. Each visit carries information about what they read, how long they stayed, which pages they returned to. If your CRM only captures the moment someone submits a form, you're working with a fraction of the story.
HubSpot's tracking code changes this. It follows a visitor across sessions, ties anonymous visits to known contacts once they convert, and passes all of that activity into the CRM record automatically.
HubSpot CRM integration connects website behavior to contact records. It records page views, form submissions, and source data. Revenue teams use this connection to trace closed deals back to their original source whether that was a Google ad, a LinkedIn post, or an organic blog visit from eight weeks earlier.
The result is a contact timeline that shows the full journey from first visit to closed deal, not just the last touchpoint before someone hit "submit."
Before walking through setup, it helps to know what data actually flows once the connection is live.
Contact source data records where a visitor came from organic search, paid ads, direct traffic, email, or social. HubSpot stores this as "original source" and "original source drill-down" on the contact record. These fields don't change once set, which is what makes first-touch attribution reliable.
Page views and session history show every page a contact visited, when they visited, and how many times they returned. This appears in the contact activity feed, visible to both marketing and sales.
Form submissions create or update contact records and log the form name, the page it appeared on, and the submission timestamp.
UTM parameters pass through to contact properties when someone arrives via a tagged URL. If your paid campaigns use UTM tracking, that data lands in the CRM without any manual work.
Behavioral events capture specific actions beyond page views: clicking a CTA, downloading a resource, watching a product video, booking a meeting. These feed into lead scoring and workflow triggers.
This is the data foundation that makes lead attribution possible. Without it, you're looking at the last 10% of the buying journey and calling it the full picture.
For a deeper look at how website-to-CRM data architecture is structured, this post on CRM integration with websites covers the technical setup in more detail.
If your website runs on HubSpot CMS, the tracking code is already built in with no separate installation needed.
For WordPress or a custom-built site, go to Settings > Tracking & Analytics > Tracking Code in your HubSpot portal. Copy the JavaScript snippet and paste it into the <head> section of every page. Most teams deploy it through Google Tag Manager to avoid touching the site codebase directly.
The tracking code starts building anonymous visitor profiles immediately. Sessions get tied to contact records when a visitor submits a HubSpot form or clicks a tracked email link.
HubSpot tracking code captures anonymous sessions. It assigns a cookie to each visitor. It creates a contact record and imports session history when the visitor converts.
For teams building or migrating to HubSpot, webdew's HubSpot development services handle the full implementation, tracking configuration, form setup, and custom event tracking included.
HubSpot forms are the bridge between an anonymous visitor and a known contact. When someone submits a native HubSpot form, the platform connects their full session history to their new contact record instantly.
Place native forms (not embedded third-party forms) on your highest-traffic conversion pages: demo request pages, contact pages, gated content downloads, and newsletter signups.
Third-party forms can connect via the HubSpot API, but they require extra configuration and often lose session history in the handoff. Native forms preserve the complete visitor timeline.
UTM parameters tell HubSpot where paid and social traffic comes from. Without them, campaign clicks show up as "direct" or "other" in your source data, and your attribution reports become unreliable.
Build UTM parameters into every campaign URL:
HubSpot records these values in contact properties automatically. You can then segment contacts by campaign source and build pipeline reports without manual tagging.
One common mistake: don't add UTM parameters to internal links. When someone navigates from your blog to your pricing page using a UTM-tagged link, it resets their original source. Use HubSpot's native page analytics for internal traffic instead.
HubSpot's standard tracking handles page views and form submissions well. Custom behavioral events capture everything else: pricing page visits, video completions, chatbot interactions, scroll depth.
Set these up under Settings > Tracking & Analytics > Events. Custom events appear in the contact timeline and can trigger workflows, update lead scores, or notify sales reps.
A contact who visits your pricing page three times in one week is in a different buying stage than someone who reads a single blog post. Custom events make that distinction visible and actionable.
Once data flows in, attribution reports show which sources, campaigns, and content pieces drive the pipeline.
Go to Reports > Analytics Tools > Traffic Analytics for source-level breakdowns. For deal attribution tied to revenue, use Revenue Reports under the Reporting section.
HubSpot supports four attribution models:
Multi-touch models require Marketing Hub Professional or Enterprise. Running first-touch and last-touch reports side by side is a good starting point for most teams; they show the difference between what starts deals and what closes them.
For a broader look at HubSpot's integration options and how attribution connects across hubs, this HubSpot integration overview walks through how the pieces fit together.
Teams hosting their website on HubSpot CMS get tighter attribution data than those running external sites with the tracking code installed. The reason is architecture: HubSpot CMS pages connect natively to the CRM. There are no third-party relays, no session-loss risk during handoffs, and no delays between a conversion event and the CRM update.
HubSpot CMS stores contact activity directly. It removes the gap between website events and CRM records. Marketing teams see conversion data without waiting on sync schedules or export jobs.
If you're evaluating whether to move your site onto HubSpot CMS, this breakdown of HubSpot CMS features covers what's included at each tier and when a migration makes business sense.
Using last-touch only. Most CRM platforms default to last-touch attribution, which credits the form page or final campaign. It ignores the six blog posts and two webinars that came before it. Build a multi-touch model to see what actually drives awareness, not just what triggers the final form fill.
Not filtering your own team's traffic. Your internal visits inflate traffic numbers and pollute conversion data. Filter your office IP addresses and team members under Settings > Tracking & Analytics > Approved IP addresses.
Running multiple tracking scripts. If you run HubSpot alongside a separate analytics platform without proper configuration, you'll get inflated session counts. Decide which platform owns attribution reporting and configure accordingly.
Ignoring anonymous visitor data. Not all high-intent visitors convert on the first visit. HubSpot's Prospects tool (available with certain subscriptions) shows company-level data for anonymous visitors, which gives sales a lead source they'd otherwise miss entirely.
For a full walkthrough of how to set up HubSpot CRM integration correctly from scratch, this HubSpot CRM integration guide covers the initial configuration steps in detail.
Connecting HubSpot website data to your CRM is not a one-time setup task. It's a system you configure, maintain, and build on as your marketing operations mature. The tracking code, native forms, UTM discipline, custom events, and attribution reports each add a layer to the picture.
When those layers work together, your revenue team can answer the questions that actually matter: which pages convert, which campaigns produce pipeline, and where the buying journey starts, not just where it ends.
If you want to build this system correctly from day one, webdew's HubSpot development team works with RevOps and marketing teams on tracking implementation, CMS migration, and attribution reporting setup.