Reporting and Dashboards | Entry 78
HubSpot datasets create reusable, governed foundations for reporting, segmentation, and automation. They help teams share definitions, filters, calculations, joins, and approved sources while making it possible to analyze HubSpot information alongside supported external data.
Two staff members can answer the same fundraising question and return different results. One includes pledges while another counts only received gifts. One uses the payment date while another uses the deal close date. One removes refunds while another does not.
A governed dataset captures the approved sources and logic once, giving every report builder the same trusted starting point. That is how a nonprofit moves from having many polished reports to having reliable reporting.
HubSpot Data Studio can connect supported external sources, including spreadsheets and data warehouses, but this does not mean every source is universally available, requires no setup, consumes no HubSpot Credits, or can always be used without syncing information into the CRM.
Availability, beta status, connectors, refresh behavior, activation, synchronization, and credit consumption may vary by subscription and implementation.
A dataset is a prepared collection of information that can combine selected sources, columns, filters, formulas, joins, and summary logic. Once created, it can be reused instead of reconstructed for every report.
Development, finance, marketing, program, leadership, and board audiences may all report on the same information. A shared dataset can standardize:
A development team should not have to decide which object, pipeline, amount, date, status, and exclusion rules to use every time it creates a donation report. The dataset can establish those choices once.
Staff can then create monthly donations, fund revenue, major-gift, recurring-revenue, campaign, first-time donor, average-gift, and team-performance reports without changing the underlying definition of a donation.
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.
Not every important nonprofit data point lives in the CRM. HubSpot Data Studio is designed to consolidate HubSpot information with supported external sources for analysis and activation.
Confirm supported sources, connection methods, update behavior, subscription requirements, and HubSpot Credit implications during implementation.
In appropriate configurations, external information can be prepared and analyzed in a dataset without first modeling every external row as a standard or custom CRM record. This can reduce clutter when the information is needed only for analysis.
Using external data in a dataset does not necessarily create CRM records. Syncing or activating it may create or update records and introduce record, property, permission, privacy, and governance considerations. Preparing, joining, syncing, or exporting data may also consume HubSpot Credits.
| Dataset element | Possible configuration |
|---|---|
| Sources | External ticket sales, HubSpot memberships, campaigns, and event records |
| Shared keys | Event ID, campaign ID, ticketing campaign code, or carefully validated date and venue combinations |
| Measures | Anonymous tickets, ticket revenue, active and new memberships, membership revenue, and conversion period |
| Reports | Ticket sales by event, memberships by event, revenue comparisons, and post-event membership growth |
An event ID is generally safer than an event name because names can change or be entered inconsistently.
Anonymous purchases cannot be attributed to individual members unless a reliable identity or matching key exists. The dataset may compare event-level totals, but it should not claim that a particular anonymous buyer became a member without evidence connecting the identities.
| Connection type | Best for | Management considerations |
|---|---|---|
| Static data | Historical event files, year-end exports, one-time participation files, or archived membership data | A snapshot must be replaced or updated manually when newer information is required. |
| Dynamic data | Maintained spreadsheets, warehouses, connected financial systems, supported applications, or scheduled cloud files | Assign ownership for access, refresh schedules, schema stability, mapping, failures, credits, and source changes. |
A dynamic connection is only dependable when someone owns and monitors it.
Reusable formulas prevent one report from defining a major donor as someone who gives $5,000 annually while another silently uses $10,000 in lifetime giving.
Sources need a logical relationship and a reliable key, such as a contact, company, donation, membership, event, program, campaign, household, or external transaction ID. Stable system-generated IDs are generally safer than names or editable text.
If one donation joins to several campaign rows, or one contact joins to several membership records, totals can multiply unexpectedly.
| Tool | Best use |
|---|---|
| Custom property | Store a reportable value directly on a CRM record. |
| Custom object | Represent a distinct record type with its own properties and associations. |
| Dataset | Prepare reusable sources, calculations, filters, and joins for analysis or activation. |
| Report | Visualize and summarize the resulting information. |
| Workflow | Act on records that meet defined conditions. |
| Segment | Group records for targeting, analysis, or activation. |
A dataset should not replace a custom object when staff need individual records, histories, owners, associations, record-based processes, CRM page visibility, or ongoing operational management.
HubSpot documents datasets as scheduled workflow enrollment triggers. Records represented in a dataset can enter a workflow on a schedule, and dataset variables can be available to actions when enrollment occurs through that trigger.
Because enrollment is scheduled, do not describe it as an immediate real-time trigger without confirming the current configuration.
| Governance field | Purpose |
|---|---|
| Dataset name and definition | Makes the purpose and represented population clear. |
| Owner and approved users | Identifies who maintains and may edit the logic. |
| Sources and join keys | Documents inputs and how they connect. |
| Filters and formulas | Explains inclusion, exclusion, and calculation rules. |
| Refresh schedule | Shows how current the information is. |
| Dependent reports | Identifies what a change may affect. |
| Validation date | Shows when results were last reviewed. |
| Status | Marks the dataset as draft, approved, or retired. |
Clear name: APPROVED | Fundraising Revenue | Received Gifts | FY Reporting
Unclear name: Donations Final v3 New
If these questions cannot be answered, the dataset is not ready to become an organizational source of truth.
Dataset and Data Studio functionality continues to evolve, and some capabilities may be identified as beta. Confirm Data Hub subscription, feature status, permissions, supported external sources, connection direction, refresh behavior, Credit requirements, dataset and reporting limits, CRM record implications, and data privacy requirements.
Datasets can give fundraisers, finance staff, marketers, program teams, executives, and board members consistent answers without forcing every report builder to recreate the same logic. The value comes from governed definitions, appropriate source selection, stable joins, validated calculations, controlled editing, and ongoing ownership.