Form Field Mismatches: Why Submitted Data Does Not Map Correctly

What’s happening

Form submissions are received, but some contact fields appear blank or contain unexpected values. This can disrupt automation and segmentation.

Why this happens

Field mismatches occur when form fields are not mapped to the correct contact fields or when workflows reference different field names.

What to check

Confirm form fields are mapped correctly, custom fields exist, and workflows reference the same field identifiers.

Make sure every form field is mapped to the correct contact field. Check that the custom fields you expect actually exist and match the field names used in your workflows. If a workflow references a different field or an old field ID, update it so everything aligns. Once the form, custom fields, and workflows use the same identifiers, submissions will populate correctly and your automations will run the way they should.

Example

If a form captures “Company Name” but the workflow checks “Business Name,” the automation condition will fail.

How to Fix

1. Open the form. Go to Fields (or Edit Fields).

2. Click each field. Confirm it’s mapped to the correct Contact Field / Custom Field.

3. Go to Settings > Custom Fields. Confirm the field exists and the type is right (text, dropdown, phone, etc.).

4. Open the workflow(s). Check every step that uses that field (If/Else, filters, tags).

5. Re-select the field from the dropdown so it points to the correct field (not an old/duplicate).

6. Submit a test form entry. Open the contact record and confirm the fields populate correctly.

When to contact Support

Contact Support if something is not functioning as intended within your plan’s defined scope.

For next steps, review the Gemini HQ Support Center and Support Policies, as support availability and response scope vary by Support Plan.