Reporting and Dashboards | Entry 79
HubSpot reporting calculations transform raw CRM data into averages, percentages, differences, ratios, rates, and other decision-ready insights. When a calculation is needed for only one report, a report formula can provide the answer without adding another permanent CRM property or shared dataset formula.
Knowing that a nonprofit received 500 donations is useful. Knowing the average donation amount, donor retention rate, year-over-year growth, and average time from first engagement to first donation creates a much clearer view of performance.
The right calculation turns stored fundraising, membership, volunteer, event, program, and engagement data into a metric leaders can interpret and act on.
This entry focuses on calculations used inside HubSpot reports, including report-specific formula fields, aggregations, percentages, averages, differences, and rates. It distinguishes those calculations from reusable dataset formulas and permanent CRM calculation or rollup properties.
A formula alone does not make a metric reliable. Donor retention and similar measures require clearly defined populations, periods, statuses, and exclusions before the math is applied.
Reporting calculations use CRM, transaction, activity, or engagement data to produce a value inside a report. HubSpot formula fields can perform row-level math using fields included in the custom report builder.
| Nonprofit metric | Basic calculation |
|---|---|
| Average donation | Total donation amount / qualifying donations |
| Donor retention rate | Returning donors / eligible prior-period donors |
| Donor acquisition rate | New donors / total donors |
| Donation conversion rate | Donors / qualifying audience |
| Membership renewal rate | Renewed memberships / memberships eligible for renewal |
| Event attendance rate | Attendees / confirmed registrants |
| Volunteer return rate | Returning volunteers / eligible prior volunteers |
| Campaign goal attainment | Revenue received / campaign goal |
| Net donation revenue | Gross donations - refunds - qualifying fees |
| Year-over-year growth | Change from prior period / prior-period value |
| Grant success rate | Grants awarded / completed grant applications |
| Program completion rate | Participants completing / enrolled participants |
| Cost per participant | Program cost / qualifying participants |
| Average gift frequency | Number of gifts / qualifying donors |
The formula is only one part of the metric. The nonprofit must also define the population, dates, statuses, and exclusions.
A row-level formula calculates a value for each underlying report row. Examples include donation amount minus processing fee, revenue minus refund, days from first engagement to first donation, an allocation amount, or whether one gift qualifies as a major donation.
Aggregate math summarizes multiple records, such as total donation revenue, average gift amount, distinct donor count, maximum donation, or average time to donate.
A report might first calculate time to donation for each constituent, then average those individual row results across the qualifying population.
Documentation should explain what is included and excluded, how sources connect, which date controls the period, which formulas apply, how often sources update, who approved the logic, who maintains it, and which reports depend on it.
A fundraising leader asks: what was our average completed donation amount this quarter?
Total completed donation revenue / number of completed donations
HubSpot may answer this with the standard Average aggregation on the donation amount field. A custom formula is not always necessary.
Average gift amount divides revenue by gifts. Average donor value divides revenue by distinct donors. One donor making five gifts affects these metrics differently.
A report-specific row-level formula can calculate donation revenue after refunds and processing fees:
Donation amount - refund amount - processing fee
The report can then sum the calculated value. Missing-value rules must be intentional. Treating a blank refund as zero may be appropriate, while treating an unknown donation amount as zero could hide a data-quality problem.
Converting a blank to zero in a formula affects only that report. It does not update the original CRM property.
For each converted constituent, calculate:
The report can then average those individual results. Before building it, define which engagement starts the clock, what qualifies as a donation, whether only first-time donors count, how non-donors are handled, whether invalid negative intervals are removed, and whether the result is shown in days, weeks, or months.
A formula cannot correct unreliable milestone dates. The source fields must be structured and maintained consistently.
An annual definition might treat the denominator as distinct donors who made at least one qualifying gift during the prior fiscal year. The numerator would be members of that same population who also made a qualifying gift during the current fiscal year.
Retention compares distinct populations across periods, so it may require a dataset, supporting properties, or cohort logic rather than one report formula. The math is simple; defining the population is the real work.
Examples include net revenue for one event, a temporary campaign projection, event profitability, a report-specific allocation, a temporary gift classification, a one-time comparison, or donation value after fees.
Report formula fields are not reusable across separate reports unless the report is cloned. Dataset formulas are the better home for shared analytical logic.
Use a CRM property when the result should exist directly on a contact, company, donation, membership, or other record and needs to appear in saved views, trigger workflows, support segmentation, power personalization, or guide individual staff action.
Calculation properties use values from the same object. Rollup properties can summarize counts, sums, averages, minimums, maximums, and dates from associated records.
| Reporting need | Recommended option |
|---|---|
| Basic count, sum, or average in one report | Standard report aggregation |
| Row-level calculation needed in one report | Report formula field |
| Reusable logic across several reports | Dataset formula |
| Value displayed on a CRM record | Calculation property |
| Calculation across associated records | Rollup property |
| Value used for automation or personalization | CRM property or activated dataset logic |
| Governed logic using multiple data sources | Dataset |
| Comparison with a prior period | Report comparison or purpose-built analysis |
Use the simplest option that produces an accurate, maintainable result.
Does the event audience mean everyone invited, everyone registered, everyone who attended, confirmed attendees, or everyone who received the follow-up appeal? Each denominator produces a different rate.
Confirm that the periods are equal in length, use the same definitions and date property, include the same revenue categories, identify partial periods, and apply consistent refund and adjustment rules.
When the prior-period value is zero, conventional percentage growth does not produce a meaningful result. Handle that condition explicitly.
| Error | Why it matters |
|---|---|
| Counting gifts instead of donors | Ten donations may come from fewer than ten people. Use distinct donor identifiers. |
| Mixing pledges with received revenue | Committed and received revenue answer different questions. |
| Using the wrong date | Creation, donation, close, payment, and deposit dates are not interchangeable. |
| Using an incomplete denominator | A conversion rate fails when the eligible population is incomplete. |
| Treating every blank as zero | Blank may mean zero, unknown, not applicable, or missing. |
| Averaging averages | Group averages can mislead when group sizes differ. |
| Rebuilding the same formula | Shared logic belongs in a dataset or CRM property. |
| Hiding the definition | Leadership should be able to explain every important metric. |
HubSpot formula fields perform row-level calculations and are available with eligible Professional and Enterprise subscriptions. Limits vary by subscription, formulas are not reusable across separate reports unless cloned, and additional Functions tools currently require dataset access through Data Hub Enterprise.
Formulas may require internal property values instead of visible labels, can apply report-specific missing-value rules, and do not update their source CRM properties. Calculation and rollup properties have separate limits and behaviors. Confirm current requirements before finalizing the reporting architecture.
Reporting calculations help teams move beyond raw counts to understand retention, conversion, growth, timing, efficiency, margins, and progress. The most dependable results come from clear definitions, intentional calculation placement, valid source data, documented handling rules, and tested outcomes.