The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →A form submission is not automatically a correctly populated CRM record. The form, the integration that sends or captures its data, and the destination CRM property must agree on the field’s identity, data type, and destination object. To find the break, first identify how the submission reaches your CRM; then audit each field and verify the result with controlled test submissions.
First identify how the form reaches the CRM
Before changing field names or properties, trace the actual data path for the affected form. Record its URL, form platform, CRM, integration method, and intended destination object. A native CRM form, an externally hosted form captured by tracking code, a form handler, and an API submission do not necessarily use the same mapping or validation rules.
As an Amazon Associate I earn from qualifying purchases.
- Native CRM form: A field is typically connected to a CRM property. In HubSpot, the connected property determines which CRM object stores the value. HubSpot’s form documentation explains this relationship.
- External form collected by tracking: The CRM may attempt to detect submissions and match fields automatically. HubSpot’s non-HubSpot form collection route has its own matching order, type restriction, and behavior for hidden fields.
- Form handler: The external form submits data to a configured endpoint where field names are explicitly mapped. Salesforce Account Engagement form handlers, for example, require a case-sensitive match to the source input name.
- API or other integration: Check the integration’s own field mapping, object, and validation behavior. Do not assume the rules documented for a tracked external form or a form handler apply to an API.
If you do not know which route is active, inspect the form’s integration settings and page code, then confirm where a test submission appears. Diagnose the live route—not just the form builder settings.
Recommended Free Tools
Build a field-by-field mapping inventory
For every submitted value, note what the visitor sees, what the integration sends, and where the CRM is expected to store it. Include hidden fields, consent fields, and marketing-source values; they can fail differently from visible inputs.
#1 Best Overall
| What to record | What to check |
|---|---|
| Visible label | Is the label clear, and does it describe the value being collected? |
| HTML input name | What is the input’s name attribute? This is critical for integrations that map by source field name. |
| Integration field name | What name does the collector, handler, or API actually receive? |
| CRM property | Record both the property label and internal name, where available. Similar labels can conceal different properties. |
| Property type | Does the submitted value fit the destination type—for example, text, phone, date, or a selection value? |
| Destination object | Should the value belong to a contact, lead, account, or another object supported by this integration? |
| Requirements and value source | Is the field required? Is it visible, hidden, or populated from a URL parameter or another source? |
This inventory helps distinguish a missing submission from a value that was captured but not written to the expected record or property.
Check the mapping rules for the integration path
HubSpot: non-HubSpot form collection
HubSpot says its non-HubSpot form tool tries to match submitted fields to existing contact properties automatically. It checks, in order: field name against property internal name; field label against property name; field label against property internal name; then field name against property name. Its documentation says these fields match only to single-line text contact properties. If it finds no suitable property, a value may appear in the form submission data without being stored on the contact record. See HubSpot’s field-mapping documentation.
For this path, compare the external form’s submitted names and labels against the contact property’s name and internal name, and verify that the property is single-line text. Do not assume a field has mapped just because it appears in a submission record.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Salesforce Account Engagement: form handlers
For an Account Engagement form handler, the configured External Field Name must match the external form’s HTML input name attribute exactly, including letter case. Salesforce states: “The External Field Name entered in the Account Engagement form handler must match the name= attribute of the <input> tag in the HTML of your original form.” Salesforce’s troubleshooting guide also identifies missing required fields and values that do not match the configured field type as causes of failed submissions.
Rank #2
- Pre-designed templates for both business and personal use
- 10,000 clipart images and 100 fonts
- Notes table for history and to-do items
- Sort, filter and index
- Calculation & totaling
Compare the handler configuration with the actual page markup, not just the label shown in the form editor. A visitor may see “Phone number” while the HTML input is named something like phone_number; the handler must use the source name required by the integration.
Native forms, APIs, and other integrations
For a native form, confirm which property is connected to each field and which object owns that property. HubSpot’s documentation says the connected CRM property controls the object that receives the value. For an API or third-party integration, inspect its explicit mapping and supported field types rather than borrowing assumptions from another route. A correct label alone does not establish a correct destination.
Verify the destination object and data type
Even when a field name is recognized, the destination can still be wrong. Confirm that the intended property belongs to the right CRM object and that the integration can write to it. A contact property is not interchangeable with a company or account property simply because their labels look alike.
Then compare real submitted values with the destination’s type and accepted formats. Salesforce’s troubleshooting documentation gives the example of a phone value containing punctuation failing when the handler field is configured as an incompatible numeric type. Do not “fix” such a mismatch by stripping meaningful characters unless that is appropriate for the data; correct the mapping or type configuration instead.
Review required fields, validation, and hidden values
Required fields and validation
Check both sides of a required-field rule: whether the destination or handler requires the field, and whether the active form actually sends it on every valid submission. Review allowed formats and selection values as well. Salesforce lists missing required fields and submitted values incompatible with the configured type among form-handler failure causes.
Validation is path-specific. HubSpot announced live CRM property validation for supported HubSpot forms in 2024, but that does not establish identical behavior for every external form, collection route, or integration. Confirm what the particular form and connection enforce rather than assuming a CRM rule will block invalid values before submission. Details are in the HubSpot developer changelog announcement.
Hidden fields and URL-derived values
Hidden fields can intentionally set known property values, including values supplied through URL parameters, when the form path supports that behavior. HubSpot documents this approach in its hidden-field instructions. However, HubSpot’s non-HubSpot form collection documentation says that collector does not collect hidden fields. Check which integration actually captures the submission before relying on a hidden field to carry source, consent, or other data.
For URL-derived values, verify that the parameter is present on the submitted page, uses the expected name, and is connected to a supported field or property through the active route.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Run a controlled test and inspect both records of the submission
- Choose test values that expose mapping errors. Use recognizable values for each field, including a phone number with punctuation if that is a valid expected input, and a known value for any hidden or URL-derived field.
- Submit through the real published form. A test inside a builder may not use the same page code, tracking, handler, or API path as the live form.
- Inspect the form submission details. Check which fields were captured, what names and values arrived, and whether hidden or required fields are absent.
- Inspect the resulting CRM record and object. Look for missing values, values written to the wrong property or object, unexpected overwrites, and duplicate or partial records.
- Change one mapping issue at a time, then submit again. This makes it easier to identify which correction resolved the failure instead of masking it with several simultaneous edits.
- Repeat after publishing changes. Verify the live form and retain the mapping inventory so later edits to form fields, properties, or integrations can be checked against it.
Submission details and CRM records answer different questions: the first shows what the integration captured, while the second shows what reached the destination. Comparing both is the fastest way to separate capture problems from mapping, type, or destination problems.
Salesforce handler failures need prevention and visible feedback
Salesforce says it does not retain logs of failed Account Engagement form-handler submissions, so a missing CRM record may not leave a server-side failure history to inspect. Validate field names, required values, formats, character encoding when values are appended to a handler URL, and submission method before launch; provide useful field-level error messages where possible. Salesforce’s form-handler overview also describes a hidden honeypot as one spam measure, complemented by other anti-abuse measures.
Keep the data path from silently breaking again
Store the mapping inventory with the form or integration documentation. Recheck it whenever someone changes an HTML input name, label, CRM property, property type, required-field setting, hidden field, or integration. For critical forms, make a real submission part of the change checklist and verify both submission details and the destination record before considering the update complete.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
