0
Course / cohort objects in your portal — "course" is only fields on contacts
27
Distinct cohorts spread across those contact fields
101
of 11,290 contacts carry any course data (~0.9%)
15+
Per-contact fields duplicated for every attendee in a session
How it works today vs. a single source of truth
Same cohort — Mastering ToP · Apr 22, 2026 · MRA MN — modelled two ways.
Today — logistics stamped on every contact brittle
The venue / date / hotel / trainer is written onto each attendee individually.
Attendee 1
Attendee 2
Attendee 3
… Attendees 4–9
Change the venue → you must edit all 9 records. Miss one → that person's email merges a blank.
Recommended — one Course record “Stamps” info for all attendees single source of truth
The logistics live once, on the Course record. Attendees are associated to it.
Course · MTOP-2026-04-22-MN
Date: Apr 22, 2026 Venue: MRA MN
Hotel: Holiday Inn Express Lead: Irina
Attendee 1Attendee 2Attendee 3
…Attendee 9
✓ Change the venue once → it updates for all 9 instantly. Nothing to keep in sync.
Why the current model is hard to scale & keep accurate
No stable cohort key
A "cohort" is only identifiable by the fuzzy string course_name + date + venue.
course_code / course_id are empty on every record.Dirty, blank-prone identity
Names carry typos and many records are no-date, no-venue, or TBD — exactly the blanks that flow into the emails.
Duplication = drift
The same logistics are repeated on every attendee, so there is no one place to update and values drift apart over time.
Evidence: Apr 22 venue/hotel/trainer copied across all 9 attendees.Tiny, fragile coverage
Only ~0.9% of contacts are course-tagged, so for almost everyone the merge fields resolve to nothing.
Evidence: 101 of 11,290 contacts; venue set on just 73.What "right" looks like
- Use the native Course object (already active on your plan). One record per dated session — holds date, venue, hotel, parking, lead trainer once.
- Associate attendees to the cohort with association labels —
Registered·Attended·Cancelled·No-show— the exact pattern HubSpot's community recommends for events and courses. - Stop duplicating logistics on contacts. The contact keeps who they are; the cohort keeps what/where/when. Update the venue in one place.
- Send cohort comms as workflow-triggered marketing emails keyed to the cohort, not 1:1 sequences. (Personalization in sequences reads from the contact/sender, not associated custom objects — another reason these belong in workflows. Ties back to the "sequences vs. workflows" mismatch.)
Good news on tier: the Course object is part of HubSpot's Object Library, which activates on your current Marketing + Sales Pro plan (a Super Admin has already activated it) — it is not a fully-custom object that would require an Enterprise upgrade. One email caveat remains: marketing emails merge Contact/Company tokens, not Course-object tokens, so a small copy-down workflow stamps the Course's venue/date onto associated contacts for the send — you still edit the Course once.
What the authorities say
"Each object has individual records which can be associated with records of other objects… information is stored in properties." The data-model usage view even surfaces "the number of properties that have no data, are unused, or are potential duplicates."
HubSpot's own model is object → associations, and it flags blank/duplicate properties as a data-quality problem — exactly what we're seeing.
SmartBug Media — HubSpot's Standard Objects vs. Custom Objects (HubSpot's 2025 N. America Partner of the Year)
"When you are ready to start establishing relationships in your data between one-to-many rather than one-to-one, you will want to start structuring your data with custom objects." Update a shared record once and it "would automatically update and reflect" everywhere it's associated.
One course → many attendees is the textbook one-to-many case for a custom object — and the source of the single-source-of-truth benefit.
HubSpot Community — Courses object & enrolling students in multiple courses · Structuring objects for event attendance
Create an Event/Course object and associate contacts with labels for "Registered, Attended, Cancelled, and No Show"; change the relation to many-to-many so "a single contact [can] be associated with multiple courses."
HubSpot's community has solved exactly this (offline courses + attendance) with a Course object + association labels.
Move high-volume / repeating data off contact properties and into custom objects, where you have far more room and a cleaner structure; audit and de-duplicate properties first (teams often cut 30–40%).
Reinforces that repeating, structured data (course logistics) doesn't belong sprayed across contact fields.
"Accurate CRM data allows sales and marketing to operate from the same source of truth." MDM creates a single "golden record"… and strong data hygiene drives "up to 70% improvement in email deliverability and 25% increase in sales productivity."
The single-source-of-truth principle isn't just tidiness — it's tied to deliverability and revenue outcomes.