ZoomInfo intent: how it works and where the coverage caps

A marketing lead turns on ZoomInfo Copilot's intent layer and the LinkedIn-native enterprise accounts light up cleanly. The local-business slice of the same target list returns no signal. The intent layer is doing its job. The audiences in that slice just don't browse the publishers it tracks.

Whether ZoomInfo intent works depends entirely on whether your buyers' intent gets tracked in B2B publishing networks. This piece walks the mechanism honestly (where the signals come from, how the surge score is built), surfaces real-team experience patterns including the "100 score, didn't pick up" complaint, lands the architectural framing, and covers what to do if you're already paying for it.

1. What ZoomInfo intent actually is

ZoomInfo intent is a product that aggregates buyer signals from multiple sources. Bombora's third-party publishing network, ZoomInfo's own WebSights site-tracking, G2 review activity at higher tiers. And surfaces accounts that show in-market behavior on topics relevant to your business. It's bundled into the Advanced+ and Elite+ ZoomInfo tiers rather than sold as a standalone product. The intent layer complements ZoomInfo's contact graph, surfacing which accounts are in-market while the contact data tells you who works there.

1.1. Intent data vs contact data

Contact data tells you who works at an account. Intent data tells you which accounts are in-market. Different products, different price points, different jobs. ZoomInfo's intent product complements the contact graph rather than replacing it. Buyers cycling between intent platforms and contact-data tools are usually solving different problems. Both are required for outbound to work; neither substitutes for the other.

1.2. How ZoomInfo surfaces intent

Three ingredients combine into the surfaced signal. First, Bombora-derived third-party intent (B2B publishing network signals on what content accounts are consuming). Second, ZoomInfo WebSights (first-party site visitor identification on your owned web properties). Third, the topic taxonomy and scoring layer that maps observed behavior to the topics you select and produces a normalized 0-100 surge value relative to baseline.

2. Where ZoomInfo intent's data comes from

2.1. Bombora

Bombora is a B2B intent-data network that tracks content consumption across thousands of publisher sites in the B2B-tech corpus. Companies like 6sense, ZoomInfo, Demandbase, and Madison Logic all license Bombora data; it's the standard third-party intent source pool across the category. ZoomInfo overlays its account graph on Bombora signals to attribute consumption to specific accounts, which is the value-add over licensing Bombora directly without an account-graph platform.

2.2. Websights

WebSights is a JavaScript snippet that sits on your own website and reverse-IP-identifies anonymous visitors at the account level. Available at higher ZoomInfo tiers. Most reliable for accounts that have visible corporate IP ranges; thinner for remote workforces and accounts behind shared NAT or VPNs. The first-party signal is higher fidelity than third-party intent because it's behavior on your owned properties, not aggregated publisher data.

2.3. G2 integration

ZoomInfo's G2 integration surfaces accounts researching specific products on G2. Higher-fidelity signal for software categories where buyers research vendors on G2 before making decisions. The integration is typically gated to Elite+ tier. For categories with strong G2 presence. SaaS, cybersecurity, dev tools. The G2 layer is the strongest single signal in the bundle.

2.4. Topic taxonomy

ZoomInfo maps signals to a taxonomy of roughly 10,000 topics. You select topics relevant to your business; ZoomInfo surfaces accounts surging on those topics. Topic selection is the operational lever that determines whether intent produces signal or noise. A poorly chosen topic set drowns useful signal in irrelevant surge events.

3. How ZoomInfo intent scores work

3.1. Surge score

ZoomInfo computes a surge score from 0 to 100 for each account-topic pair based on the change in content consumption against the account's own baseline. Surge over baseline matters more than absolute volume. A small company researching one topic 10× more than usual is a stronger signal than a large company maintaining steady research at high volume. The normalization against baseline is what makes the score comparable across accounts of different sizes; without it, large companies would dominate every signal list.

3.2. Topic selection drives everything

