Required Datapoints
- Total Trial Sign-Ups (by day/week/month)
- Time Period for Analysis
- Optional: Channel attribution or campaign cohorting
Trial Sign-Up Velocity measures the rate at which new users are initiating free trials over a specific period. It helps track momentum and trendlines in trial acquisition.
Trial Sign-Up Velocity is a key indicator of growth momentum and demand generation consistency, reflecting how quickly and regularly trial sign-ups are occurring over time.
The relevance and interpretation of this metric shift depending on the model or product:
A rising velocity means your messaging and offers are landing, while a flat or declining trend may signal channel fatigue or missed expectations.
By segmenting by campaign, persona, or region, you identify what’s driving spikes or stalls.
Trial Sign-Up Velocity 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 Launches | Campaign Launches focuses on the strategic planning, execution, and monitoring of coordinated campaigns spanning marketing, sales, and product initiatives to increase customer awareness, acquisition, and engagement. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include Trial Sign-Up Velocity. |
| Trial Funnel Strategy | Trial Funnel Strategy focuses on Designing, implementing, and continuously refining the end-to-end process for guiding prospective customers through a product’s trial experience is at the core of this activity. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Trial Sign-Up Velocity. |
| Top-of-Funnel Forecasting | Top-of-Funnel Forecasting involves estimating the volume, quality, and conversion potential of early-stage leads or prospects as they begin their engagement journey. It turns signals into decisions, interventions, and measurable follow-up. Relevant KPIs include Trial Sign-Up Velocity. |
| Signup Speed Optimization | Signup Speed Optimization focuses on Streamlining and optimizing the user sign-up process reduces friction, shortens time-to-value, and enhances the initial experience for new users. It improves performance by removing friction, testing changes, and scaling what works. Relevant KPIs include Trial Sign-Up Velocity. |
Week 1: 2,100 trials
Week 2: 2,520 trials
Formula: (2,520 − 2,100) ÷ 2,100 = 20% Weekly Velocity Growth
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(`TrialSignUpVelocity`, { sql: `SELECT * FROM trial_sign_ups`,
measures: { totalTrialSignUps: { sql: `id`, type: 'count', title: 'Total Trial Sign-Ups', description: 'Total number of trial sign-ups over a specific period.' } },
dimensions: { id: { sql: `id`, type: 'number', primaryKey: true }, signUpDate: { sql: `sign_up_date`, type: 'time', title: 'Sign-Up Date', description: 'The date when the trial sign-up occurred.' }, channel: { sql: `channel`, type: 'string', title: 'Channel', description: 'The channel through which the trial sign-up was acquired.' }, campaign: { sql: `campaign`, type: 'string', title: 'Campaign', description: 'The campaign associated with the trial sign-up.' } },
preAggregations: { main: { type: 'rollup', measureReferences: [totalTrialSignUps], dimensionReferences: [signUpDate, channel, campaign], timeDimensionReference: signUpDate, granularity: 'day' } }});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