MetaLocator lead forms typically collect a visitors name in the "From Name" field. MetaLocator can also collect a visitor’s first, middle, and last names in separate fields. This is useful when your organization needs structured name data for CRM integrations, reporting, personalization, or other downstream workflows.
In addition to collecting a visitor’s complete name in a single From Name field. You can now add any combination of the following fields:
First Name
Middle Name
Last Name
Each name component can be stored in its own custom field while MetaLocator continues to display and process the visitor’s full name as a single value where needed.
Add name fields to a lead form
To add separate name fields:
Open the interface you want to update.
Go to Leads and view the Lead Form configuration.
Click Add Field
Select one or more of the following fields from the Special Fields group:
First Name
Middle Name
Last Name
Configure the field options, including:
Label
Placeholder
Help text
Required status
Tooltip
CSS classes
Storage field
Repeat these steps for each name component you want to collect.
Remove the From Name field from the Lead Form, it will now be automatically populated from the concatenation of the First, Middle and Last name fields.
Save and publish the interface.
You do not need to add all three fields. For example, a form can collect only first and last name.
Choose where each value is stored
Each name component is stored in a selected custom field. The default Target Custom Field fields are:
First Name:
custom32Last Name:
custom33Middle Name:
custom34
You can change these defaults by updating the field’s Target Custom Field setting.
Before publishing the form, confirm that each name component uses a different custom field. Assigning multiple components to the same custom field could cause one value to overwrite another.
How the full lead name is created
When a lead is submitted, MetaLocator combines the available name components in this order:
First Name Middle Name Last Name
Empty fields are automatically omitted, and MetaLocator inserts a single space between the remaining values.
Examples:
First Name | Middle Name | Last Name | Full Lead Name |
Jane | Marie | Smith | Jane Marie Smith |
Jane |
| Smith | Jane Smith |
|
| Smith | Smith |
Jane | Q |
| Jane Q |
Leading and trailing spaces entered by the visitor are removed before the full name is assembled.
If all configured name component fields are empty, MetaLocator does not create a full name from them.
Using the existing Name field
The separate name fields are designed to work in place of the From Name field.
If the From Name field contains a value, MetaLocator uses that value as the lead’s name. If the From Name field is missing or empty, MetaLocator builds the lead’s name from the First Name, Middle Name, and Last Name fields.
This preserves compatibility with existing lead forms while allowing new forms to store names in a more structured format.
Making name fields required
Each name component can be independently marked as required.
For example, you might configure:
First Name: Required
Middle Name: Optional
Last Name: Required
Visitors will be asked to complete each required field before the form can be submitted.
Referencing in Lead Email Templates
The Lead Email Body Template can be updated to include specific references to the full, middle, first or last name as shown below. In the below example, the Lead form was configured to not use the From Name field, and instead use First, Middle and Last name using the default Target Custom Fields.
Full: {{template_item.fromname}}
First: {{template_item.leadcustom32}}
Middle: {{template_item.leadcustom34}}
Last: {{template_item.leadcustom33}}
The result in the lead body email is shown below:
