Skip to main content
Web Forms Glossary

The A-Z of using Web Form Manager

Dom Yeadon avatar
Written by Dom Yeadon
Updated over 5 months ago
  • Step 1. About: this step contains an overview of the web form.

  • Step 2. Configuration: this step is where you choose the data destination, consent and tracking.

  • Step 3. Builder: this step is where you build your web form.

  • Step 4. Theme: this step is where you choose the styling for your web form

  • Step 5. Preview: this step is where you see how your web form looks and works

  • Step 6. Performance: this step is where you see how the web form is performing.

  • Academic Block: used to control Year Of Entry, Level Of Study, Subjects and Courses.

  • Address Finder: students can enter a postcode and choose their full address without typing it all out.

  • Add a New Form: where you create a new form from scratch.

  • Add Enquiry Occurrence: the setting that adds enquiry questions to a RAP form, and sends data into the selected ENQ occurrence.

  • Address Block: where you collect postal addresses and can choose to use the address finder.

  • Archiving: the process of changing the status of a web form to make it unavailable.

  • Auto-save: whenever you change something in '3. Builder' it means you don't have to save each change manually.

  • Call Back: lets students choose a channel via which they want you to call them back. Shows in Enquiries.

  • Changes: a list of changes made to the web form,

  • Clone: used to create a new form based on an existing one.

  • Compliance Officer Comments: where your Data Protection Officer can add in their comments on the GDPR compliance level of the web form.

  • Consent: where the students give you consent to process their data.

  • Custom CSS: where you can add in your own CSS to change how your webform looks. See this article for more information.

  • Custom Fields: extra fields that you can use to capture whatever data you like. See this article for more information.

  • Data Stored In: in the step '6. Performance' this hot links to the occurrence the data gets stored in.

  • Device Preview: where you can see how your web form looks on an iPhone and an iPad in portrait and landscape orientations.

  • Discard Changes: this is used to delete your safe version of the web form.

  • DIY Forms: forms that you build yourself.

  • Documents: where you can upload and view files you want to associate with the web form. See this article for more information.

  • Download List: this downloads the list of web forms as a CSV file.

  • Embed Code: this is pasted into your own web page to display the web form.

  • Enquiry Block: used in RAP forms to send enquiry details into the ENQ app.

  • Enquiry Source: where the student tells you they heard about you: from Google, a friend, etc

  • Favicon: the tiny logo in the browser tab, found on Step 3: Builder settings cog.

  • Form Completion Rate: the number of completions as a % of views.

  • Form ID: looks like "WFM4766.01.L" Built up from the ID "WFM4766'" + Version "01" + Status Code "D": D = Draft, L = Live, A = Archived. See how to find it on your form.

  • Full Logs:  this is where you can find a list of all activities related to the form.

  • GDPR Tab: this is where you create GDPR compliance statuses.

  • Help Message: used to provide extra information for a field to assist the student in completing it.

  • Hidden Fields: this is how you can pass through one fixed value, ie: "Undergraduate" without the student having to see or select it.

  • Hide & Show Eye Icon: a quick way of making certain fields appear or disappear from your form.

  • Images: add a picture to your form, with alt tag/text, description and clickthrough URL

  • Label: this is what your field is called on the form, often phrased as a question. Students will see this when filling out the form, ie: "What is your first name?"

  • Locations: used to store where each form has been embedded on your website, ie "https://www.uni.ac.uk/prospectus".  See this article for more information.

  • Notes: keep information about the form for your colleagues to see. See this article for more information.

  • Managed Forms: old forms that are not DIY and can only be updated by Student CRM as a 'managed service'.

  • Manual Save: when you click the spinning arrows on 'Step 4: Builder'.

  • Page Title: the title used in the browser tab, found on Step 3: Builder settings cog.

  • Persona: a marketing tool to group students who share certain characteristics. See how to set these up.

  • Placeholder: text that appears inside the field on the form, used to provide guidance to a student on how to complete the field. It disappears when the student starts to type.

  • Preview: used to see what your form would look like on a range of devices.

  • Privacy Impact Assessment: is a check performed when the processing of data could result in a high risk to the rights and freedoms of a person. This helps you to manage those risks by building a compliant form.

  • Publish To Live: lock your form to further changes, so that it can be used on your website.

  • QR Code: a code that can be scanned by a mobile device to access the form. Can also be displayed on an exhibition stand so visitors can complete your form on their phones.

  • Redirect After Submitting: sends the student to another part of your website once they have completed the form, after (x) seconds of looking at your Thank You page.

  • Safe Version: a version of the form you can edit that won't impact the live version.

  • Share: you a short URL that you can send to colleagues.

  • Shortlisting Countries and Nationalities: allows you to restrict the Countries and Nationalities; instead of a list of nearly 200 options you can shortlist just the ones you want to appear on the form.

  • Show Archived: gives you the option of looking at forms that have been archived.

  • Snippet (also, Code Snippet): a piece of code that you use to embed the form on your website.

  • Spacer: used to create a space between fields. it can (optionally) contain a line (horizontal rule). 

  • Stats: shows how many times it has been viewed and completed.

  • Status: there are three statuses a form can be: draft, live and archived.

  • Submit Button: the button a student clicks when they have completed their form.

  • Tags: used to create a collection of forms that can be easily searched.

  • Templates: forms that can't be edited but can be cloned. Used as the basis for future form iterations. See this article for more information.

  • Text Block: used to place formatted text on your form.

  • 'Thank You' Page: the page that is displayed as soon as a student has submitted a form.

  • Theme: customise how the form looks; affects colours, fonts, styling and layout using CSS.

  • Topics: enables students to select from a choice of communications they wish to receive, ie: "Newsletter", "About my booking" etc.

  • Tracking Tab: where you can add your tracking codes, such as Google Analytics, Google Tag Manager, etc.

  • Type: the type of form can be either "DIY" or "Managed".

  • Use this form: clicked to make a copy of a template that you can work on without affecting the original template.

  • Validation: the message that a student sees when they have not completed a field marked as required by an asterisk after the label.

  • Web Tracking: where you select from your library of tracking codes you want to use in the form.

Did this answer your question?