1 · The key insight: it's two locks, not one
A contact can only receive marketing email when both are true. Your workaround exists because imported/Arlo contacts fail both.
Lock 1 · Billing / reachability
The "marketing contact" flag
Only marketing contacts can get marketing emails or the Workflow "Send email" action — and only they count toward your ~12k cap. Imports & integrations create contacts as non-marketing by default.
Lock 2 · Legal basis
Consent / subscription opt-in
A contact must have opted in to a subscription type (a real consent record). Just flipping the marketing flag does not create consent — that's captured at registration via a consent checkbox.
Why your workaround "works": HubSpot lets sales 1:1 emails and Sequences send regardless of marketing status — so a Sequence reaches non-marketing contacts where a marketing email can't. That's exactly why the team reached for it (and the Enrollem workflow→sequence bridge). It's mechanically functional but it's marketing mail with no unsubscribe, sent from a personal inbox.
2 · Why imported & Arlo contacts arrive locked
HubSpot sets a different default per tool — this is the root cause.
| How the contact is created | Default marketing status |
|---|---|
| HubSpot form submission | Marketing ✓ (and flips an existing non-marketing submitter to marketing) |
| Manual entry | Non-marketing |
| Import (multi-file/multi-object always; single-object optional) | Non-marketing |
| Any integration / API — incl. Arlo via Zapier | Non-marketing |
So WordPress submitters who go through a HubSpot form are already fine; your imported contacts and Arlo registrants are the ones stuck as non-marketing.
3 · The recommended architecture
flowchart TD F["WordPress / hue.life
HubSpot form (or WP plugin)
+ Notice & Consent block"]:::wp AReg["Arlo registration
(add a consent checkbox)"]:::arlo F -->|"auto-marketing ✓
+ subscription opt-in"| HSok[("HubSpot contact:
marketing + consented")]:::ok AReg -->|"Zapier (no native connector)"| HSraw[("HubSpot contact:
non-marketing, via API")]:::raw HSraw --> Q{"Consent captured
in Arlo?"}:::dec Q -->|"Yes → set subscription"| SET["fa:fa-gear Workflow:
Set marketing contact status → Marketing"]:::wf SET --> HSok Q -->|"No"| TX["Stays non-marketing →
registration/transactional emails only"]:::no HSok --> WIN["fa:fa-circle-check Proper Workflows + marketing emails
(retire the Sequence / Enrollem workaround)"]:::win classDef wp fill:#FDEBE8,stroke:#EF4C32,color:#a3301c; classDef arlo fill:#e7f0f4,stroke:#2f6f8f,color:#1f4d63; classDef ok fill:#eef6f3,stroke:#1d7a5f,color:#1d7a5f; classDef raw fill:#fff,stroke:#cdd3d9,color:#232b33; classDef dec fill:#fff5ee,stroke:#EB5825,color:#8a3d1e; classDef wf fill:#eef0f2,stroke:#6b7682,color:#3f4852; classDef no fill:#eef0f2,stroke:#6b7682,color:#5a6b73; classDef win fill:#eef6f3,stroke:#1d7a5f,color:#1d7a5f;
4 · The WordPress path native & easy
- Capture hue.life registrations through a HubSpot form (embedded) or the HubSpot WordPress plugin — or, for non-HubSpot forms, the "non-HubSpot forms" tool with its "Set new contacts as marketing" toggle ON (needs the HubSpot tracking code loaded).
- Add a Notice & Consent block tied to a subscription type (e.g. "Course updates," "Newsletter"). Checking it records opt-in + sets legal basis to "Freely given consent."
- Result: the submitter is auto-flipped to marketing AND consented in one step — no extra workflow needed.
5 · The Arlo path needs a bridge
Arlo has no native HubSpot integration — it connects only through Zapier, so registrants arrive via API as non-marketing with no consent. Three steps fix that:
- Capture consent inside the Arlo registration (an opt-in checkbox / field) so there's a real basis to market — don't just flip a flag.
- Zap Arlo registrants into HubSpot, mapping the consent field to a HubSpot subscription opt-in.
- A HubSpot Workflow → "Set marketing contact status → Marketing" (available on your Marketing Pro tier) flips only the consented attendees.
Verify in the Zapier Arlo app: it's not documented whether Arlo can pass a consent/opt-in field through Zapier, or only a generic contact. If it can't, you'd re-collect consent via a quick HubSpot form/email after import. Confirm this before building.
6 · Billing & the people who don't consent
This approach is also the right way to manage your ~12k cap.
- Only marketing contacts count toward the cap — so flipping only consented attendees spends cap deliberately, not mechanically. (Your 11,290 non-marketing contacts cost nothing today.)
- Non-consenters stay non-marketing and are still reachable via registration / transactional emails (allowed regardless of status) and genuine 1:1 sales contact — you don't lose them, you just don't market to them.
- Consider turning ON HubSpot's "only allow marketing emails to contacts with a legal basis" setting so consent becomes the hard gate (recommended even though US/CAN-SPAM is opt-out, not opt-in).
7 · This retires the workaround
Once registrants are properly marketable, the reason Sequences (and the Enrollem workflow→sequence bridge) were used for cohort comms goes away. Keep Sequences only for genuine 1:1 sales outreach; move all cohort/lifecycle comms to Workflows + marketing emails (with real unsubscribe). Ties directly to the Sequences vs Workflows guidance.
8 · Verify before you build (open questions)
- Arlo + consent via Zapier: can the opt-in field actually flow into a HubSpot subscription, or must consent be re-collected in HubSpot?
- The ToP-cert-org attendees: for classes registered through the certifying organization, does HueLife have the legal right/relationship to market to them at all — or are they the cert org's contacts? (Decide this before soliciting consent.)
- Cap headroom: how close are you to ~12k marketing contacts today? Confirm room before mass-flipping Arlo cohorts (it could trigger a tier bump).
- Data-privacy tools: are HubSpot's consent/GDPR tools already on in portal 44205564? That changes whether the consent gate is enforced automatically.
9 · Sources
Verified against HubSpot's first-party documentation (current to 2026) plus Arlo's own pages.
"Only marketing contacts count toward your contact tier… you can send other types of emails… regardless of their marketing status, including sales one-to-one emails, sequences, registration emails."
"The HubSpot forms tool sets contacts as marketing by default… any existing non-marketing contact who submits the form will be updated to a marketing contact." Imports / "any integration or API sets contacts as non-marketing by default."
"A Professional or Enterprise subscription is required to automatically set contacts as marketing via workflows." (Available on your Marketing Hub Pro.)
Non-HubSpot form capture needs the tracking code/WP plugin and has a "set as marketing" toggle; consent blocks let "contacts opt in to your email subscription types through a form that includes a notice of consent."
"Toggle the Send emails to contacts with legal basis switch on… emails can only be sent to contacts who have a valid legal basis to communicate and an Opted in status." (Recommended control; not auto-enforced under US CAN-SPAM.)
"Arlo connects to Hubspot using Zapier" — no native marketplace connector; the pages document no marketing-contact-status or consent capture, so that must be handled HubSpot-side.
Scope note: This is HubSpot/Arlo mechanism research, not legal advice. Actual CAN-SPAM / Minnesota compliance (clear unsubscribe, accurate sender, no purchased lists, and whether you may market to cert-org attendees) should be confirmed with counsel. One claim was qualified in review: the "can't email un-opted-in contacts" block is enforced only when HubSpot's data-privacy tools are on — for US senders it's a control you choose to enable.
← Back to Sequences vs Workflows