Intent data helps CRM teams focus on buyers who are already showing signs of interest. The real value comes from turning those signals into a workflow that prioritizes accounts, improves timing, and gives reps a better reason to reach out.
Intent data is the signal that a company or individual is actively researching a buying decision – visiting competitor review sites, reading category content, searching for pricing pages, or downloading evaluation guides. For B2B sales and marketing teams using CRM, intent data answers a question that contact records and pipeline data cannot: who is in the market to buy right now, before they’ve raised their hand with a form fill or inbound request? Integrating intent data with CRM changes prospecting from spray-and-pray outreach to timed, relevant contact with companies that have demonstrated buying behaviour. This guide covers how intent data works, the major providers, and how to connect it to your CRM effectively.
That only works if the data is connected to a process. Raw signals without follow-up logic usually create more noise than opportunity.
How Third-Party Intent Data Works
Platforms like Bombora aggregate anonymised content consumption data from a co-operative network of 5,000+ B2B publisher sites. When a company’s IP addresses and employee devices show spikes in content consumption around a specific topic cluster (e.g., “CRM software,” “sales engagement platform,” “CPQ tools”), Bombora flags that company as surging on that intent topic. This is useful because it identifies companies doing active category research before they’ve visited your website – allowing outreach to reach them earlier in the buying cycle than inbound alone.
6sense operates differently: it uses AI to model the full buying journey using first-party, second-party, and third-party signals together, and assigns each account a predicted buying stage (Awareness, Consideration, Decision, Purchase). 6sense’s account scores are generally considered more actionable than raw intent signal scores because they contextualise intent within a buying journey model.
Connecting Intent Data to Salesforce
Bombora + Salesforce: Bombora’s native Salesforce integration pushes Company Surge scores directly to Account records as custom fields. Configure which intent topics are relevant to your business (your category keywords), and Bombora updates the Account record’s surge score daily. Sales reps can filter the Salesforce account list by “Bombora Surge Score > 60” and “Account not yet an Opportunity” to identify high-intent targets. Best practice: create a Salesforce report or list view called “High-Intent Accounts – No Open Opportunity” that surfaces exactly these accounts for SDR prospecting.
6sense + Salesforce: 6sense integrates with Salesforce to push account buying stage, intent topic data, and contact-level signals to Account and Contact records. 6sense also connects to Salesforce Campaign objects – accounts in the “Decision” buying stage can be automatically added to a Salesforce campaign that triggers an SDR task. 6sense’s Salesforce integration is generally considered the most operationalised intent-to-CRM workflow available.
G2 Buyer Intent + HubSpot/Salesforce: G2’s Buyer Intent integration surfaces which companies have viewed your G2 profile, compared you to competitors on G2, or read your reviews in the last 30 days. This is high-signal intent – these companies are actively evaluating your specific product category. G2 integrates natively with Salesforce (pushing Account-level intent) and HubSpot (pushing company-level intent), allowing automatic task creation for accounts showing active G2 engagement.
Connecting Intent Data to HubSpot
HubSpot’s integration with intent data providers is less mature than Salesforce’s, but functional for most use cases. Bombora integrates with HubSpot to update Company records with surge score data. G2 Buyer Intent connects to HubSpot and can trigger HubSpot workflows – for example: when a company’s G2 intent score exceeds a threshold, enroll the company in a HubSpot workflow that creates a task for the assigned sales rep and adds the key contacts at the company to an email sequence.
For HubSpot-native first-party intent, HubSpot’s own contact activity data (page visits, email opens, content downloads) provides strong intent signals that can be used to trigger sales activities. A contact who visits your pricing page twice in one week is demonstrating intent that should trigger immediate sales outreach – this is achievable with HubSpot’s native tools without a third-party intent data provider.
Intent Data in CRM: Practical Workflow
The highest-value intent data workflow in CRM combines multiple signals: (1) Third-party intent identifies companies surging on your category. (2) First-party website data identifies whether any contacts from those companies have visited your website. (3) G2 Buyer Intent data identifies companies actively researching your specific product. (4) CRM automation creates a prioritised account list for SDR outreach with context: “Company X is surging on [category], 3 employees have visited your pricing page, and they viewed your G2 profile yesterday.” This contextualised outreach, triggered by CRM automation from intent signals, converts at 3-5x the rate of cold outreach to accounts with no intent signals.
“We’re paying for Bombora but nobody is using the intent data in Salesforce”
Intent data unused in CRM is one of the most common RevOps investments that fails to deliver ROI. The typical failure mode: intent data is pushed to Salesforce Account fields, but sales reps have no defined workflow for acting on it. The data sits unused because there’s no process for when and how to act on an intent signal. Fix: build a specific Salesforce report titled “Accounts Surging This Week – No Active Opportunity” filtered to Bombora surge score above your threshold and no open Salesforce opportunity. Assign this report to the SDR team manager as a Monday morning review task. Each SDR reviews their assigned high-intent accounts, identifies the best 3-5 contacts at each account (using Apollo or ZoomInfo to source contact details if not already in Salesforce), and adds them to a personalised outreach sequence that references the relevant intent topic. A defined workflow transforms intent data from a field in Salesforce to a prospecting engine.
“Our intent data shows companies that aren’t in our target market – too many false positives”
Third-party intent data, particularly Bombora’s broader publisher network signals, has meaningful noise – companies consuming content about your category are not always companies that would buy your product. Fix: filter intent data by your Ideal Customer Profile (ICP) criteria before it surfaces to sales. In Salesforce, create a combined filter: Bombora surge score + company employee count within your ICP range + industry within your target verticals + no existing customer account. Applying ICP filters reduces the false-positive rate from 60-70% to 15-25% for most B2B use cases. 6sense’s AI model applies ICP filtering as part of its buying stage model, which is one reason its intent signals are considered more actionable than raw Bombora signals for teams with defined ICPs.
Sources
Bombora, Company Surge Intent Data and Salesforce Integration Documentation (2026)
6sense, Account Intelligence Platform and CRM Integration (2026)
G2, Buyer Intent Data Integration with Salesforce and HubSpot (2025)
Forrester, B2B Intent Data Providers Wave Report (2025)
The integration should make the team faster to act, not just give them another dashboard. If the data is not showing up in a way that changes outreach decisions, the setup needs to be simplified.
Advanced Strategies and Common Pitfalls in CRM and Intent Data
Step-by-Step Fix: Build Your Foundation Before Scaling
Successful implementation of crm and intent data follows a consistent pattern: start with a clearly defined use case for a single team, measure the baseline, implement incrementally, and scale only after achieving measurable results in the pilot. Avoid configuring everything simultaneously. A phased approach with 30-day review cycles catches configuration errors before they spread.
Measuring Success: KPIs and Review Cadence
Establish three to five quantifiable success metrics before launch: adoption rate, data completeness score, and process efficiency measured as time saved per rep per week. Review these metrics monthly and tie configuration decisions to data rather than opinion.
What are the key benefits of CRM and Intent Data?
The primary benefits include improved operational efficiency, better data visibility for management decision-making, and more consistent customer-facing processes. Organisations that implement structured approaches report average productivity improvements of 20 to 35 percent, though results vary based on implementation quality and user adoption levels.
How long does implementation typically take?
Simple configurations for small teams can be live in two to four weeks. Mid-complexity implementations for 20 to 100 users typically take 60 to 90 days. Enterprise-scale projects with custom integrations and data migrations usually require four to nine months from kickoff to full production deployment.
What is the most common reason implementations fail?
Implementations fail most often due to insufficient user adoption rather than technical problems. Systems are configured correctly but teams revert to old habits because training was insufficient, workflows were not simplified, or leadership did not reinforce usage. Executive sponsorship and simplicity of design are the two highest-leverage success factors.
How do you calculate ROI from this type of investment?
Calculate ROI by comparing costs against measurable gains: hours saved per week multiplied by average hourly cost, pipeline increase attributable to improved process, and reduction in revenue lost to poor follow-up. Most organisations targeting a 12-month positive ROI need to demonstrate at least three dollars in measurable value for every one dollar of cost.
Common Problems and Fixes
Common Implementation Challenges to Anticipate
Organisations working on crm and intent data frequently encounter three recurring obstacles: inadequate stakeholder alignment during planning, underestimated data migration complexity, and insufficient end-user training budget. Addressing all three before go-live dramatically improves adoption rates and time-to-value. Build a project team with representatives from sales, marketing, and IT rather than delegating entirely to one function.