HubSpot

What Is HubSpot?

HubSpot is an all-in-one customer platform that combines a free CRM with paid "Hubs" for marketing, sales, customer service, content management (CMS), and operations. If you need a one-sentence answer: HubSpot is the system many companies use to capture leads through forms and chat, nurture them with email and automation, track them through a sales pipeline, and host the marketing website and blog that feeds the whole funnel. Founded in 2006 by Brian Halligan and Dharmesh Shah out of MIT, HubSpot popularized the term "inbound marketing" and has grown into a publicly traded company serving well over a hundred thousand customers across more than 120 countries, according to HubSpot's own published figures.

The reason HubSpot matters for technology detection is that it leaves an unusually rich and consistent footprint in the browser. A site that runs HubSpot forms, the tracking code, the chat widget, or the HubSpot CMS typically loads several recognizable scripts and sets a distinctive family of first-party cookies. That makes HubSpot one of the easier marketing platforms to identify from the outside, which in turn makes it a high-value signal for competitive research and lead qualification: a company on HubSpot is usually a company that invests in structured inbound marketing and sales.

It is worth being precise about scope. HubSpot is a SaaS platform, not a browser extension or a plugin you self-host. When a website "uses HubSpot," it almost always means the site embeds HubSpot's JavaScript (the tracking and forms code) and connects to a HubSpot portal identified by a numeric "Hub ID" (also called a portal ID). The actual customer data, automation, and reporting live inside HubSpot's cloud, not on the website itself.

A useful mental model is to think of HubSpot as two layers: a front-end layer that runs in the visitor's browser (forms, chat, tracking, and optionally the rendered pages of the HubSpot CMS) and a back-end layer in HubSpot's cloud that stores records and runs automation. Technology detection sees only the first layer, but because that layer is so distinctive, it lets you infer a great deal about the second. A company that has wired its forms and chat directly into HubSpot is almost certainly running its lead lifecycle, email nurturing, and pipeline reporting there too.

How HubSpot Works

At the center of everything is the CRM database. HubSpot stores contacts, companies, deals, and tickets as records, and every interaction, a form submission, an email open, a page view, a chat conversation, a sales call, is logged against the relevant contact. The free CRM is the foundation; the paid Hubs add capabilities on top of that same shared data layer, which is HubSpot's core selling point: marketing, sales, and service teams all read and write to one source of truth instead of separate disconnected tools.

The pieces that touch a public website work roughly like this:

• The tracking code. A small JavaScript snippet (loaded from js.hs-scripts.com) is placed sitewide. It records page views, identifies returning visitors via cookies, and ties anonymous browsing to known contacts once they submit a form or click a tracked email link.
• Forms. HubSpot forms are embedded with a script from js.hsforms.net. When a visitor submits, the lead is created or updated directly in the CRM, often kicking off an automated workflow.
• Analytics. A reporting/analytics script (commonly from js.hs-analytics.net) feeds engagement data back into HubSpot's dashboards and attribution reports.
• Chat and the conversations inbox. HubSpot's live chat and chatflows surface as an on-page widget (frequently associated with markup and assets referencing hs-banner and the conversations tooling) that routes messages into a shared inbox.
• Workflows and automation. Behind the scenes, server-side automation enrolls contacts into email sequences, lead scoring, and lifecycle-stage changes based on the behavior the tracking code reports.

Because all of this is keyed to a single Hub ID, once you find that ID you have effectively confirmed which HubSpot portal a website belongs to.

How to Tell if a Website Uses HubSpot

HubSpot is one of the more reliably detectable platforms because it touches scripts, cookies, and the DOM all at once. Here are the signals and the tools to check them.

Script domains (the strongest tell)

Look for requests to HubSpot's CDN and infrastructure domains. The most common are:

• js.hs-scripts.com — the main tracking/loader script, usually loaded as js.hs-scripts.com/<HubID>.js, where the number in the path is the portal ID.
• js.hsforms.net — the forms embed library.
• js.hs-analytics.net — analytics/reporting.
• js.hs-banner.com and *.hubspot.com / *.hs-banner.com — cookie-consent banner and related assets.
• *.hubspotusercontent*.net and *.hscta.net — hosted content and calls-to-action.

The numeric Hub ID embedded in the hs-scripts URL is the single most useful artifact: it uniquely identifies the customer's portal.

Cookies

HubSpot sets a recognizable family of first-party cookies. The classic ones are:

• hubspotutk — the visitor's unique tracking token, used to associate browsing with a contact.
• __hstc — the main tracking cookie (contains domain, timestamps, and session counts).
• __hssc — the session cookie.
• __hssrc — a flag indicating whether the user restarted their browser session.

Seeing hubspotutk together with __hstc/__hssc is essentially a fingerprint for the HubSpot tracking code.

JavaScript globals and DOM

HubSpot exposes objects on the page you can inspect in the DevTools Console. Common globals include window._hsq (the tracking queue array you push events into) and window.hbspt (the namespace used to programmatically create forms, e.g. hbspt.forms.create(...)). In the DOM, embedded forms render inside containers with classes like hs-form and hsforms, and the chat/CTA tooling often injects elements and iframes referencing hs-banner or HubSpot conversation assets.

Tools and method

1. View Source. Search the raw HTML for hs-scripts, hsforms, hbspt, or hubspot. Embedded form and tracking snippets are usually visible directly.
2. DevTools Network tab. Reload with the Network panel open and filter for hs- or hubspot. The hs-scripts.com/<id>.js request reveals the Hub ID.
3. DevTools Console. Type window._hsq or window.hbspt and press Enter; defined objects confirm HubSpot is active. Check Application > Cookies for hubspotutk and __hstc.
4. Wappalyzer (or similar fingerprinting extensions) will typically label the site "HubSpot" automatically by matching these scripts and cookies.

