Intent Data Is a Timing Signal, Not Proof of a Deal

Intent data is packaged behavioral signal that an account is researching a problem, product, or category, used to time outreach before anyone fills a form. Demandbase defines it as a signal, not proof the account picked you. In the 2025 Buyer Experience Report, 94% of buying groups ranked preferred vendors before first seller contact.

Only about 5% of B2B buyers are in-market in a given quarter (Ehrenberg-Bass / LinkedIn B2B Institute; the figure is category-dependent). That is why marketers buy timing. It is also why a lone topic surge is a poor reason to fire an SDR sequence.

Key Takeaways

• The category sells a timing signal that an account is researching a topic. It is not proof of a deal, a named buyer, or consent to be sold.
• First-party activity on your site is a fact. Third-party surge is an inference modeled from a panel or co-op.
• Second-party signal (review sites, publisher-owned readers) sits between those two and is closer to vendor selection.
• A Company Surge names the building, not the floor. Attach a person before you treat the account as a sequence.
• Use the feed to prioritize accounts already on your ABM list. Do not let a platform become the list.

What Is Intent Data?

Demandbase's FAQ is blunt about the gaps. The category cannot show that a specific person decided to buy, selected your company, or is ready for a call today.

Your ICP still decides who is worth the work. Timing is the only new answer.

Treat two nearby phrases as different products. The packaged category is mostly account-level, sold on a contract, and scored against a topic taxonomy. An intent signal is any observable buying indicator you can see without buying a dataset: a pricing-page visit, a new VP, a hiring spike, a G2 comparison.

This article is B2B purchase intent. It is not Android Intent, not a legal letter of intent, and not a generic cookie or CDP lecture.

How Intent Data Works

Most stacks share a five-step loop, whether the vendor calls it Company Surge, a buying-stage score, or buyer intent.

Signal Collection

Vendors pull activity from sites you own, partner networks, publisher pages, review platforms, or ad exchanges. Bombora runs a publisher co-op. G2 watches category and comparison behavior on its own marketplace.

Topic Mapping

Pages and actions get classified into topics, keywords, categories, or named vendors. Topic taxonomies are not comparable across vendors. A spike on "CRM software" is not a spike on your CRM.

Account Matching

Anonymous activity is resolved to a company with IP, cookies, registrations, or a modeled identity graph. This step is where students, shared offices, and VPNs become someone else's pipeline.

Scoring and Surge

The useful number is change versus that account's own baseline, not raw page views. A research-heavy company can look "hot" forever. A quiet company that suddenly researches data enrichment is the stronger change signal.

Recency, frequency, velocity, topic relevance, and content type all feed the score. Early "what is" reading is not the same event as a pricing-page binge.

Activation

The score lands in a CRM, MAP, ad platform, or sales-engagement tool. HubSpot Buyer Intent is one MAP-native version of this last mile. Activation is the part most programs skip, then blame the feed.

Types of Intent Data

For B2B buying research, the useful split is where the behavior was observed, not a generic cookie taxonomy.

Demandbase splits the types by where the activity happened.

First-Party Intent Data

Three pricing-page visits in a week is a fact you can inspect. A demo replay is a fact. Both live on properties you control: site, product, email, webinars, CRM, MAP.

The catch is coverage. First-party only sees buyers who already found you. Adam Robinson (founder and CEO of RB2B) put the limit in one sentence: a website visit is a great signal, and it is still not enough of one.

Person-level identity on your domain is a separate product. That is visitor tracking, not a co-op surge.

Second-Party Intent Data

G2 Buyer Intent is the common buy: category views, comparison-page hits, and pricing-page activity on a review marketplace. You are licensing another organization's first-party data, sold or shared on a contract.

Publisher-owned portfolios sit here too. Informa TechTarget sells Priority Engine against permissioned readers across its own media, not a bidstream scrape. The fidelity is higher because the publisher saw the registration.

