Buying an intent data platform is easy. Getting it to actually drive outreach and campaigns is where most teams get stuck.
The gap is almost always in the activation layer: the data flows, field mappings, automation rules, and workflow logic that convert raw intent signals into actions your teams can take. Without activation, intent data sits in a platform that your SDRs and marketers have to remember to log into, which means they stop using it after the first few weeks.
This guide covers the full activation architecture: how to connect intent data to your CRM and marketing automation platform, what fields to build, what automations to configure, and how to close the loop from signal to action to result.
Intent data activations fail for three predictable reasons.
Reason 1: The data lands in the wrong place. Intent signals get pushed to a single contact record rather than the account record, or they land in the marketing automation platform but not the CRM. Sales reps who live in the CRM never see the signals. Marketers who live in the MAP run campaigns without knowing which signals are driving them.
Reason 2: There is no defined action for each signal type. The intent data arrives and nobody has decided what to do with it. Individual reps interpret signals differently, resulting in inconsistent follow-up. Some high-value signals get ignored because no workflow routes them to the right person.
Reason 3: The signals are not prioritized. All intent signals are treated equally. A weak single-topic signal gets the same response as a strong multi-topic surge. Reps get alert fatigue and start ignoring all signals.
A well-designed activation architecture solves all three problems.
A complete intent data activation architecture has four components:
Build these four layers in order. Attempting to build the execution layer before the data and routing layers are stable is the primary cause of messy, unmaintainable intent integrations.
Before connecting any platforms, define the fields you need on each system and what maps to what.
Account fields in the CRM (required):
| Field Name | Data Type | Description |
|---|---|---|
| Intent Signal Strength | Picklist (None/Low/Medium/High) | Current signal strength from intent platform |
| Intent Signal Date | Date | Date of most recent intent signal |
| Intent Topics (Active) | Multi-line text or list | Which topics are currently surging |
| Intent Score (Raw) | Number | Numeric score from the intent platform |
| First Intent Signal Date | Date | Date the account first appeared in intent data |
| Intent Signal History (30-day) | Number | Count of intent events in the last 30 days |
Contact fields in the CRM (if contact-level data is available):
Some intent platforms provide contact-level signal data (indicating specific individuals engaging with relevant content). If your intent platform provides this, add fields on the contact record:
| Field Name | Data Type | Description |
|---|---|---|
| Contact Intent Engaged | Checkbox | Individual has been identified in intent data |
| Contact Intent Date | Date | Date of most recent individual intent signal |
Marketing automation equivalent fields:
Mirror the account-level intent fields in your MAP if contacts are managed there. The MAP needs visibility into intent signals to suppress or accelerate contacts in active programs.
Most intent platforms offer native integrations with Salesforce and HubSpot (and many also support Marketo). Configure the native integration to push signals to the CRM on a defined schedule.
Integration configuration checklist:
Intent platforms identify companies by IP address, domain, or company name. Your CRM identifies accounts by your internal ID. The matching logic between these two identification systems is where data quality problems typically originate.
Configure the matching rules carefully: - Primary match: domain name (most reliable) - Secondary match: company name fuzzy matching (watch for false matches between similarly named companies) - Fallback: IP-to-company matching (lowest confidence, use carefully)
Log all matching failures for manual review. A high volume of unmatched intent signals may indicate that your CRM account list is missing the companies generating signals, which is useful targeting information in itself.
For each signal strength category, define the exact action that should be triggered.
High-Confidence Signal Response:
Trigger: Account moves to Intent Signal Strength = High AND account is in the ABM target list.
Actions: 1. Create a high-priority task for the account owner in the CRM: “High intent signal detected - review and initiate outreach within 24 hours” 2. Send a Slack notification to the SDR or AE owner with the signal details (topics, score, date) 3. If the account is in Tier 3 and has high ICP fit, auto-promote to Tier 2 and trigger the Tier 2 ABM enrollment workflow 4. If there is no existing contact at the account in the CRM, create a research task to identify the right contacts before outreach
Medium-Confidence Signal Response:
Trigger: Account moves to Intent Signal Strength = Medium AND account is in the ABM target list.
Actions: 1. Add account to the daily digest report (no real-time alert, no task created) 2. If the account is in Tier 3, flag for the weekly ABM review meeting as a potential promotion candidate
Low-Confidence Signal Response:
Trigger: Account moves to Intent Signal Strength = Low AND account is in the ABM target list.
Actions: 1. Update the CRM field to log the signal. No immediate action. 2. Increment the Intent Signal History (30-day) counter. If it reaches a threshold (for example, 3 or more Low signals in 30 days), escalate to Medium response.
Signal Decay Response:
Trigger: Intent Signal Date is more than 14 days old AND Intent Signal Strength is High or Medium.
Actions: 1. Downgrade Intent Signal Strength by one level (High to Medium, Medium to Low) 2. If the account was promoted to Tier 2 based on the intent signal and has no active sales engagement, flag for tier review
In Salesforce, these responses are built as Process Builder flows or Flows (the more current tooling). In HubSpot, they are built as Workflows.
For each trigger condition, build a separate workflow. Avoid building a single monolithic workflow that handles all signal types. Separate workflows are easier to debug, modify, and disable independently when something goes wrong.
Test each workflow with a sample account before enabling for the full database. Common issues to test for: - Duplicate task creation (the workflow fires multiple times for the same event) - Tasks creating for inactive users (accounts owned by departed employees) - Tier promotions triggering for accounts that are already in active ABM sequences
Intent signals should trigger MAP program enrollments. The specific programs depend on your intent platform’s topic coverage and your ABM program structure.
Example enrollment logic:
Account shows High-confidence signal on topics related to your category AND account is Tier 2 AND account has at least one known contact in the MAP.
Enrollment action: Add the known contacts to the Tier 2 Consideration-Stage Email Program. This is a 5 to 7 email sequence with mid-funnel content (comparison guides, customer case studies, product capability content).
Before enrollment, check the suppression conditions: - Is any contact at this account already enrolled in an active program? Do not double-enroll. - Is the account in Tier 1 or in an active sales sequence? If yes, suppress from the MAP program (the SDR or AE is handling direct outreach). - Is any contact at this account in an unsubscribe or opt-out list? Suppress those contacts.
For accounts showing intent signals, activate a corresponding LinkedIn ad campaign targeting the company’s contacts with relevant content.
Build intent-triggered LinkedIn audiences in two ways:
Manual list update: Export the list of accounts that crossed the High-confidence signal threshold in the past week and upload to LinkedIn Matched Audiences. Update the list weekly.
Automated audience sync: Some intent platforms and ABM platforms support automated sync to LinkedIn Matched Audiences. If this is available, configure it. Automated sync ensures LinkedIn campaigns stay current without manual list management overhead.
Configure the LinkedIn campaigns to serve consideration-stage content (not awareness-stage, because these accounts are already showing active research behavior) with a frequency cap of 3 to 5 impressions per account per week.
High-signal accounts should generate immediate, actionable tasks in the CRM for the account owner. A task with no context is useless. Each task should include:
The activation architecture is only validated when you can trace intent signals to business outcomes. Build reporting that connects the signal to the action to the result.
Report 1: Signal volume and distribution. How many High, Medium, and Low signals are arriving per week? What is the trend over time? A sudden drop in signal volume may indicate an integration failure. A sudden spike may indicate unusual market activity or a data quality issue.
Report 2: Signal-to-action conversion rate. For every High-confidence signal, did a task get created and completed? What percentage of High signals resulted in actual outreach within 24 hours? If this is below 50%, reps are not acting on signals and you need to understand why.
Report 3: Signal-to-opportunity rate. For accounts that received a High-confidence signal and subsequent outreach, what percentage developed into CRM opportunities within 60 days? Track this over time. It is the core metric that tells you whether intent data is actually useful for your program.
Report 4: Intent signal coverage of closed deals. For deals that closed in the last quarter, did they show intent signals before the sales conversation began? What percentage of closed-won accounts showed High or Medium signals in the 60 days before the first outreach? This is the retrospective validation that intent data is correlated with deal quality.
Run a weekly integration health check:
Double-syncing: The intent platform pushes the same signal twice, creating duplicate tasks or enrollments. Fix by adding deduplication logic to workflows: check whether a task already exists for this signal type before creating a new one.
Signal decay not working: Accounts stay at High signal strength permanently even when no new signals arrive. Fix by ensuring the decay workflow has the correct trigger condition (signal date comparison) and runs on a daily schedule.
Intent data not reaching the MAP: Account intent fields in the CRM are updating correctly, but MAP contacts are not seeing the data and MAP programs are not triggering. Fix by ensuring the CRM-to-MAP sync is active for the relevant account fields and that MAP is receiving field updates in real time, not on a 24-hour batch sync.
A marketing qualified account (MQA) is a target account that meets ideal customer profile criteria (firmographic fit, company size, industry) and demonstrates behavioral intent signals (increased website visits, content engagement, or...
Account-based advertising is fundamentally different from traditional lead-gen advertising. Instead of targeting by interest, role, or demographic, account-based advertising targets by company account name.