Comparison

Company signals vs third-party intent data

Behavioural intent watches people read. Company signals describe the company itself. What each kind delivers, what each is built to show, and how to join and test the two in one account ranking.

Updated 27 October 20268 min read

Two different things are sold as intent data. One measures what people at a company read: articles, reviews, comparison pages. The other describes the company itself: dated signals about the company, scored by topic, each with evidence a person can open. This comparison sets the two side by side, using the public documentation of Bombora and G2 for the first and the Fokals datasets for the second. By the end you can tell which kind a score is, what each kind is built to show, and how to use both in one account ranking.

Fokals is the worked example of the second kind. Its intent scores are evidence-backed: every score comes with the dated evidence behind it, so a rep, an analyst or a model reviewer can open the evidence and check it. The two kinds report different things, which is why this comparison ends with a join that runs them together.

Two kinds under one name

Behavioural intent is third-party data about attention. A vendor observes content being consumed on sites it has access to, attributes the activity to a company, classifies the content by topic and reports where a company's reading has risen. Bombora's own definition is that intent data shows when buyers are researching topics across the internet, based on the content they consume. What is observed is a person reading. What is reported is the account.

Company signals describe the company. Each record is dated, kept at the level of the company and open to a check: a person can see what was recorded about the company and when.

The two report different stages of a purchase, which is the reason to tell them apart. Reading can rise with no budget behind it, and a company can commit to a purchase without anyone reading on a monitored site. Research shows interest in a subject. A company signal shows a step the company itself has taken.

What Bombora, G2 and Fokals deliver

Bombora's Company Surge is derived from its Data Co-op. Its site says research consumption is collected through a consent-driven tag on every site in the Co-op, and its Co-op page describes direct relationships with member publishers and brands, with engagement captured from gated, paywalled and open content. The site states that Bombora monitors company research activity against more than 25,000 topics. Its site describes scoring that is relative to the account: for every pairing of account and topic, the most recent three weeks of activity are compared with a 12-week historical baseline. Its guidance for customers treats a score of 60 or more on a topic as a spike.

G2 Buyer Intent comes from the research that buyers do on G2. G2's documentation describes it as data about buyers researching a vendor's product across G2, sent at the level of the product, and says it also includes research activity from Capterra, Software Advice and GetApp. A signal is triggered when a buyer views the vendor's product profile or its pricing page, a category page that includes the product, a comparison that includes it or an alternatives page, and a competitive signal records views of a competing product's pages. G2's documentation says two scores are calculated for each company, a Buying Stage (awareness, consideration or decision) and an Activity Level (low, medium or high), and that G2 updates both daily. It adds that the vendor's G2 plan determines which signal types it receives.

The Fokals intent dataset delivers three datasets. Intent Scores gives a weekly score from 0 to 100 for each company and topic, across 69 topics in nine groups, from advertising and marketing to data, technology and business systems. Each score comes with the dated evidence behind it, and a surge flag marks a company that has become active on a topic against its own record. Company Signals delivers dated company signals daily, each with its kind and the topics it bears on, and Company Funding delivers private capital raises reported in regulatory filings. The methodology describes each dataset.

Bombora Company SurgeG2 Buyer IntentFokals intent
What a record describesAn account's research on a topic, across the sites of its Data Co-opA buyer company's research on a vendor's product, its category and its competitors on G2A company's activity on a topic in one closed week
SubjectsMore than 25,000 topics, as its site statesThe vendor's product, its category and its competitors69 buying topics in nine groups, from advertising and marketing to data, technology and business systems
MeasureThe most recent three weeks against a 12-week baseline, for each account and topicBuying Stage and Activity Level for each company, updated dailyA weekly score from 0 to 100 for each company and topic, with a surge flag and the dated evidence behind it, written once after the week closes
DeliveryIntegrations with advertising, marketing, sales and CRM platforms, or a flat file or APImy.G2, CSV exports and integrationsREST API and bulk files in JSON, JSON Lines or CSV, delivered direct
Built forTeams that use go-to-market tools: advertising, marketing, sales and CRM platformsVendors with a product on G2Revenue teams, funds and data platforms that need a dated, verifiable reason behind every score

The delivery row for Bombora follows its integrations page, and the fields G2 returns, including the buyer's company domain, are in its data reference.

What each kind can show

Behavioural intent can show interest before the company itself moves. People read about a category before a role is advertised or a tool appears on a page, and sometimes neither ever follows. It can also separate narrow subjects. A taxonomy as large as the one Bombora states draws fine distinctions between subjects, and G2's signals are specific to one product: its profile, its pricing page, a comparison that includes it.

Company signals show a step the company has taken. They also show evidence that a person can check: each Fokals score comes with its dated evidence, and each week is written once after it closes and never revised, so the score you ranked on is the score you find when you audit the ranking later.

Read each for what it records. A rise in reading records attention to a subject. A company signal records a step the company took, so it marks the point at which interest became a commitment. That is the dated reason a rep can open a call with, and the feature a model can be tested on point-in-time.

Reading the evidence behind a score

The difference is clearest when a rep asks why an account is on the list. With Fokals the answer is a set of rows from Intent Scores.

select week_start, score, surge, evidence
from company_intent_weekly
where company_id = :company_id
  and topic = 'crm'
