An unsubscribe link alone cannot document a SaaS consent model. When promotional, educational, and customer emails all share one category, contacts lose control over what they receive.
Well-configured HubSpot subscription types give recipients meaningful choices and give your team a clear record of each email’s purpose. They also reduce the chance that a workflow sends a product webinar invite to someone who only wanted release notes.
Start with the sending purposes your business actually has, then connect those purposes to forms, email settings, and routine testing.
What HubSpot subscription types control
A subscription type is a named category of marketing email. It appears on your subscription preference page, where contacts can opt in or out of individual communication categories.
When you select a type for a marketing email, HubSpot uses the contact’s status for that category when applying subscription preferences. A contact who has unsubscribed from the selected type should not receive that email.
However, subscription types are only one part of email governance. Keep these three layers separate:
| Layer | What it controls | What it does not control |
|---|---|---|
| Contact subscription status | Whether a contact is subscribed or unsubscribed from a defined email category | The wording or proof of a form consent interaction |
| Form consent notice | The disclosure and consent action presented when someone submits a form | Future email eligibility on its own |
| Email-send eligibility | Whether HubSpot can include a contact after checking the chosen type, lists, suppression rules, and account settings | Whether your category names accurately describe the message |
A subscription type does not write your privacy notice, decide your legal basis, or turn an imported contact into a documented permission record. It also doesn’t make a message transactional. Password resets, invoices, security notices, and other operational emails often follow separate sending rules and internal policies.
A visible privacy policy link is different from a recorded agreement to receive a defined email category.
For that reason, treat subscription status, consent capture, and send eligibility as connected controls, not interchangeable ones.
Build a SaaS email taxonomy people can understand
Useful categories describe the purpose a recipient recognizes, rather than the team that owns the campaign. “Marketing updates” is broad. “Product updates” tells a customer what they are choosing.
A practical starting taxonomy for a SaaS business might look like this:
| Subscription type | Include | Keep separate |
|---|---|---|
| Product updates | Feature releases, availability announcements, optional roadmap briefings | Required outage or security notifications |
| Educational content | Guides, training resources, newsletters, and on-demand learning | Promotional event invitations |
| Events and webinars | Event invitations and optional follow-up content | Registration confirmations that are purely operational |
| Customer communications | Adoption tips, account-admin education, and non-urgent service updates | Billing, password resets, and required account notices |
These categories are examples, not a universal template. A developer tool may need release notes and technical webinars. A finance platform may separate regulatory education from product news. Base the taxonomy on your actual sending purposes, customer expectations, and approved communication policy.
Avoid creating a new type for every campaign, region, or internal team. Subscription types should remain stable enough for recipients to understand over time. Campaign names, audience segments, and lifecycle stages belong elsewhere in HubSpot.
Also, write descriptions as recipient-facing promises. “Receive product announcements, feature availability notices, and optional release briefings” is clearer than “Product comms.”
Set up HubSpot subscription types in the current interface
Before creating anything, inventory your existing newsletters, automated workflows, sales handoffs, and customer email sequences. Each recurring marketing purpose needs an owner and an approved subscription category.
The current path is Settings > Marketing > Email > Subscription Types. HubSpot’s official subscription type setup instructions are the best reference if menu labels change in your portal.
Use this sequence for each category:
- Open the Subscription Types tab and select Create subscription type.
- Choose the language that matches the recipient-facing name and description.
- Enter a short subscription name, such as “Product updates.”
- Add a description that explains the messages people can expect.
- If data privacy settings are enabled, select the Purpose of subscription and set the Method of communication to Email.
- Review the preview carefully. This is how the category appears on the subscription preference page.
- Select Create, then place the type in a sensible order on the preference page.
Put high-frequency, broad-interest categories near the top. More specialized categories, such as partner webinars or beta-program announcements, can sit lower on the page.
HubSpot also lets admins edit, reorder, and archive types from the same area. Archive a category only after you have checked email templates, workflows, forms, and integrations that may still reference it. Replacing a type without auditing those assets creates confusing preferences and interrupted automation.
During implementation, compare your new HubSpot subscription types against every active marketing email. Each email should use the category that matches its actual content, not the category that happens to have the largest audience.
Connect forms, consent notices, and email workflows
Forms are where intent enters your system. A person might request a demo, download a guide, register for a webinar, or create a trial account. Those actions don’t all justify the same email category.
Where your HubSpot form uses communication consent controls, map the consent choice to the relevant subscription type. For example, a webinar registration form can offer consent for “Events and webinars.” A content download form may offer “Educational content” without automatically subscribing someone to product announcements.
Your legal or compliance owner should approve consent wording, disclosure text, and the conditions under which a team can add or update subscription statuses. This configuration supports your process, but it does not guarantee compliance with GDPR, CAN-SPAM, or any other law.
Contact behavior can change after form submission. Someone may agree to receive educational emails, then later unsubscribe through the preference center. The current contact subscription status should guide future marketing email sends.
You can review a contact’s state in CRM > Contacts. Open the record, then select View subscriptions in the Communication subscriptions section. HubSpot’s guide to managing contact subscription preferences also covers updates through records and workflows.
For product-led signup flows or custom preference centers, use documented subscription identifiers rather than matching on a label that someone may edit. HubSpot’s communication preferences API guide explains how integrations can work with subscription types and contact statuses.
Do not use a workflow to silently re-subscribe contacts after they opt out. If a legitimate process updates a status, document the trigger, the owner, and the data source.
Run a controlled test before your first campaign
Implementation checklist
Before publishing forms or activating workflows, confirm the basics:
- Every active marketing email has a subscription type that matches its stated purpose.
- Each type has clear recipient-facing wording and an approved internal owner.
- Forms capture the right consent action for the communication being offered.
- Workflow emails use the same category promised by the source form or signup flow.
- Suppression lists, marketing contact settings, and global opt-out handling are part of the send review process.
- Retired categories have no remaining dependencies in emails, forms, or integrations.
Test with a dedicated contact
Create a test contact with a mailbox your team can access. If your portal manages marketing contacts, follow your normal process for marking that contact as eligible for marketing email.
First, submit each relevant form as the test contact. Check that the consent notice displays correctly and that the form associates the expected subscription category.
Next, open the contact record and use View subscriptions to inspect the saved status. Record the result and the source of the update.
Then send a test marketing email that uses one subscription type. Confirm that the test contact receives it when subscribed. Use the email footer to open the preference page, unsubscribe from that category, and send the same test again. HubSpot should exclude the contact from the category they left.
Finally, test a second category. A contact who leaves product updates should still be able to receive educational content if they remain subscribed to it. That distinction is the practical value of a well-designed preference center.
Conclusion
A preference page only builds trust when its choices match the emails people receive. Clear categories, honest form language, and regular testing turn HubSpot subscription types into a reliable operating control.
Keep the taxonomy small, assign owners, and review it whenever your product, email program, or consent process changes. Your subscribers should always be able to understand what they are choosing and change that choice without friction.
