Skip to main content

CTM Web Form Field Mapping: Why Field Names Must Match Exactly Across All Forms (CRM)

Overview

If you send web form submissions to Dazos CRM through CTM — including forms built in other tools, such as Gravity Forms connected to CTM with Form Reactor — the field names your forms send must be the same on every form. Each Dazos field is mapped to one CTM field name. If different forms use different names for the same information, only the forms that use the mapped name will fill that field in Dazos.

Why Field Names Must Match

In the CTM field mapping, each Dazos field can hold only one CTM field name. Saving a new mapping for a Dazos field replaces the previous one — it does not add a second name.

For example, if Date of Birth in Dazos is mapped to Birthdate:

  • Forms that send Birthdate ✅ — the date of birth comes into Dazos.

  • Forms that send Date of Birth or DOB ❌ — that field is left empty in Dazos.

Fields That Often Differ Between Forms

  • Date of Birth — Birthdate, Date of Birth, DOB

  • Insurance Provider — Insurance Provider, Insurance, Insurance Carrier

  • Member ID / Policy Number — Member ID, Policy Number, Policy Number / Member ID

Steps

  1. Audit your forms: Review all web forms connected to CTM and list every field name used across each form. Identify fields where the same data is collected but the field name differs from form to form.

  2. Choose a single standardized name for each field: Decide on one consistent field name to use across all forms for each piece of data. For example, choose Date of Birth as the single name to use on every form, replacing all variations like Birthdate and DOB.

  3. Update your web forms: Edit each form to rename the inconsistent fields to the standardized name you selected. If you use Gravity Forms with Form Reactor, update the field labels within Gravity Forms so they match the chosen standard name exactly — including capitalization and spacing.

  4. Confirm the standardized names with your Dazos support contact: Once your forms are updated, let the Dazos team know so they can configure or verify the field mappings in Dazos CRM using the correct, standardized names.

  5. Test your forms: Submit a test entry on each updated form and confirm that all fields — including Date of Birth, Insurance Provider, and Member ID / Policy Number — appear correctly on the resulting record in Dazos.

Important Notes

  • Future submissions only. Renaming fields affects new submissions. Past submissions that used a different name are not updated.

  • Plan new forms with the same names. Keep a list of your standard field names and use it whenever you build a new form.

Related Resources

Did this answer your question?