How 1st-, 2nd- and 3rd-party buying signals turn into qualified meetings, and the CRM fields you need so finance can audit where each meeting came from.
TL;DR
Buying signals turn into meetings when every signal goes through the same path: match it to an account and a person, verify the contact, score it, have a human approve the message, send it on the right channel, and write the result back to the CRM. Skip any step and the signal turns into CRM clutter. Most intent-data pages stop at the list of signal types. This one covers the steps after the signal fires, including the CRM fields that let you prove a meeting came from a signal six months later.
A buying signal is evidence that an account is more likely to care right now: a job post for the role you replace, a new tool in their stack, three visits to your pricing page, a champion who just changed companies. Intent data is the commercial name for some of those signals. It doesn't replace list quality, deliverability or judgment about who to contact.
| Layer | What it is | Examples | How much to trust it |
|---|---|---|---|
| 1st-party | Data you already own | Pricing-page visits, product sign-ups, form fills, CRM stage changes, replies to past outbound | Highest. Usually underused because it never leaves the marketing tool. |
| 2nd-party | Data from a partner or platform you work with | Partner account overlap, review-site activity, champion job changes, engagement with your founder's posts | High when you can tie it to a named person. Low when you can't. |
| 3rd-party | Public or purchased market data | Job openings, tech installs, funding news, website-visitor ID tools, intent topics from providers such as Bombora | Lowest. High volume, high noise. Score hard before anyone gets an email. |
Start with 1st-party. If target accounts already visit your pricing page every week, you don't need a new intent provider yet. It needs those visits matched to people and routed to a rep the same day.
Every signal needs a person and a working channel. Run enrichment as a waterfall: your own cached data and pattern matches first, paid email and phone finders next, the expensive lookups last, then one verification step at the end. Treat accept-all (catch-all) domains as a decision, not a pass. We cover the build in the email waterfall and Clay for B2B prospecting playbooks.
A hot account shouldn't get three unrelated sequences from three tools. Email, LinkedIn and phone should run off the same scored list, the same offer and the same suppression list, with one place where a person reviews outbound before it goes. When a reply or a booked meeting comes back, it should write to the CRM with the source fields already attached.
| Step | Who owns it | What it produces |
|---|---|---|
| Signal capture | GTM engineer or ops | Normalized signal events in one table |
| Enrich and verify | Data ops | A deliverable contact, or an honest miss |
| Score | RevOps with sales leadership | A priority tier and the kill rules |
| Draft | Campaign strategist, often with an AI draft | Copy and channel plan ready for review |
| Review | Client or a named reviewer | Ship, edit or kill |
| CRM writeback | The system, not a rep | Meeting, outcome and source fields |
If finance can't trace a meeting back to the signal that started it, the program will lose its budget the first time someone asks what it produced. Crediting is a writeback contract you agree on before launch, not a dashboard you build afterward. Capture the fields at activation, before the AE is involved, so first-touch, influenced and opportunity links still hold up months later.
Minimum fields to write back
| Failure | What it looks like | Fix |
|---|---|---|
| Unverified contacts | Signals attached to the wrong person, an old title or an email that bounces | Waterfall plus a verification step; decide catch-all handling explicitly |
| No human review | Automated copy fires on every job-change alert; the domain and the brand take the hit | A person approves accounts and messages before send |
| Too many disconnected tools | Website-visitor ID in one tab, intent topics in another, the sequencer somewhere else, nothing in the CRM | One capture table and one CRM writeback contract |
| Vanity dashboard | A count of "intent accounts" with no definition of a qualified meeting | Define a qualified meeting, then report meetings and misses by segment |
| Data stuck with a vendor | The lists and Clay tables live in an agency's workspace and leave when they do | Build in your own accounts from day one |
| Approach | Works when | Breaks when |
|---|---|---|
| DIY Clay and a sequencer | You're testing signals on a narrow ICP and someone owns enrichment day to day | Nobody owns deliverability, replies or CRM writeback |
| Appointment-setting or cold email agency | Your ICP and offer already work and you want meeting volume without owning the machine | You want a signal system you keep, or past outbound failed and nobody knows why |
| Fractional GTM team | The bottleneck is the whole path: signals, enrichment, deliverability, review and CRM | You only want a short burst of meetings and don't want anyone touching your stack |
Astra GTM is in the third row. We build and run revenue systems inside your stack with your GTM leadership: market data, signals, outbound and reporting. Engagements have a three-month minimum, most run past twelve months, everything we build stays in your accounts, and nothing sends without your review. Pricing is scoped per engagement. If you only need meetings booked against an ICP that already works, an appointment-setting agency is probably the cheaper call.
Enter your email and we'll send you this playbook, plus the open GitHub repo of setup skills when it ships.
We build and run these systems embedded with your team.