order by week_start desc
limit 4;

Illustrative: Acme Robotics scores 58 on the CRM topic in the latest week, is flagged as a surge and carries three dated items of evidence. Each item states what was recorded about the company and on which day, so the rep can open it before the call.

Three dated items of evidence say more than the number does. The surge flag marks an intent surge: a company that has become active on the topic against its own record. Beside the scores, the Company Signals dataset delivers dated company signals daily, each with its observation time, its kind and its topics.

Using both in one ranking

If you license a behavioural feed as well, keep the two sources in separate tables and join them at the account. A behavioural feed may identify companies by domain, as G2's data reference does with its company domain field, while Fokals rows are keyed on the company ID, so the bridge is a table of domains, built by domain matching.

with domains as (
  select distinct domain, company_id
  from company_technologies
),
acts as (
  select company_id, score, surge, evidence
  from company_intent_weekly
  where topic = 'crm'
    and week_start = date '2026-09-28'
)
select b.domain,
       b.reading_surge,        -- from your behavioural feed
       a.score, a.surge, a.evidence
from behavioural_feed b
left join domains d on d.domain = b.domain
left join acts a    on a.company_id = d.company_id;

Read the result as four cases.

A company signal on the topicNo company signal
Reading has risenAttention and action agree. Work the account now and open with the evidenceResearch with no step taken yet. Nurture, and watch Company Signals for the first signal
Reading is flatA step taken without visible research. A decision is under way, so open with the evidence and learn where it standsNo evidence from either kind. Keep the account in the plan

A surge from one source is not comparable with a surge from the other, so do not average them. Keep both columns in the queue and let the rep see which evidence put the account there.

Test the combination before you route leads on it. For each account that opened an opportunity, record whether each source flagged it in the 90 days before, and do the same for a matched set that did not. Fokals weekly scores are written once, after the week closes, and are never revised, so the test reads each score exactly as it stood in the week you would have acted on it.

What each is built for

  • Behavioural intent is built to observe research: buyers who read for months before they act, subjects as narrow as a single product, and views of your product's profile, its pricing or a comparison that includes it, which is what G2's signals record. The guide to Bombora alternatives covers that kind of source.
  • Company signals are built for evidence: a reason that a rep or an analyst can verify, weekly scores written once and never revised for a product or a model, and a point-in-time record that an investor can test as readily as a seller can act on it.
  • Both are worth running when a wrong call is expensive, because agreement between attention and action is stronger evidence than either alone.

How Fokals delivers its signals

Scores are written weekly and signals arrive daily. Intent Scores, Company Signals and Company Funding are delivered direct, by REST API and as bulk files in JSON, JSON Lines or CSV, which you load where your scoring runs. The feed of signals runs oldest first from a time you set, so the last cursor is the bookmark for incremental sync. A score keeps the definition it was written under, and a breaking change ships with at least 90 days' notice, so a ranking or a model built on the scores stays stable.

Two further guides start from here. What a Fokals intent score gives you shows how to read a row, and prioritising accounts with intent scores turns the scores into a weekly queue.

Frequently asked questions

What is third-party intent data?

Third-party intent data is evidence of buying interest gathered outside your own website and CRM and licensed from a vendor. Bombora defines it as signals collected outside a company's owned and paid experiences. The kind that Bombora and G2 describe is behavioural: it measures the content that people at a company consume, on a network of publisher sites or on G2, and reports a rise by topic. It reaches accounts that have never visited you, which first-party data cannot.

What is the difference between behavioural intent data and company signals?

Behavioural intent measures attention: what people at a company read, attributed to the account and scored by topic. Company signals describe the company itself: dated steps it has taken, each with evidence a person can open and check. The first observes interest in what is read, often early and in narrow subjects. The second records a step already taken.

What evidence stands behind a Fokals intent score?

Every weekly score comes with the dated evidence behind it. A rep can open what stands behind a score before making contact, and a model reviewer can trace a feature back to dated facts. The Company Signals dataset delivers dated company signals daily, for teams that want the events on their own as well as the weekly score.

Can you use Bombora or G2 intent data together with company signals?

Yes. Keep each source in its own table and join at the account, with the company's domain as the bridge. Rank first the accounts where reading has risen and a company signal has been recorded, treat a rise in reading alone as early interest, and treat a company signal alone as a sign that a decision may already be under way. Test the combination against your own opportunities before you route leads on it.

How does an intent surge differ between the two kinds?

Both mark a company that stands out against its own recent past, and they report different things. Bombora's site describes comparing the most recent three weeks of content consumption with a 12-week baseline for each account and topic. A Fokals surge flag marks a company that has become active on a topic against its own record, on a weekly score that is written once. A surge from one source cannot be compared with a surge from the other.

What does a company signal record, and about whom?

A company signal is one dated event about a company. A record in Company Signals names the company, the kind of event, the topics it bears on and the observation time, and a leadership change is recorded by the role concerned. It is company-level data throughout. Behavioural sources start from the activity of people, so ask the vendor what is collected about individuals, on what basis, and what reaches you.

The queries and code on this page are examples to adapt. Test them in your own environment before you rely on them.

What this page says about the products it names was checked against their public documentation on 4 October 2026. Product and company names are trademarks of their owners. Fokals is not affiliated with them or endorsed by them.