|
You can insert forms into your Landing Page using a dedicated Form Block= . |
V1.7=
Forms can be embedded in Landing Pages for different purposes, from simp= le forms for registering for a newsletter to complex questionnaires.
=20- =20
- Adding a form =20
- Viewing form results=20 =20
Adding a form
Each form is contained in a Landing Page block that is added to the page= like all other blocks, by dragging.
See Form Block to learn about t= he settings that are available.
Viewing form results
Viewing all forms
To view a list of all forms, click Content in the Navig= ation hub and select Form Builder.
![](=3D"/download/attachments/32869495/form-builder-in-menu.png?version=3D1&=)
You can see there a table with every form placed anywhere in your site, = with the number of submissions and other details.
Previewing form submissions=
When you click any of the forms, you can see a table with all the entrie= s submitted using the form.
Deleting form submissions
You can delete any submission by clicking the Delete bu= tton in the table.
Downloading form submissio= ns
You can also download all the submissions to a form in a CSV (comma-sepa= rated value) format by clicking the Download Data button o= ver the results table.
Best Practice
Avoiding possib= le inconsistency in forms:
When creating a form using Form Fields each field is reflected with a un=
ique ID in the database. This unique ID is tied with this field, regardless=
of changes made in Form Builder afterwards.
This means that editi=
ng a field in a form that is already published may lead to possible inconsi=
stency of data provided by viewers.
For example: If you decide to =
gather a wider range of information from viewers, using a form that consist=
of many Form Fields is the best idea. However, after some time, it may see=
m reasonable to re-use one of the fields by changing its name and to collec=
t information that requires the same field type. Let's say the field <=
strong>Name is renamed to Full Name&nbs=
p;in order to make it more clear for viewers and collect more accurate data=
. What happens here is that all entries from field's old version&nb=
sp;and all entries from updated field are now saved under the=
same unique ID.
Best practice is to remove the old field and create a new one with a new= unique ID if there is a risk of inconsistency.