Study first
Review the ideas behind the questions
These notes help you review a CRM form before it starts collecting leads. Focus on what each field updates, whether hidden values are safe, and what should happen after submission.
Map form fields to CRM properties
A form should collect information that can be stored and used in CRM records.
- Form fields collect visitor information and update matching CRM properties.
- The email field is required by default when form submissions create contacts.
- A visitor-facing field should be clear enough for the person submitting the form to answer accurately.
Use hidden fields for known values
Hidden fields can set values during submission without asking the visitor to type them.
- Hidden fields can set default property values during form submission.
- Hidden fields can capture URL parameters, such as UTM campaign values, into contact properties.
- A required form field cannot be set as hidden.
Plan what happens after submission
The form setup should create or update the right record and trigger the right follow-up.
- Forms can create or update CRM records from visitor submissions.
- After submission, simple workflows can send emails, notify users, or add contacts to a segment.
- If automatic contact creation is turned on, unique unknown email addresses create new contacts, while matching addresses update existing records.