Streaming live at 10am (PST)

Auto-fill form values based on URL querystring


Hey mate, this has been a great help to me, but I am having a little trouble with number inputs pulling down from the URL, is there anything I need to add to the code to allow for this?


First and foremost - this thread has been a tremendous help - thanks so much!

Quick question - is there a way to make a field in the form non-editable in nature, while still pulling data from a specific URL parameter to fill that specific form field.

For example, in the screenshot attached below, you can see that a similar site has brought in an email address from the URL, and prompts you to create an account with that email. It doesn’t let the user edit it, as it is already pulling the email from the URL which the user would have entered in an earlier step.

I hope this makes sense! Please let me know if I can clarify further. Thanks in advance! :grinning_face_with_smiling_eyes:

Screenshot - Circle Comm

Yes, but you have to use custom code component to manually code a field with an attribute that does that, or use custom code to set the attribute on page load.

At we have a form on the landing page from where we carry over the e-mail to a form on the survey page. We use @exponent42 's script (from above) as “before-body-tag”

// This ensures the form has been received by the server
$(document).ajaxStop(function() {

and the other script

  function getParam(name) { name = name.replace(/[\[]/, "\\[").replace(/[\]]/, "\\]"); var regex = new RegExp("[\\?&]" + name + "=([^&#]*)"), results = regex.exec(; return results === null ? "" : decodeURIComponent(results[1].replace(/\+/g, " ")); }
  Webflow.push(function() {

in the footer_code section. This works fine for us (thanks btw!). BUT:

Every now and then it happens that the reload is triggered immediately after loading the homepage and not after pressing the submit button of the form. So people that come to our page have no chance to read the homepage because the second page is loaded almost immediately. I can stop this behavior only by deleting all cookies in the browser.

Do you have an idea what’s happening here? Maybe ajaxStop is not what we need, maybe we need something that deletes cookies first?