| Purpose | Understand why some Cloudbeds Insights metrics are averaged instead of totaled, and which metrics allow you to change their aggregation. |
| Best for | Anyone building or reviewing a custom report in Cloudbeds Insights. |
| Use this when | A metric such as ADR, RevPAR, Occupancy, Booking Window, or Length of Stay shows an average instead of a sum, or you want to know whether its aggregation can be changed. |
| Requirements | A custom Cloudbeds Insights report that includes a metric summarized across multiple rows or groups. |
| Expected result | You can identify why a metric is averaged, whether its aggregation can be changed, and how to interpret the summary value correctly. |
| Limitations | Dynamic fields such as ADR, RevPAR, and Occupancy are recalculated for the report grouping and cannot have their aggregation changed. Other stored metrics may start as an average but allow a different aggregation. |
Introduction
Most metrics in Cloudbeds Insights total the way you would expect. Revenue, taxes, rooms sold, and other amounts or counts can be added together to produce a meaningful total.
Some metrics work differently. Rates, percentages, and durations often use an average because adding their row values together would not produce a meaningful result.
There are two important groups to understand. Some metrics are Dynamic fields that are always recalculated and cannot use a different aggregation. Others are stored values that start as an average but can be changed when another aggregation better supports your analysis.
This article explains why averages are used, which metrics are always averaged, and which ones allow you to change the aggregation.
Table of contents
- Why some metrics use an average instead of a total
- Metrics that are always averaged
- Metrics that start as an average but can be changed
- Metrics that total normally
Why some metrics use an average instead of a total
Adding rates or percentages together can produce a number that does not represent the performance of the full period.
For example, three nights with ADR values of 100, 120, and 80 do not produce an ADR of 300. The ADR for those three nights is 100.
| Stay Date | Rooms Sold | ADR |
|---|---|---|
| 1 Aug | 1 | 100 |
| 2 Aug | 1 | 120 |
| 3 Aug | 1 | 80 |
| Total | 3 | 100 |
The summary ADR is calculated for the full period instead of adding the daily ADR values together. Rooms Sold, which is a count, totals normally alongside it.
An averaged summary does not mean the report is missing data. For metrics such as ADR and Occupancy, Cloudbeds Insights recalculates the value for the complete period or grouping instead of adding the row values together.
Metrics that are always averaged
Dynamic fields are not stored as standalone values. Cloudbeds Insights calculates them from other fields each time the report runs.
Because the metric must be recalculated for the period or grouping being viewed, its aggregation cannot be changed.
| Metric | What it represents | What the summary row shows |
|---|---|---|
| ADR / Booked ADR / Blocked ADR | Room revenue divided by rooms sold. | The rate for the full period, recalculated from the underlying values rather than the daily rates added together. |
| RevPAR | Room revenue divided by rooms available. | The rate for the full period, recalculated for the complete grouping. |
| Average Bed Rate | Room revenue divided by guest count. | The rate for the full period, recalculated for the complete grouping. |
| Occupancy / Adjusted Occupancy / Bed Occupancy / Adjusted Bed Occupancy | A percentage based on rooms or beds sold compared with what was available. | The percentage for the full period. The daily percentages are not added together. |
These nine Dynamic metrics are always recalculated: ADR, RevPAR, Occupancy, Adjusted Occupancy, Bed Occupancy, Adjusted Bed Occupancy, Average Bed Rate, Booked ADR, and Blocked ADR.
Metrics that start as an average but can be changed
Other metrics are stored values rather than Dynamic calculations. They start with an average because an average is usually the most useful summary, but Cloudbeds Insights can offer other aggregations for these fields.
| Metric | What it represents | Default summary behavior |
|---|---|---|
| Booking Window / Reservation Length of Stay / Room Length of Stay | A count of days. | The average number of days. Reservation Length of Stay can also repeat across every night of a booking, so totaling the repeated values can count the same stay more than once. |
| Commission Percent / Conversion Rate | A stored percentage or rate. | The average. These values are rates rather than amounts, so adding them together usually does not provide a useful summary. |
If you need the highest or lowest value in a period, or another available aggregation, you can change how these stored metrics are summarized. The summary row updates to reflect the selected aggregation.
Use Sum carefully for rates, percentages, and durations. Cloudbeds Insights may allow Sum for some stored metrics, but the resulting number is not always meaningful for the analysis. Choose the aggregation that matches the question you are trying to answer.
Metrics that total normally
Amounts and counts such as revenue, taxes, fees, payments, payouts, guest counts, rooms sold, and room nights can be added together and therefore total normally in Cloudbeds Insights.
The key distinction is whether the field represents an amount or count that can be summed directly, a stored value that can use different summary methods, or a Dynamic metric that must be recalculated for each report grouping.
Related articles
Now that you understand why different metrics use different aggregation behavior, review this foundational guide for more information about how Cloudbeds Insights fields behave at different levels of detail:
Comments
Please sign in to leave a comment.