
Pittsburgh Greenfield Bridge Demo
And, of course, we know HubSpot Support always offers the best solution. 
Cycling the HubSpot GDPR toggle as a DOI workaround will be like getting your truck stuck under a bridge then blowing up the bridge to get it out. The better solution is to simply take the air out of the tires, roll it out, then re-inflate. More work in the short-term, but much less of a mess to clean up afterwards. And, you won’t wake the neighbors! 
Read then rethink for yourself Antonia -- Things That Change In HubSpot When You Toggle GDPR
As you stated, the better solution would be to simply allow HubSpot DOI functionality to handle the task since contacts created via the HubSpot API are also eligible for DOI if enabled (see How To Setup DOI For HubSpot Emails). However, again, these are NOT toggles to use as temporary workarounds (ever). Both the HubSpot GDPR and the HubSpot DOI settings have serious far-reaching implications for contacts, forms and pages portal-wide. Unless a Super Admin fully understands each of those portal-wide implications (rare outside the HubSpot Product team), doing so is just irresponsible. (no matter who recommends it)
An alternative when HubSpot DOI isn’t an option would be to build out an opt-in confirmation workflow. (fairly easy with zero risk)
Just a thought … ok, 2 thoughts! haha
-ps
>>“since typeform creates a form in HS”
Thought Typeform creates HS contacts via the HS API. Did that change?
Help answer your question? If so, remember to accept this solution now.
Best,
Frank
Remote B2B Digital Marketing Manager
MFrankJohnson.com | Connect on LinkedIn
Help find posts quickly … accept this solution now.