Intent Data Just Moved Onto the HubSpot CRM Record

HubSpot Company Surge, powered by Bombora, puts third-party B2B intent data directly on the CRM record as a native standard signal — no marketplace app, no separate Bombora account, no separate configuration surface. HubSpot's Knowledge Base article and the PM announcement describing it are both dated August 11, 2026.

The feature detects, in HubSpot's words, “when a tracked company's research activity spikes on topics related to your business,” using Bombora's B2B Data Co-op, and surfaces the result everywhere standard HubSpot intent signals already flow: company timelines, the Signals tab, workflow triggers, segments, lead scoring, and reports. It works across Marketing Hub and Sales Hub and is gated by HubSpot Credits and permissions rather than a separate purchase.

This post covers what actually shipped, why the dates you'll read elsewhere don't match HubSpot's own, how the native signal differs from the marketplace connector that has existed since 2022, and — the durable part — what a surge signal is and is not, and how to wire routing and sequencing around a signal that is directional rather than deterministic.

Company Surge is Bombora's trademarked intent product — Bombora created the term, and it's now used industry-wide as shorthand for intent data generally. Inside HubSpot, it arrives as one more standard signal type in the Buyer Intent product, sourced from Bombora's B2B Data Co-op, which HubSpot describes as covering “millions of companies across thousands of business and publisher websites.”

Each signal event carries five fields: the Topic that surged, a Research level (High, Medium, Mild, or Low), a Category, the Top metros where the research is happening (top three geographic areas), and a Source field that always reads “Bombora” — the third-party origin is explicitly attributed on every event. HubSpot auto-selects an initial set of up to 12 Bombora topics based on your website, and you have full edit control after that one-time generation.

The signal flows into every surface standard intent signals already reach: workflow triggers and actions, segment filters, lead-scoring criteria, personalization tokens, company record activity timelines, the Signals tab, and custom reports. A “Recent Intent Signals” company property lets you build saved views of companies that triggered a surge. All signal types, Company Surge included, are on by default once available in an account; turning one off stops future firing but keeps historical events on the timeline.

Two dates are circulating for this release, and they are not the same claim. HubSpot's own Knowledge Base article carries an August 11, 2026 last-updated stamp, and the Community announcement by Justin, HubSpot's PM for Intent, was published August 11, 2026. The “week of August 17” timing you'll see in most coverage traces to Orange Marketing's Monday Recap — a tracker post dated August 17 that opens its Company Surge item with “Starting today, you have native access to data powered by Bombora's B2B Data Co-op.” That's a tracker re-dating an August 11 release to the Monday it covered it, and other write-ups have repeated the framing since.

The “beta” label has the same provenance problem. Neither the KB article nor the PM announcement uses the word in its visible body copy — the Community post's own language is “now live and native in HubSpot.” The beta characterization comes from the trackers: Orange Marketing calls the feature “in beta and native to HubSpot as its newest intent signal,” mediaposte-martech repeats near-identical phrasing, and Sirocco Group's August 19 analysis says it “entered beta in HubSpot during the week of 17 August 2026.” An in-product Beta badge behind the login can't be confirmed or ruled out from the outside — so treat beta status as third-party-characterized, and verify what your own portal shows before relying on it.

“Bombora inside HubSpot” is not new. A separate Bombora Company Surge marketplace connector app has existed since at least 2022 — Bombora's own blog post promoting it is dated November 8, 2022, and carries a customer claim of 300% more net-new high-intent accounts — a vendor-published customer figure with no methodology attached. That connector required a Bombora relationship, an app install, and its own configuration surface. What changed in August 2026 is that Company Surge became a first-class, standard signal type inside HubSpot's own Buyer Intent product: no separate app, no separate Bombora account, no separate place to configure it.

The marketplace app didn't disappear — it's now the upgrade path. HubSpot's included access caps at 12 topics; going beyond that ceiling means purchasing a paid plan directly from Bombora and connecting the existing marketplace integration. The native signal is the on-ramp; the connector is the expansion tier.

The trend this reflects is worth reading as a platform strategy, not a feature note. CRM vendors are pulling third-party data products into the record itself, because a signal that lives where reps already work gets acted on, and a signal that requires a tab switch mostly doesn't. Sirocco Group's analysis makes the same point about why earlier intent programs stalled: the data was rarely the weak link — acting on it required someone to leave the tool they spend their day in. Moving the signal onto the CRM record removes that excuse, which also means the differentiator shifts from having intent data to what your routing does with it.

The durable half of this story has nothing to do with August dates. It's understanding what kind of evidence a surge actually is. The mechanism, as Bombora describes its architecture: a company's current research volume on a topic is compared against that same company's own historical baseline, and a spike from normal to significantly above average produces the surge rating. Detection is resolved to the company via IP-to-company and firmographic matching — not cookies, not individual people.

