A recognition table covering the default field names of Meta lead forms, Google lead forms and the common website form builders — full_name, your_name, email_address, mobile_number, postal_code and dozens more, plus Google's upper-case column ids. Explicit mapping rows always win. Anything unmapped becomes an answer on the card by default; you can choose to drop unmapped fields instead.
Also called: map form fields · my form field names are weird · custom form questions
- 1Order of resolution: explicit mapping row, then attribution keys, then auto-recognition, then the unmapped policy
- 2Budget mapping extracts a number and also keeps the raw phrasing — '$50k-$100k' stays visible as context
- 3Unmapped keys are title-cased into readable question labels
- 4Missing names fall back to first plus last, then email, then phone
Every form provider names its fields differently, so connecting a new lead source meant an admin sitting down to map each one before a single lead could land. Common names are now recognised with no configuration at all. Anything that does not map is kept as a question and answer on the card rather than discarded, because the unmapped fields are usually where the context lives — a budget given as a range says something a single number cannot. Provider field names are preserved exactly as they arrived, so the mapping screen and the debugger both speak the same language the provider does.
- Every new form requiring manual field configuration
- Unmapped questions silently discarded
- Range answers reduced to a meaningless number
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →