GDPR - Form Submissions will no longer work on Exported sites :-(

Looks like I was off on my estimation on how long this has been the case. It is apparently a every-two-years thing to talk about whether or not to make this change and I’m now neck-deep in this platform as opposed to knee-deep like the last time.

Hey everyone, thank you for all the feedback. We’re listening, and I hope that I can answer the questions being raised here.

Since there’s a lot, I’ll try to respond point by point…

Seems like a gimmick to get users to pay for Webflow hosting.

For what it’s worth, this is not the reason behind this change. While it would be good for us for folks to sign up for more hosting on our platform, the vast majority of the Export use cases in Webflow have so many export-dependent requirements (e.g. code changes need to be made, conversion needs to happen to a WordPress theme, etc), requiring hosting for form submissions from exported sites would likely not even make a dent in our hosting revenue.

Does this mean that for all Webflow hosted sites, the Webflow team will ensure that all forms are properly set up with no hidden checkboxes so as to ensure that all sites are GDPR compliant?

No, unfortunately we cannot ensure this at this time, given the multi-faceted nature of GDPR requirements and the still-pending upcoming rules in the ePrivacy Regulation, which will be additional to the current GDPR regulations. However, it does make it significantly easier for us to implement future changes to our forms functionality to aid our customers in complying with regulations if there’s the common baseline assumption that form handling code cannot be modified or circumvented.

(As a tangential benefit, it also helps us build other form-based improvements – such as reCAPTCHA and file upload support – significantly faster.)

If Webflow is just the data processor, why does it matter how users collect the data whether hosted on Webflow or externally?

Even though we are “just” a data processor for form submissions, we still have to take reasonable steps to ensure that we are doing everything in our power to protect personal data. As a processor, we are required to map out and document exactly how personal data could be sent from browser to server – and on exported sites, we can’t map this out with certainty.

What is the alternatives?

One of the easiest integration options today is to send form submissions to MailChimp - we have a guide on how this can be set up.

We are in the process of creating additional guides on integrating exported forms with other external form providers, such as Wufoo.

it really seems as if they lack effective communication about these forms and how they operate

You’re right, and for that I personally apologize. :bowing_man:‍♂️ This has historically been an area of ambiguity in our pricing pages and feature listings, and that sucks. GDPR forced a conversation on this internally, and we’re now actively working to reconcile all of our internal and external documentation to make it clear that form submissions will not automatically work on exported code.

I have no option but to pay an experienced developer to reconfigure these forms for multiple clients.

To help with this, we’re going to extend the timeline of this migration for existing exported sites – and will be adding more content like our MailChimp Integration guide to make finding a developer not necessary.

We’re also considering extending the timeline for capturing form submissions beyond July 31st to give everyone more time to make this transition.

I don’t know whose idea it is to repeatedly attempt to get people to pay for hosting

As mentioned before, this is not the motivation. Sure, it does become easier to deal with this by hosting with Webflow, but that only applies to a tiny percentage of our export use cases – and would not make a material difference for Webflow’s business.

Not only that, but you can put an HTML embed into a form, and Webflow is apparently not checking the code on those anymore sooooooooooooooo… you could still hide a checkbox if you wanted to.

Yes, as long as that embed is an <iframe>, there’s already an expectation that Webflow is not in control of custom code as a data processor – similar to how we’re not in control of the data that might be collected by Google if a YouTube video is embedded on a published site. If, however, Webflow was directly offering a feature that is clearly not dependent on a 3rd party processor (such as our forms collection, or Background Videos), we have a heightened responsibility – at least from how we currently understand our role under the new GDPR rules.

I’m not paying an additional $2,640+ per year for the privilege of remaining [a customer]

If you use the MailChimp integration mentioned above (and some other free solutions we’ll be suggesting soon), there is no requirement for you to switch to our hosting solution to preserve form submission functionality.

Can you guys give us an option in the settings area to hook up our forms to something 3rd party and cut Webflow out of the process for those who wish to export?

Webflow already has this, either via a custom Action on each individual form or via something like our MailChimp Integration. :grinning:

I wish there was more focus and encouragement on the exporting of clean code for further development and hosting where you like. I want devs around the world to know webflow as the #1 platform for prototyping / quick development of front end etc and be backed by this amazing ability to export clean code and do with it what you like. Instead its tracking more towards these web builder platforms[…]

This change will actually make this distinction easier. By clearly separating form submissions as a hosting/platform function (similar to CMS, Site Search, ECommerce, etc), it frees up more of our design tooling team to build more general non-hosting features, such as CSS Grid Layout, Photo Galleries, etc.

However, it’s important to note why Webflow provides all the platform-level integrated features. The vast majority of people who use Webflow are professional designers who just want to create and deliver solutions for their clients - in most cases, they’re not expert coders, they don’t have easy access to developers, and don’t have the desire to set up their own server/hosting stack.

So creating a straightforward way for them to design and launch/run sites in production is a lifesaver, and in many cases means the difference between running a web design business and not being able to. For those folks that know how to export code, modify it, and run a server – that’s great, but for the majority that’s not the case, and Webflow provides a lot of added convenience.

I hope all that makes sense, and please let me know if you have additional questions. Thank you for reading! :bowing_man:‍♂️

10 Likes

@callmevlad Thanks for the comprehensive response and explanation.

@Thomas_92 @Cricitem @Robit97 @NewInBoston
I just set up one of my forms with a new service called Formcarry - www.formcarry.com

Pretty quick and easy to set up.

  • Will need to make a new account for each website but I’ll just use alias email addresses of my own for each site.
  • Then change the form to POST and add the Action URL.
  • Then export the site and that’s it!

It’s a bit of hassle but nothing too strenuous (depending on how many externally hosted sites you have!)

6 Likes

Thanks for the detailed follow up Vlad. I should have mentioned in my previous response that I understand why GDPR is forcing Webflow’s hand and that this is not a ruse of some sort to force hosting onto others.

I didn’t realize the form action was an option, thanks for pointing that out. I’ll edit my previous post!

Learning everyday… :slight_smile:

1 Like

Wait…

Does this also apply to forms that are sending data to Zapier?

I’m not sure if it does. Try it

I can’t try it. I won’t know until Webflow breaks all of my forms. I doubt I’ll get an answer otherwise.

This garbage is probably going to put me out of business. I wish I were being melodramatic. This is about to cost me a [redacted] amount of money.

Why can’t you try it? It takes a few minutes only.

I already have a Zapier account for one of my clients who has emails automatically generate a salesforce lead.

If this breaks that…

Does this also apply to forms that are sending data to Zapier?

It does if that data is sent to Zapier via Webflow’s servers.

I won’t know until Webflow breaks all of my forms.
This garbage is probably going to put me out of business.

Don’t worry, none of your existing working forms will break - we’ll make sure that there’s plenty of time to consider other solutions for existing exported sites that rely on our forms functionality, including extending the July 31st timeline further.

As @Diarmuid_Sexton pointed out, there are multiple ways (e.g. using MailChimp, Formcarry, etc) that this change can happen at zero additional cost. All of those tools support the same Zapier hooks, so your Salesforce integration will keep working with some slight changes on the Zapier dashboard.

This is about to cost me a [redacted] amount of money.

Also, can we please keep this community forum discussion civil, @Cricitem? Please see our Community Guidelines.

1 Like

https://formspree.io/

Another form handling service. Free for up to 1000 subs/month per email address.

And then a plethora of options compiled by this dude above for people hosting static sites…

4 Likes

I don’t know what that means.

I went through the Zapier integration. I sent a test through and that email shows up on the Webflow dashboard. How do I get it to NOT do that, since I’m assuming that is what is causing this entire nonsense problem? Do I have to add another processor between Webflow and Zapier? All of the others send through absolutely garish notification emails with gigantic logos.

There needs to be a better solution than, “Go through this free service that puts their logos at 100px height at the top of every notification email your otherwise-white-labeled customer receives.”

Thanks for a detailed response Vlad.

It’s good to hear your intentions surrounding the changes, and I can see your point re a clearer distinction between the the areas. I guess the main gripe will be over communicating with multiple clients and then transitioning the way we approach site forms for smaller builds.

I think if the team (maybe nelson :wink: ) could provide us with some documentation or a video on recommended alternatives and a process then it will make it easier for all. And of course when its possible, clearer documentation surrounding these types of features, so we don’t end up in situations making changes for a number of clients.

Thanks

Great one @Diarmuid_Sexton!!! You’ve nailed it :wink:

Relax. The writing has been on the wall for a while. I almost exclusively export and dropped webflow forms way back. There are plenty of affordable options. BUT, you really should dump the idea of providing hosting for free… The surplus from hosting fees should cancel out your other overheads and then lead to a small passive income by quantity.

I use netlify for hosting and netlify forms. There are also numerous other third parties to look at (with better flexibility vs webflow forms IMO).

I’m not a developer. A github thing doesn’t help me at all.

I’m sorry that it’s so annoying for me to be trying to keep doing business with Webflow.

As it stands, this completely unnecessary change (for any client based in the US, this is a 100% unnecessary change), is costing me money and that money is going to have to come from somewhere in my budget. Since Webflow is surrendering the main portion of its service that was utility rather than convenience (and the main driving force for me starting up with Webflow in the first place), the Webflow portion of my budget is the part that is most likely to get cut.

You’ll probably be able to get away with fixing this almost completely for free (perhaps a small amount per month for high traffic sites with high form usage).

I’ve made a thread where people can post their solutions.

The tool I use requires my site to be hosted with them (netlify forms) but like others it’s been a simple case of just adding a basic line of text to the action field and perhaps 1 attribute to the form (from within the webflow editor). It takes me about 10 seconds and I do it as soon as I build the contact page so it’s done and forgotten.

Hey everyone, there is a growing list of suggestions over at Any Suggestions on Replacing Exported Forms of Webflow due to GDPR?, including a new video guide on how to easily hook up existing forms to Mailchimp on Webflow University.

I’m going to close this topic for now to avoid two separate threads.