Advanced Customisation

The above is enough to create a simple registration form that will collect email and name (automatic) and some textual comments. If you want to take your form to the next level, you’ll want to use additional questions to collect custom information specific to your use case.

Additional Questions

You can add as many additional questions as you like to your form. Each question you add will add a new input on your form for customers to fill in. Here are the options you need to configure for each additional question:

• Slug: a simple slug-style, internal name for the question (used when creating custom URLs, more on that later)

• Disabled: disable input to this field (this sounds useless, but can be powerful when used in conjunction with ‘prefilled’ data, more on that later)

• Hidden: completely hide the input from the customer (again, sounds useless, but you’ll see why it’s useful shortly)

• Required: make the field non-optional

• Placeholder: customise the placeholder text in the input field in order to clarify what information a customer should provide

• Choices: instead of free-form text input, provide a list of options for the customer to choose from

Prefilled Data

Once you’ve configured any number of additional questions, they will show up as additional fields in the form input. You can stop there, but there are some interesting advanced features that make the form functionality even more powerful, namely “prefilled data”

Prefilled data means providing the form to the customer in a state where one or more of the additional questions are already filled in. Here are some potential use cases for this trick:

• Completely prefilling out the form to make life easier for the customer (so essentially you are just collecting and registering their permission/subscription option/privacy preferences/signature)

• Prefilling the customer source (e.g. the link from a particular ad compaign could codify that they came from that campaign)

• Prefilling complex pieces of data like model numbers or serial codes

• Prefilling agreed pieces of data, like credit terms

Prefilled data fields are “fed through” to the form via URL parameters, so the link to a form with the question “Where did you find us?” and answer “Google” might look like this:

/form/my-form?form-question-key=source&form-answer=Google

A customer arriving at the form via this link would find the ‘source’ field prefilled with the answer “Google”.

This is where ‘disabled’ and ‘hidden’ options come into play. If you want to prefill with some data but don’t want the customer to be able to change that answer, choose ‘disabled’. If you want the answer to register with the form submission but don’t even want the customer to be aware the question exists, simply choose ‘hidden’.

URL Builder and QR Code Generator

Obviously creating URLs like the one above by hand would be time consuming and error prone, so we provide a URL Generator directly inside the form record where you can build up sets of answers to questions, save them and see/copy the corresponding URL. Each URL generated also gets a custom QR code that links directly to the prefilled form - so if it’s more convenient you can have customers scan a QR code to get to the form - this is great for product and packaging labels where you might want guide a customer to a product registration form.