The blog · Tools & Stack · 7 min
Demand Compass vs Bombora: what does intent data leave out?
A topic surge feeds one axis at the company level. What it cannot see is whether the account knows you, or what its people do on surfaces you own.
Bombora sells Company Surge, a third-party intent feed that tells you which companies are researching topics in your category more than usual, built from a data co-op of publishers and B2B sites. The Demand Compass is the operating model above that feed: a two-axis score on every account, brand awareness and readiness to buy, with one play per quadrant. Intent data of this kind feeds one axis, readiness, at the company level; it leaves out the awareness axis and is thin on the lead-level dark channel, the named people on surfaces you own. Keep Bombora if you have it. The Compass turns its surge into a decision.
What is Bombora's Company Surge, in its own words?
Bombora's Company Surge is intent data that identifies "high-potential, in-market accounts", drawn from a Data Co-op of "thousands of trusted and influential publishers, brand sites, and premium data providers". As of September 2026 the home page puts numbers on the scale: "16B+ monthly events" across "5M+ company domains" and "21,600+ Intent topics", with "86% of the data in our Co-op" shared exclusively with Bombora for the purpose of deriving intent. Source: Bombora, Home page, 2026
The mechanism, on its product page, is a proprietary JavaScript tag placed across "hundreds of publishers and brands, and thousands of B2B sites", reading "gated, paywalled, and open content, including text, form fills, downloads, and registrations", consent-driven for GDPR and CCPA. Around the feed sit Visitor Insights, which identifies anonymous traffic on your own site, B2B Digital Audiences for activation on ad platforms, and Campaign Measurement. Source: Bombora, Company Surge product page, 2026
What does intent data measure, and what does it leave out?
Third-party intent data measures one thing well: whether a company, somewhere, is consuming more content on a topic than its usual baseline. In the Demand Compass that is a readiness input at the company level. It leaves out two things: how much that account already knows you, the awareness axis, and what named individuals are doing on the surfaces you own, the lead-level dark channel. That is not an argument against the feed; it is a description of what a surge can and cannot say about one account.
The Demand Compass reads every account on two independent axes. Awareness is the one you build, with everything you publish and every room you are in. Readiness is the one you can only detect: momentum inside the account, a budget freed, a leader hired. An account surging on your topic that has never heard of you is In-Market: fast, signal-informed outreach from an SDR. The same surge on an account whose people follow yours and reply to your newsletter is Sales-Ready: the AE moves now. A feed that reports the surge alone cannot tell those two apart.
Intent without awareness is noise; awareness without intent is vanity.
The second omission is closer to home. Company Surge, by Bombora's own description, reads other people's sites; Visitor Insights adds your own web traffic. What no third-party feed watches is the rest of your dark channel: the free-tier account used this week, the docs page read three times by the same engineer, the badge scan from last month's event, the community thread where someone asked about you by name. Those signals are private, and they separate an account reading about a category from an account evaluating you.
Why is a topic surge not the same as readiness?
A topic surge is not the same as readiness because readiness is a composite of several signals on the same account inside the same few weeks, and a surge is one of them. Teams misread the readiness axis in three predictable ways, and all three show up the week an intent feed goes live.
- One signal treated as readiness. The dashboard lights, a rep pounces, the prospect has no idea why a stranger is in their inbox. A single surge can be an analyst or an intern writing a report. The stacking is what means something: surge plus a stack-revealing job post plus a pricing-page visit, together.
- Reading at the person instead of the account. Company Surge is company-level by design, which gets this right. The mistake returns when a team enriches the surge into a contact list and treats the first name that surfaces as the buyer. The person who signals is rarely the person who signs.
- Ignoring decay. Readiness goes stale faster than any other evidence. A surge this week is live; the same surge seven months ago is history. After a real signal fires, you usually have thirty to sixty days before the account shortlists without you or settles back into inertia.
How do the Demand Compass and Bombora compare?
Everything in the Bombora column is from its own site as of September 2026.
| Bombora Company Surge | The Demand Compass | |
|---|---|---|
| What it measures | Topic-level research intensity by company, against its baseline | Two axes per account: brand awareness and readiness to buy |
| Level | Company domain | Account, rolled up from company, person and industry signals |
| Where the signal comes from | A co-op of publishers, brand sites and B2B sites, via a JavaScript tag | Every sensor you own or rent, Bombora included, reporting into one account store |
| Decay | Not described on the pages we read | Readiness decays fast on a curve; awareness decays more slowly |
| Awareness axis | Not measured | Half of the model, scored from engagement with what you publish |
| Lead-level dark channel | Visitor Insights on your own site traffic; the rest is outside its scope | Product, docs, free tier, community, events and CRM, wired in by you |
| What you own vs rent | Rented: the co-op, the topics and the scoring are Bombora's | Owned: the score, the weights, the plays and the routing |
| Price disclosure | Not published; the call to action is "Speak to an expert" | Not applicable; it is a model your team runs on your stack |
On price, Bombora has no pricing page as of September 2026; its calls to action route to "Speak to an expert". We state no figure because the vendor states none. Source: Bombora, Home page, 2026
Where does the lead-level dark channel come from?
The lead-level dark channel comes from sensors you own or rent one at a time, each reporting into a single account-level store. The Demand Compass names them by type, never by vendor: web de-anonymization, product and developer intent, job-post monitoring, community listening, field and event capture, and trigger feeds. Most of our deployments run roughly twenty signals and one tool per category.
The order is the reverse of what most teams do. Industry-level signals are the hardest to instrument; the private, lead-level ones are the easiest, because you already own the tools that produce them. Build from the bottom up, then climb. A surge feed like Bombora slots in at the company level as a strong second sensor rather than the only one. The awareness side is where our own response numbers come from: cold email replies in the low single digits, and the same channel into accounts that had engaged with us first replied near 20 percent.
How do you plug Bombora into the Demand Compass?
You plug Bombora into the Demand Compass by mapping the surge to a weighted, decaying readiness input at the account level, adding the sensors it does not watch, and building the awareness axis from data you already have. Nothing gets ripped out.
- Map Company Surge to a readiness input with a weight and a decay curve. A surge is a strong signal, not a verdict.
- Add your own lead-level sensors, cheapest first: page-level site de-anonymization, product and free-tier activity, job posts read for stack and seniority.
- Score awareness from what you own: replies, follows, newsletter engagement, event attendance.
- Attach a play to each quadrant with an owner and a response time; route surging accounts by quadrant, not by surge alone.
- Calibrate the weights against last quarter's closed-won.
Related questions
Do I need to cancel Bombora to run the Demand Compass?
No. A feed you already trust is one sensor for the Signal Radar, and a strong one at the company level. The Compass sits above the vendors and decides what to do with the surge.
Does Bombora measure brand awareness?
Not on the pages we read as of September 2026. Company Surge is described as topic-level research intensity by company. Awareness is the axis the Compass adds from your own engagement data.
Is a surging account In-Market or Sales-Ready?
It depends on the awareness axis. A surge on an account that has never heard of you is In-Market and gets fast SDR outreach; on an account already engaging with your content it is Sales-Ready and goes to the AE now.
