Frequently Asked Questions
Last updated: July 6, 2026
Can we build program-based lists we can actually use for workflows and outreach — not just member vs. non-member?
Yes. Program detail (program name, branch, type) syncs at the line-item level on each registration deal, so you can build cross-object lists of the people who registered for a given program and use them for email and automation. See How to Build a Program-Based List.
Can members and non-members stay on the same list when they're in the same program?
Yes — and that's the default. A program list naturally includes both, because program membership and membership status are independent. When you want to send each group different messaging, branch inside a workflow rather than splitting the list. See How to Segment Members vs. Non-Members.
How do we tell a real program registration apart from a membership-only or fee line item?
Filter on the product type = Program. That cleanly separates real classes from membership renewals and incidental fees. Be sure to filter on the type name/description, not a single type ID. See Product Types.
Can we tie sends to actual class start dates instead of just months or periods?
Yes. The month/period you see comes from how programs are coded, but the actual session begin date lives on the product record and supports "X days before class starts" workflows today. Precise time-of-day scheduling is a planned enhancement. See How to Trigger a Workflow on a Class Start Date.
Why do some join dates look wrong or blank — can we trust the lists?
Earlier placeholder dates (where a missing date showed as an obviously wrong value) have been resolved: a missing date now syncs as a true blank, which carries real meaning (for example, that someone was never a member). You can trust the membership status property for segmentation; if a specific record looks surprising, spot-check it and report anything genuinely off. See How to Segment Members vs. Non-Members.
How do we make sure the right adult receives a child's program emails?
Young children are never emailed directly — they exist only as member records. Their registrations connect to an emailable adult in the household through the member relationships. For clean, direct enrollment of guardians in program emails, a small configuration step is recommended; contact SyncSmart or your partner. See Households, Minors, and Who Receives Program Emails.
Does the data actually support our real list and workflow use cases?
Yes. Member vs. non-member, program name, branch, program-vs-membership separation, and per-session class dates are all supported by data flowing today. Most of the remaining work is HubSpot buildout and enablement — building the lists, workflows, and emails — rather than a question of whether the data exists. Start with The Object Model and How to Build a Program-Based List.