Ramps
To view the metrics listed below in your Chargebee site, go to RevenueStory from the left navigation pane, select Reports Explorer, and then search for the required report or metric.
These metrics count Subscription Ramps that are upcoming, created, or fulfilled.
Subscriptions with Upcoming Ramps This Month
The number of distinct subscriptions that have at least one ramp scheduled to take effect in the current month, as of today.
Explanation of metric
This metric shows how many subscriptions are about to go through a planned price, quantity, or plan change. A subscription with several upcoming ramps is counted once. It is a point-in-time snapshot, so it changes daily as ramps are applied, canceled, or newly added.
How it's measured
Subscriptions with Upcoming Ramps This Month = COUNT(DISTINCT Subscription ID) where Ramp Status = Scheduled and Ramp Effective Date is after Report As-of Time (today) and on or before the end of the current month
Draft, failed, and deleted ramps are excluded, as are ramps on deleted subscriptions. A ramp whose effective date equals the report as-of time is excluded. Total Upcoming Ramps uses that same lower bound. The value is always less than or equal to Total Upcoming Ramps.
Reading
An upward trend means more subscriptions are lined up for planned changes, which usually means higher near-term billing activity. A sharp drop without a matching rise in fulfilled ramps may point to ramps being moved to draft or deleted.
Interpretation
Use this metric to size the number of accounts that need attention in the coming weeks, such as billing operations checks before a ramp applies or customer success outreach ahead of a price increase.
Example
For a given day:
- Subscription A: 2 upcoming ramps
- Subscription B: 1 upcoming ramp
- Subscription C: 3 upcoming ramps
- Subscription D: 0 upcoming ramps
- Subscriptions with Upcoming Ramps This Month = 3
Three subscriptions (A, B, and C) have upcoming ramps, even though they hold 6 upcoming ramps between them.
Total Upcoming Ramps
The number of ramps that are scheduled to take effect in the future and have not yet been applied, as of today.
Explanation of metric
This metric counts every pending ramp, not only the subscriptions that hold them. It shows the total volume of planned changes in the pipeline. It is a point-in-time snapshot, so it falls when ramps are applied or canceled and rises when new ramps are created.
How it's measured
Total Upcoming Ramps = COUNT(Ramp ID) where Ramp Status = Scheduled and Ramp Effective Date > Report As-of Time (today)
The lower bound matches Subscriptions with Upcoming Ramps This Month: a ramp whose effective date equals the report as-of time is excluded. Draft, failed, and deleted ramps are excluded, as are ramps on deleted subscriptions. A subscription can hold several ramps, so this value can exceed Subscriptions with Upcoming Ramps This Month.
Reading
An upward trend means more ramps entered the Scheduled status than left it. New ramps add to the count. Draft ramps that are rescheduled to a future date also add to it. Ramps that are applied, canceled, or moved back to draft reduce it.
Interpretation
Use this metric to understand the workload and revenue changes coming up. Compare Total Upcoming Ramps at two snapshot times to see whether the backlog grew.
Example
For a given day:
- Total Upcoming Ramps = 6 (across subscriptions A, B, and C)
There are 6 ramps waiting to be applied, spread over 3 subscriptions.
Ramps Fulfilled This Month
The number of ramps whose scheduled change was applied to the subscription during the current calendar month.
Explanation of metric
This metric shows how many planned changes have taken effect so far this month. A ramp counts as fulfilled once its change is applied to the subscription, and it is counted in the month it was applied, not the month it was created. It is a month-to-date figure that resets on the first day of the month.
How it's measured
Ramps Fulfilled This Month = COUNT(Ramp ID) where Ramp Status = Succeeded and Fulfilled Date is between the first day of the current month and today
Ramps applied in earlier months are excluded, even if they were created this month. A ramp whose effective date has passed but whose status is failed is not counted. The value is always less than or equal to Total Ramps Fulfilled.
Reading
An upward trend across months means a growing volume of planned changes reaching customers. A month well below the number of ramps that were scheduled for it may point to ramps that failed or were moved to draft.
Interpretation
Use this metric to measure how many scheduled ramps were applied during the month. A ramp counts once whether it was applied on its effective date or later in the same month. To check whether a ramp was applied on time, compare its effective date with its fulfilled date. The count also gives finance a view of expansion or step-up revenue that has just taken effect.
Example
For a given month:
- Ramps applied on day 1: 4
- Ramps applied on day 5: 3
- Ramps applied on day 12: 5
- Ramps applied in the previous month: 9 (not counted)
- Ramps Fulfilled This Month = 4 + 3 + 5 = 12
Twelve ramps were applied in the current month so far. The 9 applied in the previous month are excluded.
Total Ramps Fulfilled
The cumulative number of ramps that have been applied to a subscription, across all time.
Explanation of metric
This metric is the running total of all ramps that have taken effect since ramps were first used. It shows how much of the planned change activity has actually been delivered. It only increases over time, unless ramp records are deleted.
How it's measured
Total Ramps Fulfilled = COUNT(Ramp ID) where Ramp Status = Succeeded
No date filter is applied. Failed ramps are not counted even if their effective date has passed, and ramps on deleted subscriptions are excluded. The value includes Ramps Fulfilled This Month.
Reading
An upward trend is expected and means continued use of ramps. A flat line over several weeks while Total Upcoming Ramps is not zero may mean ramps are not being applied or are failing.
Interpretation
Use this metric as the lifetime delivery count. Divide Total Ramps Fulfilled by Total Ramps Created to get the fulfillment rate. Total Ramps Created excludes deleted ramps, so the rate is the share of non-deleted ramps that have been applied. If Total Ramps Created is zero, the rate is undefined. The ramps that are not fulfilled are upcoming, failed, or draft.
Example
For a given date, deleted ramps are already excluded:
- Total Ramps Created: 200 non-deleted ramps
- Total Ramps Fulfilled: 140
- Fulfillment rate = 140 / 200 = 70%
Seventy percent of the non-deleted ramps have been applied to their subscriptions.
Ramps Created This Month
The number of new ramps set up during the current calendar month, whatever their status today.
Explanation of metric
This metric shows how many new ramps were added so far this month. It reflects the rate at which subscriptions are put on planned price, quantity, or plan changes. A ramp is counted in the month it was created, even if it is applied later, fails, is moved to draft, or is already fulfilled. It is a month-to-date figure that resets on the first day of the month.
How it's measured
Ramps Created This Month = COUNT(Ramp ID) where Ramp Created Date is between the first day of the current month and today and the ramp is not deleted
Deleted ramps are excluded. No other status filter is applied, so scheduled, succeeded, failed, and draft ramps are included. The value is always less than or equal to Total Ramps Created.
Reading
An upward trend means more ramps are being sold or configured, which feeds the upcoming ramp pipeline for later months. A drop may reflect fewer multi-phase deals closing.
Interpretation
Use this metric to track adoption of ramps and sales activity. Do not infer backlog growth by comparing it with Ramps Fulfilled This Month. Created ramps include drafts, and Total Upcoming Ramps does not. Compare Total Upcoming Ramps at two snapshot times to see whether the backlog grew.
Example
For a given month:
- Ramps created on day 2: 6
- Ramps created on day 9: 4
- Ramps created on day 12: 5
- Ramps created in the previous month: 11 (not counted)
- Ramps Created This Month = 6 + 4 + 5 = 15
Fifteen ramps were created in the current month so far, whether or not they have been applied yet.
Total Ramps Created
The cumulative number of ramps ever created, across all time and all statuses, excluding deleted ramps.
Explanation of metric
This metric is the lifetime count of ramp records. Every upcoming, fulfilled, failed, or draft ramp was created at some point, so the other ramp counts roll up to this total.
How it's measured
Total Ramps Created = COUNT(Ramp ID) where the ramp is not deleted
No status or date filter is applied, but deleted ramps are excluded. Upcoming, fulfilled, failed, and draft ramps are included. Deleting a counted ramp lowers the total.
Reading
An upward trend means continued use of ramps over time. Deleting a ramp lowers the total, so the metric can fall as well as rise. Read it alongside the monthly figures to see whether adoption is speeding up or slowing down.
Interpretation
Use this metric as a reconciliation check. Total Upcoming Ramps + Total Ramps Fulfilled + failed ramps + draft ramps equals Total Ramps Created only when every non-deleted ramp falls into one of those groups. A scheduled ramp whose effective date is not after the report as-of time stays in Total Ramps Created and is excluded from Total Upcoming Ramps by the date filter. That gap is not an unrecognized status.
Example
For a given date:
- Total Upcoming Ramps: 40
- Total Ramps Fulfilled: 140
- Failed or draft ramps: 20
- Total Ramps Created = 40 + 140 + 20 = 200
The 200 ramps created to date split into 40 upcoming, 140 fulfilled, and 20 failed or draft.