Subscription Setup

[BMelville]

We've recently consolidate with another organization and need to build out a more complex structure to our subscription types. Ideally, we would have an overarching subscription category (e.g. Accounting Updates, Sustainability Updates) and sub-categories under each of those which a user could subscribe to. They could subsrcribe to all or some of the sub-categories to follow relevant information. 

I don't see a straightforward way to set this up in HubSpot, other than to have a separate subscription for every possible combination. Hoping this makes sense, and wondering if anyone has a similar setup in their instance. I am looking for ways to keep this as simple as possible. 

Thanks!

[karstenkoehler · Accepted solution]

Hi @BMelville,

HubSpot doesn't have any out-of-the-box features for nested subscription types, correct. Here are a few things you could consider:

• Unless you want contacts to be able to subscribe or unsubscribe from each nested subscription type, some nuances can also be handled with custom properties, especially to declutter the preference page. Again, this only works if just showing the main types is fine and if the ability to manage preferences for nested types isn't crucial.
• Since contacts can be subscribed to multiple types, you don't necessarily have to create subscription types for all combinations - unless each combination gets specific emails.
• You can use workflows to automatically to opt contacts into subscription types. This allows for a lot of complexity but of course, the preference page would still be cluttered.

For more detailed advice, I'd have to better understand your subscription types and how you use them. If you want to share more details, I can elaborate.

Best regards!

[BMelville]

Thanks so much for your prompt response. Unfortunately our setup is complex in that each combination would get specific emails (depending on which sub-categories they've opted into) and I think we would need contacts to be able to subscribe/unsubscribe to each nested subscription type. From a GDPR-perspective, I don't see a way around that.