Reporting and Dashboards | Entry 76
HubSpot cross-object reporting combines related records so nonprofits can analyze relationships among people, donations, memberships, events, volunteers, companies, programs, and sponsorships. The custom report builder can bring a primary source and related secondary sources into one report without repeatedly merging spreadsheet exports.
Nonprofits rarely ask questions about only one object. Constituent relationships cross fundraising, memberships, volunteering, events, programs, organizations, and communications.
Cross-object reporting brings these connected records into one analysis and lets the nonprofit see more of the constituent story.
This is not a general overview of dashboards, attribution, funnels, or nonprofit data architecture. Those concepts matter only when they explain why a cross-object report succeeds or fails.
The primary source establishes the report's focus. Related secondary sources contribute additional information, and the choice of primary source can materially change which records appear.
One person may be a donor, recurring donor, member, volunteer, attendee, employee of a sponsor, board member, subscriber, and program participant. A single-object report can show only one portion of that relationship.
Cross-object reports connect engagement, fundraising, programs, events, memberships, and organizational relationships so teams can understand how those activities influence one another.
| Nonprofit question | Potential HubSpot data sources |
|---|---|
| Which event attendees later became donors? | Contacts, event registrations, and donations or deals |
| Which current members have not renewed? | Contacts, memberships, and payments or deals |
| Are volunteers also making donations? | Contacts, volunteer records, and donations |
| Which sponsors have employees who volunteer? | Companies, contacts, sponsorship deals, and volunteer records |
| Which donors belong to the same household? | Contacts, household records, and donations |
| Which gala attendees became recurring donors? | Contacts, registrations, subscriptions, or recurring gifts |
| Which funders support multiple programs? | Companies, grants, programs, and deals |
| Which campaigns generated members and donors? | Campaigns, contacts, memberships, and donations |
| Which board members secured sponsorships? | Contacts, companies, deals, and association labels |
HubSpot needs to know that a gift belongs to a donor, a membership belongs to a person or household, an employee belongs to a sponsoring company, an event registration belongs to a contact, a grant connects to a funder and program, and a volunteer shift belongs to a volunteer and event.
Objects define the records. Properties describe them. Associations connect them. Association labels explain the nature of those connections. A report cannot reliably reconstruct a relationship that was never stored.
Labels can support record selection, filters, axes, and breakdowns when the required related CRM object is included.
| Contacts as primary source | Donations as primary source |
|---|---|
| Begins with people | Begins with transactions |
| Which contacts have donated? | Which donations have an associated donor? |
| Which contacts have no donations? | Which gifts lack a contact association? |
| How many donations are linked to each person? | What is total revenue by donor type? |
| Which constituent segments give most often? | How many gifts are connected with each household? |
The same two objects can produce different populations and totals. Review HubSpot's data-join information and preview table to see how sources connect and which records will be included or excluded.
Before building the report, define the population. A visitor might be a known contact with qualifying website activity or a form submission. A member might be a contact associated with an active membership record, membership deal, or consistently maintained membership indicator. Conversion means the membership began after the qualifying interaction and within a defined period.
Anonymous traffic cannot automatically be treated as a known person. The visitor must become identifiable through a trackable interaction before person-level activity can be connected reliably with membership.
| Role | Data source |
|---|---|
| Primary population | Contacts |
| Initial interaction | Web activities or form submissions |
| Conversion record | Membership custom object, deal, or other membership record |
| Supporting context | Campaign, marketing email, landing page, or traffic source |
Potential visuals include a KPI, funnel, bar chart, line chart, and validation table. If the question requires a strict ordered sequence, a funnel or customer journey report may fit better than a general cross-object report.
HubSpot may add connecting sources when selected data cannot join directly. Those connecting sources count toward the maximum of five sources in a custom report. If HubSpot cannot establish a supported path, the combination will be unavailable.
A useful architecture may include a sponsor company, a sponsorship deal, employee contacts, employee-company association labels, volunteer participation records, and connected event or program records.
The report can reveal partnerships that extend beyond financial support and sponsors who may be ready for deeper engagement. It succeeds only when company, employee, sponsorship, and volunteer relationships are represented consistently.
One company may have three sponsorships, 20 employee contacts, 50 volunteer shifts, and six events. Combining those sources can create multiple rows for the same company. A simple record count may overstate unique sponsors.
HubSpot notes that multi-source reports may count a record more than once when several associated records satisfy the criteria. Use unique counts where appropriate, inspect unsummarized rows, and compare totals with known records.
Unassociated records may be excluded or appear as “No value,” depending on the primary source and configuration.
Missing associations are an architecture and governance issue, not merely a reporting issue.
Terms such as donor, member, active volunteer, visitor, sponsor, renewal, registration, and attendance must be defined. Decide whether a donor requires a completed payment, whether an in-kind gift qualifies, whether a lapsed member still counts, whether registration equals attendance, and whether volunteer status requires a completed shift.
Cross-object reports may contain contact creation, activity, gift, close, membership, registration, event, and volunteer-shift dates. Choose the date that answers the question. “Memberships created last month” and “contacts who became members last month” may not produce identical results.
Reports cannot compensate for inconsistent object definitions, missing associations, or unreliable property values.
Great reporting should be repeatable, not dependent on the memory of the person who built it.
Cross-object reporting allows teams to connect constituent identities with donations, memberships, volunteering, events, companies, programs, campaigns, sponsorships, households, and other records. It replaces recurring manual joins with reusable analysis when the underlying relationships are modeled correctly.
The value is not complexity for its own sake. It is the ability to answer connected questions with evidence from one coherent CRM.