That design has three consequences. It's company-level: you learn that an account is researching, not who inside it. It's relative: a High research level means unusual-for-them, not large-in-absolute-terms. And it's lagging: the research already happened somewhere across the co-op's network before the signal reached your record. Each of those properties is fine — as long as your routing rules don't quietly assume the opposite. For teams running account-based motions, company-level resolution is exactly the right grain; for a one-to-one sales cadence, it's the start of a research task, not a call script.

On scale: Bombora's own site describes the B2B Data Co-op as spanning 5,000+ co-op sites, roughly 4.7 million unique domains, around 15.8 billion interactions per month, a taxonomy of 21,600+ topics, resolution to about 2.8 million businesses, and 86% of co-op websites exclusive to Bombora. None of those figures carry an as-of date on Bombora's page — read them as the vendor's standing claims about its network, not as fresh August 2026 statistics published for this integration.

Most coverage compresses the economics to “included,” which is close but incomplete. HubSpot's FAQ is precise: “Company Surge is included in the existing per-company tracking cost. There is no additional per-signal charge.” The operative phrase is existing per-company tracking cost — tracking companies for any intent signal consumes HubSpot Credits, the usage-based currency that resets monthly and doesn't roll over. Credits come bundled with seat-based subscriptions in tier-dependent amounts, with additional capacity purchasable. Notably, neither the Company Surge page nor the general Credits page publishes an exact credits-per-tracked-company number — so budget for it as a consumption line you'll observe in your own portal, not one you can price from the docs. We covered how HubSpot got to this credit-metered model in our read on HubSpot's Q2 credit-pricing shift.

Two permissions split the feature cleanly: Data Enrichment permission is required to track companies at all, and edit Buyer Intent permission is required to change signal settings, such as swapping topics. And there is exactly one place the KB page names a subscription tier: using the signal in signal-based lead-scoring criteria requires Marketing Hub or Sales Hub at Professional or Enterprise. The page does not say the whole feature needs Pro or Enterprise — don't over-generalize that single gate into a paywall the docs never describe.

HubSpot's announcement suggests three plays: notify the owning rep when a tracked account hits High research level on a configured topic, build a segment of companies with high research level in the last 14 days, and factor research level into company lead scoring. All three are sensible — and all three fail the same way if they're wired as qualification gates instead of prioritization inputs. A surge should reorder the queue, open a research task, or add scoring weight. It should not, by itself, trigger a sales sequence, promote a lifecycle stage, or mark an account qualified — because the signal carries no person, no budget, and no timeline. If your routing rules already distinguish "prioritize" from "qualify," a surge slots in cleanly; if they don't, this feature will expose that gap fast.

The second prerequisite is duplicate hygiene, and it's the most underrated line in any of the coverage. Sirocco Group's analysis puts it plainly: “If the same organisation exists three times under three spellings and two domains, the signal splits across all three and none of them looks urgent.” A company-level signal inherits every defect in your company records — duplicate and inconsistent company records don't just clutter reporting anymore; they now silently dilute the one signal you enabled to catch in-market accounts. Deduplicate first, then turn on routing.

The classic intent-data failure isn't bad data — it's category error. A surge tells you an account's research activity on a topic rose above its own baseline. Accounts research for many reasons: a competitor's launch, an analyst report making the rounds, an intern's literature review, due diligence on a vendor they already use. Treating “researching the category” as “in-market to buy from us” produces confident outreach to accounts that were never in a buying process, and it burns the credibility of the signal with the sales team — the point at which reps quietly stop opening the alerts.

Be equally skeptical of precision claims. You will find review sites quoting accuracy percentages for Bombora and its competitors; the comparative figures we encountered in researching this post trace to a study we could not independently verify, so we are deliberately not repeating them. The defensible position is qualitative: intent scoring is directional, useful for ordering attention, and unproven as a standalone predictor of purchase. HubSpot's PM makes the honest version of the pitch — “A company actively researching ‘CRM Software’ or ‘Sales Intelligence’ is a company in-motion. That's a reason to reach out, not a guess.” A reason to reach out is exactly the right altitude: better than guessing, well short of a verdict.

Looking forward, expect more of the CRM data layer to work this way: third-party products surfaced as native signals, metered by platform credits, on by default. That consolidation is mostly good — fewer connectors, fewer tabs, faster action — but it shifts the burden of skepticism onto the team consuming the signal. When the data arrives pre-installed on the record, nobody asks where it came from; the is/is-not distinctions above are the questions your routing design has to keep asking on the team's behalf. If you want help wiring intent signals into a routing and sequencing design that respects those limits, that's the core of our CRM automation practice.