Required Datapoints
- 3rd-party intent platform integration
- Tracked keywords, topics, or competitors
- Number of signals matched to ICP accounts
Intent Signal Volume (3rd-party) measures the number of buying intent signals collected from external sources (e.g., Bombora, G2, media partners) over a defined time period. It helps quantify market interest beyond owned channels.
Intent Signal Volume (3rd-party) is a key indicator of early market demand and buyer intent visibility, reflecting how many in-market accounts are actively researching relevant topics, product categories, or competitors outside of your owned channels.
The relevance and interpretation of this metric shift depending on the model or signal source:
A rising intent volume typically signals increased market readiness, stronger category awareness, or competitive activity, while a decline may reflect channel fatigue, seasonality, or messaging gaps.
By segmenting by keyword cluster, ICP tier, industry, or signal strength, you unlock insights to refine content strategies, prioritize account outreach, and align campaigns with real-time interest.
Intent Signal Volume (3rd-party) informs:
These are the main factors that directly impact the metric. Understanding these lets you know what levers you can pull to improve the outcome
Actionable ideas to optimize this KPI, from fast, low-effort wins to strategic initiatives that drive measurable impact.
Activities commonly tied to improving or operationalizing this KPI.
| Activity | Description |
|---|---|
| Campaign Targeting | Campaign Targeting focuses on identifying, segmenting, and prioritizing key customer groups or market segments for targeted go-to-market initiatives. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Bounce Rate and Intent Signal Volume (3rd-party). |
| Account Prioritization | Account Prioritization focuses on Account Prioritization ranks accounts based on value, fit, intent, and growth potential. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Expansion Readiness Index and Expansion Revenue Potential (Forecasted). |
| Outbound Strategy | Outbound Strategy focuses on the strategic design and execution of targeted outreach to identify, engage, and convert potential customers. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Intent Signal Volume (3rd-party). |
| Intent Monitoring Tools | Intent Monitoring Tools focuses on continuously tracking and analyzing behavioral data from potential customers to identify buying signals and engagement patterns. It turns signals into decisions, interventions, and measurable follow-up. Relevant KPIs include Intent Signal Volume (3rd-party). |
This KPI is associated with the following stages in the AAARRR (Pirate Metrics) funnel:
This KPI is classified as a lagging Indicator. It reflects the results of past actions or behaviors and is used to validate performance or assess the impact of previous strategies.
This role is directly accountable for the KPI and is expected to drive progress and decisions around it.
These roles contribute directly to performance and typically partner on execution, reporting, or optimization.
These leading indicators influence this KPI and act as early signals that forecast future changes in this KPI.
These lagging indicators confirm, quantify, or amplify this KPI and help explain the broader business impact on this KPI after the fact.
How this KPI is structured in Cube.js, including its key measures, dimensions, and calculation logic for consistent reporting.
cube('IntentSignals', { sql: `SELECT * FROM intent_signals`,
joins: { ThirdPartyPlatforms: { relationship: 'belongsTo', sql: `${CUBE}.platform_id = ${ThirdPartyPlatforms}.id` } },
measures: { intentSignalCount: { type: 'count', sql: 'id', title: 'Intent Signal Count', description: 'Counts the number of intent signals collected from third-party platforms.' }, matchedSignalsToICP: { type: 'count', sql: 'matched_to_icp', title: 'Matched Signals to ICP', description: 'Counts the number of signals matched to Ideal Customer Profile (ICP) accounts.' } },
dimensions: { id: { sql: 'id', type: 'string', primaryKey: true }, platformName: { sql: `${ThirdPartyPlatforms}.name`, type: 'string', title: 'Platform Name', description: 'Name of the third-party platform providing intent signals.' }, trackedKeyword: { sql: 'tracked_keyword', type: 'string', title: 'Tracked Keyword', description: 'Keywords or topics tracked for intent signals.' }, eventTime: { sql: 'event_time', type: 'time', title: 'Event Time', description: 'Time when the intent signal was recorded.' } }});cube('ThirdPartyPlatforms', { sql: `SELECT * FROM third_party_platforms`,
measures: { platformCount: { type: 'count', sql: 'id', title: 'Platform Count', description: 'Counts the number of third-party platforms integrated.' } },
dimensions: { id: { sql: 'id', type: 'string', primaryKey: true }, name: { sql: 'name', type: 'string', title: 'Platform Name', description: 'Name of the third-party platform.' } }});Note: This is a reference implementation and should be used as a starting point. You’ll need to adapt it to match your own data model and schema