Architecture | Entry 9 of 11
Association labels explain what a relationship between two CRM records means. An association shows that records are connected. A label adds the context staff and supported HubSpot tools need to distinguish an employer from a sponsor, a primary donor from a soft-credit recipient, or a preferred mailing address from a tax-letter address.
HubSpot associations connect records. A contact might be associated with a household, company, donation, volunteer assignment, program enrollment, membership, or another supported record type.
The connection alone may not explain the nature of the relationship. Association labels give it a defined meaning, such as:
The right labels depend on the nonprofit's data architecture and operating processes.
A single label describes a relationship in the same way from either direction. Examples include Colleague, Sibling, Board Member, or Program Partner.
Paired labels use different terms for each side of a relationship, such as Parent and Child, Employer and Employee, Household and Household Member, or Sponsor and Sponsorship Contact.
When one side of a paired relationship is applied, HubSpot can apply the corresponding label to the other side. This makes the relationship understandable from either record.
One constituent may have several records of the same type connected to them: multiple households, a current and former employer, several donations, current and expired memberships, or different relationships with the same organization.
Without labels, staff may see that records are connected without knowing which relationship matters for the task at hand. Labels help answer questions such as:
Association labels help staff, workflows, segments, reports, and other supported CRM tools answer those questions consistently.
A nonprofit has one household record for the Santos family and uses labels to clarify how each person and organization relates to it.
Staff can understand each relationship without opening every record or relying on free-text notes. The labels can also help the nonprofit address household communications, assign soft credit, create reports, identify corporate connections, segment board members, trigger workflows, and show staff the right associated information.
Yes, if addresses are stored as separate associated records. Labels such as Primary Residence, Preferred Mailing Address, Seasonal Address, and Tax-Letter Address can tell staff and supported automations how each record should be used.
A year-end workflow could then select the record labelled Tax-Letter Address. However, many nonprofits only need address properties on a contact or household record. A separate Address object makes sense only when the organization needs multiple address records, history, independent reporting, or complex automation.
Labels help staff understand why records are connected. Instead of seeing several unexplained company records, a user can identify an employer, sponsor, and board affiliation.
Supported workflows can use labels to find the correct related record, such as the Primary Household Member, Tax-Letter Address, Sponsorship Decision-Maker, Current Employer, or Active Membership.
Labels can support precise segments, such as contacts associated with companies as Board Members or contacts associated with donations as Soft-Credit Recipients.
Supported reports can focus on the relevant relationship instead of including every record connected to an object.
Labels can tell integrations what kind of relationship they are creating or updating. Because HubSpot currently warns that a label's internal name cannot be edited after creation, that name should be planned carefully before API use.
Too many overlapping labels can make the CRM harder to use. Main Donor, Primary Donor, Lead Donor, and Principal Donor should not all exist if they mean the same thing.
Before creating a label, define:
The team should also decide whether the concept is a relationship or a status. Employer describes how a contact and company relate, so it may be a useful label. Active Member may be better stored as a property on a membership record.
Association-label features depend on the HubSpot subscription, object pair, user permissions, and account configuration. Eligible Professional and Enterprise accounts can create labels for supported object pairs, but custom labels are not available for every object.
Before implementation, confirm:
HubSpot currently allows up to 50 labels per object pair, with a paired label counting as one toward that limit. The nonprofit should confirm current support before designing a critical process around any label.