Required Datapoints
- Form Fills, Trial Signups, Demo Requests, etc.
- Source Attribution (Inbound Only)
- Timeframe of Analysis
Inbound Lead Volume measures the number of leads generated through inbound channels over a given time period. It helps quantify how effectively content, campaigns, and organic traffic attract prospects.
Inbound Lead Volume is a key indicator of top-of-funnel health, reflecting how many leads are generated through pull-based channels like SEO, content, social, and paid search.
The relevance and interpretation of this metric shift depending on the model or product:
A rising inbound volume reflects strong brand visibility and search/content performance, while a decline may signal channel fatigue or underinvestment.
By segmenting by channel, campaign, or intent signal, you can identify high-performing sources, scale winning strategies, and cut underperforming spend.
Inbound Lead Volume 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 |
|---|---|
| Lead Generation | Lead Generation is a strategic process focused on attracting, identifying, and engaging potential customers who express interest in a company’s product or service. It helps teams translate strategy into repeatable execution. Relevant KPIs include Conversion Rate and Inbound Lead Volume. |
| Content Strategy | Content Strategy focuses on strategically designing, organizing, and optimizing content assets to accelerate buyer journeys. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Content ROI and Direct Traffic Growth. |
| Referral Programs | Referral Programs is a strategic growth approach that encourages existing customers, partners, or users to recommend a company’s product or service to new prospects. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include Average Days from Referral to Close and Inbound Lead Volume. |
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(`InboundLeads`, { sql: `SELECT * FROM inbound_leads`,
measures: { formFills: { sql: `form_fills`, type: `sum`, title: `Form Fills`, description: `Total number of form fills from inbound channels.` }, trialSignups: { sql: `trial_signups`, type: `sum`, title: `Trial Signups`, description: `Total number of trial signups from inbound channels.` }, demoRequests: { sql: `demo_requests`, type: `sum`, title: `Demo Requests`, description: `Total number of demo requests from inbound channels.` }, inboundLeadVolume: { sql: `${formFills} + ${trialSignups} + ${demoRequests}`, type: `number`, title: `Inbound Lead Volume`, description: `Total number of leads generated through inbound channels.` } },
dimensions: { id: { sql: `id`, type: `string`, primaryKey: true, title: `ID`, description: `Unique identifier for each lead.` }, sourceAttribution: { sql: `source_attribution`, type: `string`, title: `Source Attribution`, description: `Attribution of the lead source, inbound only.` }, createdAt: { sql: `created_at`, type: `time`, title: `Created At`, description: `Timestamp when the lead was created.` } }});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