What counts as evidence
Consented first-party data, attributable research, public company news, or a contact-level change with source, date, entity, and exact fact.
Verifiable programmatic library
20 signals × 25 industries × 10 roles: 5,000 English playbooks with evidence, exclusions, messaging, compliance, and measurement.
Direct answer
A B2B buyer signal is an observable event that may change an account’s context. It becomes useful only after source, recency, ICP, and role verification, followed by attribution to a commercial outcome. A visit, company event, or job change never proves purchase intent on its own.
Consented first-party data, attributable research, public company news, or a contact-level change with source, date, entity, and exact fact.
It does not establish willingness to buy, budget, timing, or the identity of an invisible individual. Each requires separate qualification.
Qualification method
Preserve the observed fact, source, date, and corroboration without turning it into a commercial conclusion.
Apply the ICP, exclusions, and geography before finding a contact or drafting a message.
Verify that a public role actually owns the affected workflow; do not infer ownership from title alone.
Attribute qualified replies, held meetings, activated trials, and paid customers to the original signal and cohort.
Measurement cohort
The first decision covers 7 signals × 5 industries × 4 roles × 2 languages. Compare impressions, qualified organic clicks, engagement, signup, trial, and first payment; do not scale based on page count.
FAQ
An observable event that may change an account’s context: consented first-party data, attributable research, company news, or a contact-level change. It is not proof of a purchase decision.
Job change, funding announcement, leadership hire, technology adoption, pricing-page visit, product launch, and competitor switching.
The 7 × 5 × 4 × 2 subset creates a readable demand, engagement, and conversion decision without confusing URL volume with performance.
Compare impressions, qualified organic clicks, engagement, signup, trial, first payment, revenue, cost, and operator time. Strengthen useful families; do not expand permutations without evidence.
Crawlable navigation
a verified public role transition with the person, company, title, and effective date aligned.
02a company announcement or reputable filing that names the round, date, and intended use of funds.
03multiple current openings in the same function, geography, or capability with stable source URLs and recent dates.
04an official appointment naming the executive, remit, start date, and reporting context.
05a current, attributable signal from documentation, job requirements, implementation pages, or a verified technology dataset.
06a verified disappearance across multiple observations or an explicit migration or deprecation statement.
07first-party consented analytics that identifies an eligible account cohort without exposing or guessing an individual visitor.
08an official launch page or release announcement with scope, audience, availability, and date.
09official market-entry, entity, office, hiring, localization, or regulatory evidence tied to a named region and date.
10a joint or attributable announcement that defines the partners, scope, customer value, and launch status.
11a primary regulator or standards body source defining scope, effective date, affected entities, and obligations.
12an official disclosure, regulator notice, or attributable status update with confirmed scope and timing.
13first-party request, public evaluation language, migration hiring, or another attributable signal of active category research.
14a first-party contract record, buyer-provided timeline, public procurement notice, or reliably verified renewal date.
15consistent, recent headcount movement from company reporting or a reputable dataset with a stated methodology.
16an official office announcement, property record, local hiring plan, or operational page naming location and timing.
17an official transaction announcement or filing stating parties, status, timing, and strategic rationale.
18buyer-provided planning dates, public fiscal calendars, procurement schedules, or first-party opportunity history.
19consented first-party engagement with a defined asset, timestamp, campaign, and account-level attribution boundary.
20an official implementation, migration role, integration change, documentation update, or verified technology movement.
Move from signal to decision
2026 sources
These categories document how the market describes signals. They do not validate a specific account, person, or purchase decision; every playbook preserves that separation.