The catch is presence. The buyer has to be on that platform. You pay for the slice of the market that already uses it.

Third-Party Intent Data

Third-party aggregates activity you do not own. Inside that bucket, collection method matters more than the label.

Co-op / publisher collective. Bombora Company Surge is the reference design: tagged content consumption across a B2B publisher network, scored against each account's baseline. Bombora reports 5,000+ B2B sites and nearly 4.9 million unique domains, with 86% of co-op data exclusive to Bombora.

Publisher-owned portfolio. Foundry and Informa TechTarget again, when you buy their media graph rather than a multi-publisher co-op. Narrower. Closer to a person or buying group.

Ad-exchange / bidstream. Huge volume, weaker context. Cognism describes bidstream as scale without the context needed to know whether an account is genuinely in-market. Prefer a consent-based co-op over bidstream if you have the choice.

Social and public events. Job changes, hiring, competitor engagement. These are often free and person-level. On r/sales, a new VP or a hire against a broken motion beats a Bombora topic spike as a reason to work the account.

"Free" usually means leftover G2 page-view surplus or first-party only. It does not mean a full Company Surge feed.

Account-Level vs Contact-Level

Almost all third-party surge is account-level. You learn that Acme is researching marketing attribution. You do not learn who, what title, or whether budget exists.

A Company Surge score names the building, not the floor. Vendor pages skip that ceiling. Sellers already feel it.

Enterprise reps say the same thing in plain language:

"Intent is mostly noise. My issues using it in the past were that the intent is org wide, not individuals. I work ENT, knowing someone at Coca Cola researched cyber security was not helpful."

u/garden_gnorm in r/sales (February 2026)

Putney Cloos (CMO at Bombora) describes the same ceiling from the co-op side: account-level intent is "Boeing or Pfizer." In her telling, that spike could be one person or ten people on a buying committee.

Person-level is a separate purchase: visitor ID on your domain, named review-site users, publisher-owned opted-in contacts, or a contact-graph add-on such as ZoomInfo Intent or Cognism. Do not assume every contact database licenses the same co-op.

Benefits of Intent Data

Time Outreach to In-Market Accounts

Most of your TAM is not buying this quarter. Those out-of-market accounts will ignore a cold sequence.

The feed is how you spend AE time on the slice that is moving. 6sense found buying groups still purchased from their preliminary favorite 77% of the time, after ranking vendors before first contact.

See Accounts That Never Hit Your Site

First-party is precise and late. Third-party is how you notice an ICP account researching the category on publisher sites you do not own. That is the discovery job the co-op was built for.

Use it as a secondary filter on an existing target account list. Suggested names that miss ICP stay off the list.

Personalize to the Topic, Then Measure Speed

A surge on "data enrichment" is a reason to lead with that problem, not a generic pitch. Pair it with an SLA.

Workato studied lead response at 114 B2B companies: average first personalized email took about 12 hours, and nearly 1 in 5 never responded by email. A scored account that sits five days is a purchased alert, not a program.

Challenges and Limitations

Account-Level Surge Is Not a Sequence Trigger

"Apple is showing interest in commerce" is an account flag. On r/sales, that is the live complaint, not a footnote.

Require a verified contact in the buying group before outbound. Hot score plus weak contactability goes to research or paid media, not an auto-dialer.

Shared Feeds Become Personalized Spam

The same co-op is for sale to you and every competitor. Once a model can write a customized email from the same surge, the edge is gone.

"It's hard for me to see how paying for these signals works well if anyone can pay for them and have their AI write personalized emails about those exact same signals. I'm hearing execs say they get 10-15 cold emails/day that are all beautifully written and customized based on their LI, pods they've been on, intent signals like you're mentioning."

u/TheGoalIsToBeHereNow in r/sales (February 2026)

Win on speed, first-party confirmation, and a warm path. The conversion contrast practitioners treat as real is warm versus cold on the same signal, not a better feed.