For a structured walkthrough, see how to tell if a website uses HubSpot and the broader guide on how to find what email marketing platform a website uses.

Key Features

• Free CRM core. Unlimited contacts and a shared record of every interaction, with marketing, sales, and service Hubs layered on top.
• Forms and lead capture. Embeddable forms, pop-ups, and progressive profiling that write directly to the CRM.
• Email marketing and workflows. Drag-and-drop email builder plus multi-step automation triggered by behavior, properties, and lifecycle stage.
• CMS Hub. A fully hosted website and blog platform with themes, drag-and-drop editing, and built-in SEO recommendations, all wired into the CRM.
• Conversations and chat. Live chat, chatbots, and a shared team inbox that unify email, chat, and forms.
• Reporting and attribution. Dashboards that tie revenue back to campaigns, pages, and sources because the data lives in one place.
• App marketplace and integrations. A large ecosystem connects HubSpot to advertising platforms, e-commerce stores, webinar tools, and data warehouses, so the CRM stays the hub even when other systems do specialized work.
• Lead scoring and lifecycle stages. Built-in scoring and lifecycle-stage automation move contacts from "subscriber" to "marketing-qualified" to "sales-qualified" based on the behavior the tracking code reports, giving sales a prioritized view of who to contact next.

Pros and Cons

Pros

• One unified platform reduces data silos between marketing, sales, and service.
• Generous free tier lowers the barrier to entry for small businesses.
• Excellent onboarding, documentation, and a large ecosystem of integrations and partners.
• Strong, consistent tracking makes attribution and reporting genuinely useful.

Cons

• Costs escalate quickly as contact counts grow and as you add paid Hubs and "Professional/Enterprise" tiers.
• Advanced automation and reporting are gated behind higher pricing.
• Deep investment in HubSpot creates switching costs and a degree of platform lock-in.
• The breadth of features can be overwhelming for teams that only need email or only need a CRM.

HubSpot vs Alternatives

HubSpot competes with focused email tools on one side and full CRM/marketing suites on the other. The table contrasts it with common alternatives.

Platform	Primary strength	CRM included	Best for	Typical detection tell
HubSpot	All-in-one CRM + marketing + sales + CMS	Yes (free core)	SMB-to-mid-market inbound teams	hs-scripts.com, __hstc cookie
Mailchimp	Approachable email + light marketing	Light CRM	Small business email & newsletters	chimpstatic.com, mc.us* endpoints
Salesforce + Marketing Cloud	Enterprise CRM depth	Yes	Large, complex sales orgs	Pardot/pi.pardot.com scripts
Marketo (Adobe)	Enterprise B2B automation	Via integration	Large B2B demand-gen teams	munchkin.js tracking
Klaviyo	E-commerce email + SMS	Light, commerce-focused	Online stores (esp. Shopify)	klaviyo.com / static.klaviyo.com

If you are comparing email-first options, our profile of Mailchimp is a useful counterpoint to HubSpot's heavier, CRM-centric approach.

Use Cases

• Inbound marketing. Capturing leads with forms and gated content, then nurturing them with automated email until they are sales-ready.
• Aligned sales and marketing. Passing scored leads into a shared pipeline so reps see the full engagement history.
• Hosted marketing site and blog. Running the entire public site on CMS Hub so content and CRM data stay connected.
• Competitive and lead research. Detecting HubSpot on a prospect's site is a strong technographic signal; it suggests a structured marketing operation and a likely budget. Pair detection with the ideas in how to find out what technology a website uses to build a fuller profile.
• Agency and partner reporting. Marketing agencies that build and run HubSpot portals for clients use detection to audit which properties are correctly instrumented, confirm that tracking fired across every domain, and spot pages where the snippet is missing or duplicated.
• Migration and consolidation. Teams moving off legacy tools verify that HubSpot tracking and forms are live before decommissioning the old stack, using the visible footprint as a deployment checklist.

Frequently Asked Questions

How can I tell which HubSpot portal a website is connected to?

Look at the main tracking script URL. HubSpot loads it as js.hs-scripts.com/<HubID>.js, and the number in that path is the portal (Hub) ID that uniquely identifies the customer's account. You can find it in View Source or in the DevTools Network tab by filtering for hs-scripts.

Does seeing HubSpot scripts mean the whole website is built on HubSpot CMS?

No. Many sites run on WordPress, Webflow, or a custom stack and simply embed HubSpot's forms, chat, and tracking code. The presence of hs-scripts.com confirms HubSpot tracking and tooling, but the website itself may be hosted elsewhere. To confirm CMS Hub specifically, look for HubSpot-hosted page assets and hubspotusercontent domains serving the actual pages.

What do the HubSpot cookies actually do?

hubspotutk stores the visitor's unique tracking token so HubSpot can associate anonymous browsing with a known contact once they submit a form or click a tracked email. __hstc and __hssc track the broader visit and session, recording timestamps and visit counts. Together they let HubSpot stitch together a visitor's full history.

Is HubSpot the same thing as a Google Analytics-style tracker?

Not exactly. Both observe page views, but HubSpot's tracking is tied to its CRM, so its purpose is to identify and nurture individual leads, not just aggregate traffic. A site can run both: HubSpot for contact-level marketing and an analytics tool for traffic measurement.

Can a website hide that it uses HubSpot?

Largely, no, if it uses HubSpot's standard embeds. The forms, chat, and tracking code all load from HubSpot's public domains and set recognizable cookies, which are visible to anyone inspecting the page. Server-side analysis makes this even more reliable by checking headers, scripts, and behavior together rather than depending on a single tell. Analyze any URL with StackOptic.