Companies that use Hubspot Content Hub Enterprise

What this captures, and what it doesn't

We believe in being transparent about how we collect our data and what its limitations are, unlike most other data providers who operate as black boxes.

This one is worth reading carefully, because detecting HubSpot Content Hub Enterprise relies on a structural quirk of the product rather than any explicit plan-level signal.

This methodology captures companies that operate two or more distinct brand domains on HubSpot CMS under the same HubSpot portal.

Multi-brand domain support is gated to the Content Hub Enterprise tier. Free, Starter, and Professional plans are limited to a single brand domain per portal. So if we can prove a company is running multiple brand domains out of one portal, that company has to be on Enterprise.

It does not capture every Content Hub Enterprise customer. The most important blind spots:

• Enterprise customers whose additional brand domains live outside our universe of roughly 3 million scanned domains. If a company runs a primary site we know about plus a secondary brand on a domain we've never indexed, the connection between the two portals is invisible to us. Our detection rate is therefore a floor, not a ceiling.
• Enterprise customers who pay for Enterprise but happen to only operate a single brand domain on HubSpot CMS. They get the plan for other Enterprise-only features (advanced permissions, hierarchical teams, adaptive testing, etc.) and leave no multi-domain fingerprint we can read.

If you need a complete view of HubSpot CMS adoption beyond the Enterprise tier, our broader HubSpot dataset at HubSpot covers every detectable usage pattern.

How we figured this out

HubSpot doesn't publish anything that distinguishes a Content Hub Enterprise account from a Professional one at the page level. The CMS markup, hosting infrastructure, and tracking scripts look identical across tiers.

What does differ is what the platform lets a customer do. One of the cleanest plan-gated capabilities is the number of brand domains a portal can run, and we turned that into a detection signal.

We start with our universe of roughly 3 million company domains, ranked by headcount as reported on their LinkedIn profiles. For each domain on HubSpot CMS, we run a three-step check.

1. Capture the HubSpot portal ID. When a site is built on HubSpot CMS, every HTTP response from that site includes a portal ID (HubSpot's internal account identifier) embedded in its headers. We crawl the domain, read that header, and record the portal ID. Domains not on HubSpot CMS are dropped.

2. Group domains by portal ID. Across our full crawl, we cluster domains that share the same portal ID. A portal hosting only one domain in our dataset tells us nothing, since that's the default Pro/Starter/Free state. A portal hosting two or more distinct domains is the signal we're looking for, because that configuration is impossible on any plan below Enterprise.

3. Verify the domains are genuinely distinct. A naive grouping would over-count for two reasons.

First, companies often configure multiple hostnames (example.com, www.example.com, get.example.com) that all redirect to a single canonical site. Those aren't separate brand domains in any meaningful sense, they're aliases.

Second, companies sometimes rebrand and redirect their old domain to their new one, which leaves two domains attached to the same portal even though only one is actually live.

So for every multi-domain portal, we follow each domain's redirect chain and confirm the final landing pages are actually different, and that no domain in the group is just redirecting into another domain in the same group. Only portals that resolve to two or more independently live destinations are kept.

The intersection of those three checks (a shared HubSpot portal ID across two or more independently resolving domains) is our fingerprint for Content Hub Enterprise.