Hiring, Students, and Partners Look Like Buyers

Careers-page traffic, student research, consultants, competitors, and low-authority employees all produce topic spikes. Account-matching errors and stale signals add another layer.

On r/marketing, practitioners describe living in the dashboard as a daily checkbox for leadership rather than a working queue. That is a workflow failure as much as a data failure.

Suppress careers and education topics. Check content stage (early "what is" versus late pricing). Confirm decision-makers are in the activity, not one intern.

Privacy Is Operational, Not a Vendor Checkbox

Work emails, titles, and direct phones sit in scope for GDPR, CCPA/CPRA, and a growing set of US state laws. Treat "B2B data isn't covered" as a vendor comfort story, not a legal finding.

Abmatic treats source class as the risk ladder: first-party lowest, second-party medium (partner DPA), third-party highest because you do not see original collection. Log where the identity came from, why you may use it, which action is permitted, and what happened next.

This is not legal advice. Do not rewrite a topic surge as "this person researched us and consented."

How to Act on Intent Data

Putney Cloos (CMO, Bombora) told marketers to pick one or two use cases, prove the motion in a narrow slice, then add on. Sales prioritization is the usual start. Content strategy is a valid first win if sales will not adopt the queue.

Do not auto-route a lone third-party surge. Confirm fit, first-party activity, and a reachable person.

GSDSI publishes the same idea as score bands: Tier A to SDRs inside 24 hours, B to nurture, C as research-only. SLAs without freshness decay reward vendors that dump historical surges into the feed.

Eight plays that keep showing up:

1. Prioritize in-market names already on the TAL. This is a secondary filter. DemandScience is explicit: names that miss ICP do not enter the list.
2. Score fit first, then intent. Abmatic: the list says who the team works; the score says when. A non-target with a high score still does not get worked.
3. Personalize to the topic, not a generic sequence.
4. Competitive displacement when the account researches a named rival.
5. Expand with lookalikes of customers that show high third-party research. Do not let the platform become the TAL.
6. Cover the buying group. One person reading about CRM is casual; three people from different departments is a committee. 6sense has long put buying groups at 10+ people on a $250K-average deal, a planning number rather than a 2025-only stat.
7. Watch expansion and churn when an existing customer researches a competitor or an adjacent category.
8. Do not auto-fire SDRs on a lone surge. Confirm first-party, fit, and contactability.

On r/sales, the working speed rule is: when a company spikes, find the role, verify the contact, reach out the same week. Signal without a verified person is trivia. Hybrid and first-party hits still belong inside the same-week window, not a weekly batch.

Robinson's version for a first-party hit is three CRM workflows, not a created deal: add to the score, start a cadence, or alert the account owner.

Intent Data Providers: Feed vs Platform

2026 listicles dump Bombora, 6sense, and Demandbase into one "providers" column. They sell different jobs. Shop the data-vendor spoke when you want a ranking.

Bombora is a co-op feed. 6sense and Demandbase are activation platforms that consume feeds. 6sense names Bombora, TechTarget, TrustRadius, and G2 as complementary partners.

Buying standalone Company Surge plus 6sense can duplicate the same co-op. Confirm it in the SOW.

Demandbase is different: Demandbase scores Bombora topics as a partner feed. Demandbase's help center requires a separate paid Bombora license, and the sync is weekly. It is not a silent resale bundled into every Demandbase seat.

Cognism states on its own product page that it uses Bombora. ZoomInfo pages extracted for this article do not name Bombora. Do not assume the same license.

Major vendors do not publish sticker prices. Honest line: custom, typically mid-five to six figures for a feed or an enterprise platform. Skip any blog that prints a single sticker price as if it were list.

Skip the category if the list is too small to separate hot from cold, the sales cycle is shorter than the third-party lag window, or you have no TAL, no CRM hygiene, and no SLA. A feed prioritizes an existing list. It is not a substitute for one.