Intent data vs. buying signals: what each one tells you

Intent data is information that suggests a company may be researching a topic, based on what people there read, search for or visit online. Buying signals are observable events at a company, such as a new leader, a funding round or a cluster of job postings, that you can see, date and check yourself.

Both can help a seller decide which accounts to look at. They answer different questions, though. Intent data hints at what a company might be thinking about. Buying signals show what a company has actually done. Knowing the difference helps you use each one for what it’s good at.

Three kinds of evidence, defined plainly

Third-party topic intent

Third-party intent comes from outside your company. A data provider watches content consumption across many websites, such as articles read or topics searched, and groups that activity by company. If activity on a topic rises at one company compared to its usual level, the provider may flag the company as “showing intent” on that topic.

It can cover accounts that have never visited your site. But you usually can’t see who did the reading, what exactly they read or why.

First-party intent

First-party intent comes from your own channels: visits to your website, pricing page views, content sign-ups, webinar sign-ups or replies to your emails. You collect it directly, so you know where it came from.

It is usually more specific and easier to trust. The limit is reach: it only covers accounts that have already found you.

Observable account events

These are the buying signals covered across our guides: leadership changes, funding, hiring patterns, product launches, expansion and technology changes. They’re public, they have a date, and they usually come with a source you can open and read. Our guide to B2B buying signals covers them in more depth.

They tell you something changed. They don’t tell you whether anyone at the company is thinking about your problem yet.

What each one is good and bad at

Four questions help you judge any source of account evidence:

• Granularity: How specific is it? Does it point to a team, a topic, a person or just a company?
• Explainability: Can you say in a sentence why the account was flagged?
• Verifiability: Can you check it yourself by opening a source?
• Freshness: How quickly does it show up, and how quickly does it go stale?

Here is how the three types tend to compare. Treat this as a general guide; individual sources vary a lot.

	Third-party intent	First-party intent	Observable events
Granularity	Company and topic, rarely the person	Often page, visit or contact level	Company, team or named leader
Explainability	Often a score with limited detail	Clear: “visited pricing twice”	Clear: “new VP started last month”
Verifiability	Hard to check yourself	You can check your own records	Usually a public source you can open
Freshness	Shifts week to week, can be noisy	Very current, fades fast	Dated; useful for weeks, then fades

None of these is “best.” Third-party intent can widen your view. First-party intent shows real engagement with you. Observable events give you a specific, checkable reason to reach out.

How to combine them without double counting

Double counting is when one real-world change shows up in several sources and gets added to an account’s score more than once. It makes an account look hotter than it is.

For example, a company announces a funding round. A news feed flags the funding. A data provider shows a jump in research on “scaling sales teams.” Someone from the company reads your blog post about hiring reps. That may be three pieces of evidence, or it may be one event echoed three times.

A few habits help:

1. Group evidence by the underlying change. Ask “what actually happened here?” and attach related evidence to that one event.
2. Let the strongest piece lead. Use the most specific, checkable item as the main reason, and treat the others as support.
3. Cap how much one event can add. If you score accounts, limit how much related evidence can stack from a single change.
4. Keep fit separate. Timing evidence of any kind shouldn’t make up for a poor-fit account. Our guide on signal freshness covers how timing and fit work together.
5. Write the reason in plain words. If you can’t explain why an account moved up in one sentence, the evidence probably isn’t as strong as the score suggests.

A practical pattern: use third-party intent to decide where to look, observable events to decide why now, and first-party intent to decide how warm the conversation might be.

Questions to ask about any intent source

Before you lean on a new data source, ask its owner, whether a vendor or your own team, a few plain questions:

• Where does the data come from? What sites, channels or records feed it?
• How is a company matched? How do they know activity belongs to this company and not another?
• What does a “spike” mean? Compared to what baseline, over what time period?
• Can I see the evidence behind a flag? Or only a score?
• How fresh is it? How long between the activity and when it shows up for you?
• How was the data collected? Is it gathered with appropriate consent and in line with privacy rules?
• How often is it wrong? Ask how they measure false positives, and whether you can test it against your own past deals.

If the answers are vague, treat the data as a loose hint rather than a reason to act on its own.

The rule to remember

Intent data suggests what a company might be researching; buying signals show what a company has actually done. Use each for what it’s good at, count each real change once, and act on evidence you can explain and check.

To see how observable signals and account fit come together in one ranking, explore Signal Arena.