Choosing the right topics is the whole game. Too generic ("software," "marketing," "sales") produces noise. Every B2B account is reading something on those topics every week. Too specific produces no surface area. The topic doesn't have enough content consumption volume to surge against baseline. The middle band, where topics are specific enough to map to buying intent and broad enough to have signal density, is the operational sweet spot. Most teams under-invest in topic curation and get noise back.

3.3. Time decay

Intent signals are time-bound. A 100 score from last week means meaningfully more than a 100 score from three months ago. Real-time surfacing is where the value lives. Once the signal is stale, the buyer has either bought or moved on. Build the BDR workflow around fast response (sub-48-hour outreach on flagged accounts) or expect the intent contract to underperform.

4. Where ZoomInfo intent wins

4.1. B2B SaaS targeting other B2B SaaS

When your buyers research on B2B publishing networks (TechCrunch, G2, SaaStr, Gartner, Bombora-network newsletters, software-category review sites), ZoomInfo intent has signal density. Software, cybersecurity, observability, dev tools, finance tooling, sales tooling, marketing tech. These categories work because the buyers consume content on the corpus Bombora indexes. The signal-to-noise ratio is favorable.

4.2. Mid-market and enterprise account selection for ABM

Use intent to prioritize a 2,000-account ABM target list. Surface the top 10% surging this week; route to AEs for fast outreach. The use case relies on having a defined ABM list and an operational workflow to act on the signal. Without those, the prioritization output gets ignored.

4.3. Inbound lead prioritization

Already have a stream of inbound leads? Use intent to flag accounts with surge activity for fast routing to AEs. The intent overlay on inbound makes the prioritization decision sharper. A hand-raise from an account already surging is a higher-priority MQL than a hand-raise from an account showing no intent signal.

5. Where ZoomInfo intent falls apart

5.1. The "100 score, didn't pick up" pattern

The most-cited real-user complaint across Reddit r/sales and G2 reviews: high intent scores that don't convert when the BDR calls. Three structural reasons explain the pattern. First, intent is account-level, not contact-level. The surge could be from anyone in the org (an intern researching for a school project), not the buyer. Second, intent signals often lag the buying decision rather than precede it (research happens after a vendor is shortlisted, not before, so by the time you see the surge, the deal may already be lost). Third, topic noise. A 100 score on a generic topic doesn't mean a buying decision is imminent; it means content consumption surged against a baseline, which can happen for many reasons unrelated to procurement.

5.2. Local-business and trade segments

A 12-restaurant operator researching kitchen equipment doesn't generate Bombora signals. A regional plumbing contractor evaluating field-service software isn't tracked on B2B publishing networks. Horizontal contact graphs cover these segments at roughly 10-20% on decision-maker mobile, versus 60%+ on a discovery-first stack. Intent data only works where intent is published. Which is essentially the LinkedIn-native B2B-tech segment. Switching from ZoomInfo intent to 6sense or Demandbase doesn't fix this; same Bombora data plus similar topology. The fix isn't a different intent platform; for local-business segments it's discovery-first account building (license records, permit filings, franchise registries) layered with operational signals (route density, equipment installed, season-relevant timing). The right complement for those ICPs is a transparent-signal intent provider, not a publisher-co-op-derived platform.

5.3. Smaller TAMs where signal is sparse

Niche industrial verticals, regional services with thin B2B-tech publishing presence. Bombora doesn't have density. Intent looks like noise because the underlying signal pool is thin. Teams in these segments often pay for ZoomInfo intent and see surge scores that don't correlate with anything observable in their pipeline.

5.4. Topic-selection mistakes compound

Generic topic selections drown signal in noise; over-specific selections produce no surface area. Most teams under-invest in topic curation, set up "software" or "marketing automation" as topics during onboarding, and never revisit. The result is an intent dashboard that no one trusts because the surge events don't track to actual buying behavior.

6. How much does ZoomInfo intent cost?

6.1. Bundled at advanced+ and elite+

