Intent signals are one of those RevOps concepts that get discussed constantly in demand-gen strategy meetings and implemented inconsistently everywhere else. Most B2B revenue teams have access to at least some intent data — website analytics, marketing automation behavioral data, possibly a third-party intent platform — but the gap between having the signals and acting on them systematically is wide enough to drive an entire dormant pipeline through.
This guide is not a vendor comparison of Bombora versus G2 Buyer Intent versus Demandbase. It's a framework for understanding what different signal types actually tell you, what they don't tell you, and how to build a tiered action model that applies the right response to the right signal for a dormant lead reactivation use case specifically. Active prospecting and reactivation require different signal logic — most intent data implementations are designed for the former, which is why they underperform for the latter.
First-Party Signals: The Highest-Reliability Data You Already Have
First-party behavioral signals come from your own digital properties — your website, your product (if you have a product-led motion), your email platform, and your marketing automation system. For dormant leads, first-party signals are the most actionable because they tell you something the lead directly did in relation to your specific product, not just your category.
The highest-value first-party signals for reactivation, ranked roughly by conversion predictiveness: direct return to pricing page (a dormant lead who visited your pricing page was at some point past general awareness and into evaluation mode — a return visit after 60 days of silence is a strong indicator that evaluation is resuming); multiple return visits within a 7-day window (implies an active research sprint, not idle browsing); time-on-site on comparison or ROI pages (visitors spending 4+ minutes on your "EVE vs. alternatives" or "ROI calculator" pages are engaging with late-stage decision content); and integration documentation visits (a lead looking at your Salesforce or HubSpot integration docs is checking whether you fit their existing stack — this is a late-funnel signal even if they haven't requested a demo).
Lower-value but still useful first-party signals: blog or content visits (mid-funnel awareness, useful for sequencing context but not strong reactivation triggers on their own), webinar or event registrations (intent signal correlated with active research, stronger for net-new than for reactivation), and email link clicks from your nurture sequences (engagement with email indicates the contact is still reachable and paying some attention, but the click itself doesn't tell you where they are in a buying journey).
The operational challenge with first-party signals is connecting them to the CRM record reliably. If a dormant contact is visiting your site while not logged in, and hasn't clicked a tracked email link recently, your visitor identification rate (the percentage of returning visitors you can tie to a known contact) may be low — typically 5 to 20 percent for most B2B sites, depending on traffic volume and how mature your reverse IP and cookieless identification setup is. This is a real limitation that intent signal implementations regularly underestimate.
Third-Party Intent Data: What Bombora and G2 Actually Tell You
Third-party intent data platforms aggregate signals from across the web — content consumption on publisher sites, review platform activity, search behavior data from partner networks — and map them to company-level buying intent scores by topic cluster. Bombora's Company Surge data, G2 Buyer Intent, and similar products give you a weekly or near-real-time view of which companies are researching topics related to your product category.
For reactivation use cases, third-party intent data is most useful for one specific task: identifying which companies in your dormant lead database are currently in an active buying cycle for your category, so you can prioritize those contacts for reactivation outreach ahead of the rest. If you have 2,000 dormant leads from 800 companies and Bombora tells you that 45 of those companies are showing elevated intent on "sales engagement" or "revenue operations" topic clusters this week, those 45 companies' contacts move to the top of your reactivation queue — regardless of their first-party signal status.
What third-party intent data does not tell you, and this is critical: it does not tell you which specific person at that company is doing the research. The contact who originally engaged with your marketing may no longer be in a position to buy — they may have changed roles, changed companies, or moved on from the evaluation. The Bombora spike is at the company account level, not the individual contact level. When you route a dormant contact to reactivation based on third-party intent, your sequence needs to acknowledge the time elapsed and probe for whether they're still the right person to speak with, rather than assuming continuity from the original engagement.
Signal freshness is also a real operational issue. Most third-party intent platforms update on weekly or bi-weekly cadences. A company showing elevated intent this week may have already made a purchasing decision by the time your sequence reaches their contact three days from now. The faster you can act on third-party intent signals, the more value they provide — which is why intent data workflows that sit in a spreadsheet and get reviewed in a weekly RevOps meeting are substantially less effective than automated routing that triggers a sequence enrollment within hours of the signal appearing.
Product Usage Signals for PLG or Freemium Models
For SaaS companies with a product-led growth component — a free tier, a freemium product, or a self-serve trial — product usage signals are the highest-quality intent data available. A trial user who created an account, used the product lightly, and then stopped logging in for 45 days is a dormant lead with a behavioral fingerprint. If that user returns to the product and completes a meaningful action — creating a new workflow, inviting a colleague, connecting an integration — that return event is one of the strongest reactivation triggers available.
The specific signals that most predictably precede trial-to-paid conversion in product-led SaaS: feature activation of a core value-delivering feature (the "aha moment" completion on a second visit after dormancy), seat expansion on a free tier (inviting additional users signals organizational buy-in growing), and integration connection (connecting to an existing tool in their stack shows they're committing to the product enough to wire it in).
Product usage signals require a product analytics setup (Mixpanel, Amplitude, Segment, or similar) with clean event tracking and a bidirectional sync to your CRM — so that when a dormant trial user in Salesforce fires the "integration connected" event in Mixpanel, that signal surfaces in the contact record and can trigger a sequence enrollment in Outreach or Salesloft automatically. Getting that pipeline built correctly typically requires 2 to 4 weeks of engineering work, but the signal fidelity justifies it for most PLG companies.
Signal Combination and Prioritization: Building a Tiered Action Model
The mistake most RevOps teams make with intent data is treating each signal type in isolation. A single return website visit isn't strong enough to route a dormant lead to SDR follow-up — too much noise. A single Bombora spike at the account level isn't strong enough on its own either — the contact might be irrelevant to the current evaluation. But a dormant lead whose company is showing elevated Bombora intent AND who has returned to your pricing page in the past 7 days is a fundamentally different situation.
A workable tiered action model for reactivation: Tier 1 (SDR immediate follow-up) — any two or more high-value signals firing within the same 14-day window; for example, third-party account-level intent plus first-party pricing page visit. Tier 2 (automated multi-touch sequence enrollment) — one high-value first-party signal without third-party corroboration, or one moderate third-party signal without first-party confirmation. Tier 3 (low-touch nurture or monitoring hold) — single low-value signals, or signals from contacts at companies that fail your current ICP criteria on firmographic dimensions (too small, wrong vertical, wrong geography for current go-to-market focus).
The ICP filter is important and often omitted from intent signal workflows. Third-party intent data will surface companies that are researching your category but that are nowhere near your addressable market. Including those in your reactivation routing wastes SDR capacity. Running a firmographic ICP filter — headcount range, industry vertical, revenue range if available, technology stack match — before action routing dramatically improves the quality of the resulting outreach queue.
The Signal Decay Problem and Reactivation Timing
Intent signals have short half-lives. A company actively evaluating vendors is typically on a 2 to 6 week active research window before they either make a decision or defer it. A first-party pricing page visit from a dormant lead is most actionable in the 24 to 48 hours following the visit. A third-party intent spike is most actionable within 72 hours of the signal date.
This creates a challenge for reactivation workflows that rely on weekly manual review processes. By the time a RevOps manager reviews the intent signal report on Friday for leads that spiked on Monday, the actionable window for at least some of those leads has passed. Automated signal-to-sequence routing — where a qualifying combination of signals triggers an immediate sequence enrollment in Outreach or Salesloft without requiring manual review — closes this gap, but requires careful threshold setting to avoid flooding your SDR queue with low-quality automated assignments.
We're not saying manual review of intent signals is worthless — for Tier 1 high-value leads, human review of the contact context before outreach is often worth the delay. We're saying that for the larger volume of Tier 2 and Tier 3 signals, automation with well-designed thresholds consistently outperforms weekly manual review, both on response rate and on pipeline contribution per hour of SDR time invested.
Practical Implementation: What to Build First
If you're starting an intent signal program from scratch and need to sequence the work, the priority order based on signal quality and implementation effort is: first, get your CRM-to-website analytics connection clean and reliable — known visitor identification, UTM parameter consistency across all marketing channels, and event tracking on your highest-value pages (pricing, integrations, demo request). This is your first-party foundation and is a prerequisite for everything else. Second, build the CRM workflow rules that create a "reactivation signal" activity record when a dormant contact fires a tracked website event — this makes signal visibility native to your Salesforce or HubSpot workflow without requiring a separate tool. Third, if you're adding third-party intent data, start with a single platform and a single topic cluster directly aligned with your product category, and measure signal-to-opportunity conversion for 60 days before expanding scope. Platform sprawl — subscribing to five different intent data providers simultaneously — creates data conflicts and makes it impossible to identify which signals are actually predictive for your specific ICP.
The most underappreciated implementation consideration is contact-level vs. account-level signal routing. Most third-party intent platforms are account-level only. If you have three contacts from the same dormant account, you need a rule for which contact receives the reactivation touch when an account-level intent signal fires. Routing to the most senior title, the most recent engagement, or the contact with the most complete firmographic data each have defensible arguments — but you need an explicit rule, not ambiguity that produces three simultaneous outreach attempts to the same account from different reps.