Olá! Nós temos uma Comunidade em Português!

Be able to amend GDPR Subscription preferences through workflows

The new communications subscription properties are great, however only if using the HubSpot default form properties to gather consent. However, if we use custom properties for example, we have one that asks 'Do you want to optin - Yes or no' radio button, then there seems to be no way of starting a workflow that updates the subscription preferences. Also, third party providers such as Unbounce or Leadpages don't see the subscription preferences, and therefore we have to use custom properties in the forms.
HubSpot updates
53 Comentários
bmccluskey
Berater

This option doesn't exist. Following the steps listed above is a manual process. I shouldn't have to set a calendar reminder to do this daily or weekly - it should be automatic through a workflow. 

LollipopRob
Sachkundiger

^ Agreed

CST
Berater

Hi @bmccluskey,

 

Best practice is using the subscription type found in your system setting, so you don't have to make things unnecessarily complicated by creating workflows.

 

You could run the manual process once to align your contact property to the subscription type and make sure your forms GDPR compliant and have their consent in place containing the subscription type(s) moving forward.

 

It's a one time tedious effort, but it solves your struggles and you're using the system as intended.

raphaelarias
Sachkundiger

@CST

 

We don't use Hubspot forms, so we defenitly need in the workflow and on Hubspot API. A lot of our contacts comes from "Offline sources" and GDPR subscription settings is a manual job for us.

CST
Berater

Hi @raphaelarias,

 

I see your point! That does make things a bit more challenging.

I guess it's not an option to consider switching over to HS forms? ;-)

 

I will keep my eyes open for you guys whenever I find something useful.

KeyWestScott
Profi

We're in the same boat...   (we're a Ferry operation, so pun intended.....)  I have GDPR compliant information on our booking forms.  We we're good to go.  Use Collected Forms to bring that information into HS.  With a Workflow, I can change/update the Legal Basis to Contact, but not assign the Subscription Type.  Support says and can do, a manual update on anyone in that list, BUT.....  If I can do a process manually, why not automatically???  Isn't that what these computer thingies are for????  Língua do Smiley Língua do Smiley

 

Scott  

CST
Berater

Hey Scott!

 

my two cents on this is that Hubspot has build their system so that it works perfectly fine when you're using their tools as intended. If someone only gets to use some of the tools, then things don't necessarily tie in to each other very well.

Hubspot shouldn't have to worry about supporting other ways of working while their system is set up fine.

 

If you'd ask me about the workflows... the idea behind the GDPR is that your contacts/customers tell your business what you are allowed to do with their data. So for me the first vital piece of consent would be to have consent to store and process their data. Once you have that, you can enroll your contact into your HS portal and start moving data around to your needs.

 

Meaning... as long as you don't have their consent logged in the system, you shouldn't be able to process data in the first place so in that case there's also no reason to have the option in for workflows to assign consent.

 

My advice would be, if optional for your business, to start using the HS forms instead. It will make your lives a hole lot easier.

raphaelarias
Sachkundiger

@CST

 

We - businesses - are responsible for GDPR compliance, and I expect the tools I use to allow me to do that, not to prevent me. Specially in an efficent way, because at the end of the day, this is marketing automation, isn't it?

 

Easy to say we should use Hubspot as it was designed, hard to make thousands of business in different industries with different needs to accommodate one or few ways of working with a system.

 

That's why customisable workflows exist. That's why APIs exist and we can do whatever we want.

 

In my case, I can't use the forms. So, that means I'm not using Hubspot correctly? No, it means that Hubspot should support more flexible ways of using the features they designed.

 

And at the end of the day, if I make a mistake using all this flexibility - workflows, API - and because of that I'm not GDPR compliant anymore, that's my responsability.

 

Based on your advice, I should use forms, but what if I can't?

 

And Hubspot feedback on that continues to be silence.

Tnichs Top Contributor | Platinum Partner | HubSpot Certified Trainer
Top Contributor | Platinum Partner | HubSpot Certified Trainer
@CST - Unfortunately it's not always as simple as this. Consider this - A client of mine is a chain of leisure centres with 20 branches. They get walk-in enquiries and joiners which are registered on their bespoke membership management system and all necessary GDPR requirements are met - An API then creates the contact in HubSpot - But there's no way of adding in the permissions other than doing this manually in HubSpot. Or another client who uses Unbounce as a landing page builder as unfortunately as much as it pains me to say, the functionality within HS isn't as good as Unbounce. On the form, we collect the necessary permissions, but there's no way of updating HS with this. Or another client who we are migrating from Infusionsoft over to HubSpot. I need to upload 1800 contacts - With no way of updating permissions. In an ideal world, everything would be done in HubSpot - But I can give you loads more examples where this just isn't possible.
Sidsel_cph
Mitwirkender

@CST We use Hubspot for everything... I do mean everything!

But as a subscribtion based company it is critical if we can't automatically add and (even more important) remove legal basis when a person start/stops as a customer.

I guess I can live with having to add the legal basis manually  – even though I bought HubSpot so they could relieve me from the manual processes. But I can't live with not being GDPR compliant because the legal basis isn't removed the moment a customer stops being a customer. A manual process involving humans is way to fragile a process.