Required Datapoints
- New Users with Referral Attribution
- Referral Source or Campaign
- Time Window
New Users from Referrals measures the number of users who joined the platform via referral from an existing user or partner. It helps quantify the impact of referral and network-based growth strategies.
New Users from Referrals is a key indicator of organic growth momentum and user trust, measuring how many users join via invite links, affiliate codes, or sharing flows.
Its application varies by motion:
A rising referral rate reflects strong product satisfaction, community engagement, or incentive design, while a stall may suggest unclear value exchange or UX friction.
By segmenting by referrer, plan, or usage behavior, you can refine incentive programs, sharing flows, and messaging, while surfacing top advocates.
New Users from Referrals informs:
Strategic decisions, like scaling virality loops and brand trust levers
Tactical actions, such as optimizing sharing CTAs or redesigning referral prompts
Operational improvements, including referral tracking, fraud detection, or incentive fulfillment
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 |
|---|---|
| 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. |
| Invite Flow Design | Invite Flow Design focuses on designing, refining, and managing the complete workflow for inviting users to join a product, platform, or service. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include New Users from Referrals. |
| Advocacy Campaigns | Advocacy Campaigns focuses on Coordinated efforts to shape public perception, influence stakeholder opinions, and impact industry standards play a crucial role in creating favorable conditions for product adoption and business growth. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include New Users from Referrals and Personalized Referral Outreach Rate. |
| Referral Attribution | Referral Attribution involves systematically identifying, recording, and analyzing where leads or customers originate when they enter a sales or product funnel through referrals. It turns signals into decisions, interventions, and measurable follow-up. Relevant KPIs include New Users from Referrals. |
820 referred users in Q2
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(`NewUsers`, { sql: `SELECT * FROM new_users`, measures: { newUsersFromReferrals: { sql: `id`, type: 'count', title: 'New Users from Referrals', description: 'Counts the number of new users who joined via referral.' } }, dimensions: { id: { sql: `id`, type: 'number', primaryKey: true }, referralSource: { sql: `referral_source`, type: 'string', title: 'Referral Source', description: 'The source or campaign from which the user was referred.' }, createdAt: { sql: `created_at`, type: 'time', title: 'User Creation Time', description: 'The time when the user account 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