ZoomInfo intent isn't a separate SKU. It's bundled into Advanced+ ($22K-$30K/year reported) and gets richer at Elite+ ($35K-$45K+/year reported). WebSights and full G2 integration are typically gated to Elite+ tier. Reported figures, not vendor-confirmed quotes. See ZoomInfo Pricing for the full tier breakdown and ZoomInfo Cost for TCO including credit overages and auto-renewal increases.

6.2. Bombora direct licensing

Bombora can be licensed directly for $30K-$80K/year. Cheaper than ZoomInfo's intent bundle but requires you to build the analytics, account-mapping, and CRM-integration layer yourself. ZoomInfo's price premium is for the platform layer (account graph match, scoring, integrations, sales workflow), not the underlying data. Teams with engineering resources and a defined intent playbook sometimes opt for Bombora direct; most teams get more value from the bundled platform.

7. ZoomInfo intent vs alternatives

All five rely heavily on Bombora as the underlying third-party intent layer. For local-business or non-B2B-tech ICPs, none of them produce signal density. The underlying source pool doesn't extend to those segments.

Worth noting: intent platforms only matter if the contact-data layer underneath them is dense enough to act on. ZoomInfo Intent is bundled with ZoomInfo's contact graph; teams running 6sense or Demandbase typically pair with a separate contact provider. Apollo, Clay, Cognism, and Lusha are the most common contact-layer pairings for non-ZoomInfo intent stacks. For local-business ICPs, all five contact providers share the same 10-20% mobile coverage ceiling against a discovery-first benchmark of 60%+. DataLane indexes 17M+ U.S. local business locations and supplies the contact layer where the LinkedIn-dependent providers stop covering.

7.1. ZoomInfo vs 6sense intent

6sense layers a predictive-AI scoring model on similar third-party intent data. Whether the predictive model is worth the meaningful price premium depends on segment maturity and target-account count. 6sense pricing covers the comparison context. For teams with 5K+ target accounts and a mature ABM motion, the predictive layer often justifies the premium. For mid-market teams with smaller target lists, ZoomInfo intent at the lower price point usually wins on cost-per-output.

7.2. ZoomInfo vs Bombora direct

Bombora direct is cheaper but requires building the analytics, account-mapping, and CRM-integration layer in-house. ZoomInfo is paying for the platform plus account-graph match plus the workflow layer on top. For most teams the platform value justifies the markup; for teams with strong engineering and a defined intent playbook, Bombora direct is a real option.

8. How to get value from ZoomInfo intent (if you're already paying for it)

8.1. Curate topics tightly

Five to fifteen highly specific topics beats fifty generic ones. Spend time on the taxonomy at deployment and revisit quarterly. The sweet spot is topics that map clearly to buying intent in your category. "vendor evaluation [your category]," "[competitor name] alternatives," specific pain-point queries. Rather than category-level topics like "marketing software."

8.2. Pair with sales workflow

Intent is only valuable if AEs act on the signal within 48 hours. Build the workflow first. Surge alert routes to AE, AE acknowledges, sequence enrolls within 24 hours, manager reviews response rate weekly. And then turn on intent. Without the workflow, the dashboard stops getting opened by week three.

8.3. Triage surge scores realistically

Don't treat 100 as a deterministic buy signal. Use the score to prioritize attention, not predict outcomes. The team that opens the BDR queue with the surge-score-sorted list has better operational efficiency than the team that ignores intent. Even if many surge events don't convert.

8.4. Combine intent with other signals

Intent surge plus ICP fit plus a recent technographic change is a stronger signal than any one of those alone. Build the combined-signal scoring rule rather than acting on intent surge in isolation. Most over-performing intent deployments use intent as one input in a multi-factor account-prioritization model, not as the sole prioritization mechanism.

Frequently asked questions

ZoomInfo's intent layer earns its place for teams already paying for the core contact graph. The signal density depends on whether your accounts produce web-tracked intent at all. For LinkedIn-native enterprise, the layer is dense; for local-business ICPs, it's mostly empty regardless of price.