Skip to main content

Enhanced Form Tracking With Custom Field Capture and Smarter Mapping

· 3 min read
SMBcrm Team
SMBcrm Team
Product Team

Overview​

Form tracking in SMBcrm now captures more than just basic contact details like name and email.

External tracking has been enhanced to detect, capture, and map custom fields from both SMBcrm-hosted forms and standard HTML forms, with improved field-level accuracy. This helps you collect the information you actually ask for on your forms and use it more reliably in follow-ups and reporting.

What’s New: Custom Field Capture​

You can now capture a wider range of custom field types, including:

  • Single-line and multi-line text fields
  • Dropdowns (single-select and multi-select)
  • Checkboxes and radio buttons
  • Ratings and scores
  • Number, monetary, and date picker fields
  • File uploads and signatures (metadata only)
  • Source, captcha, and boolean fields

When fields are captured​

Fields are captured only when they:

  • Are visible on the form
  • Have a valid name attribute

This keeps data cleaner and reduces the chance of collecting unintended or non-user-entered values.

Smarter Field Mapping​

Captured custom fields are mapped using a consistent priority order:

  • Field name matches an existing system property or a custom field key
  • Field label matches a custom field display name
  • Field name matches label text (case-insensitive)

If no match is found, the field is stored as unmapped_field, making it easier to spot which fields need attention so your data lands where you expect.

Better Data Handling for More Reliable Automation​

Captured fields are stored with awareness of their data type, including:

  • Text, number, and choice-based fields
  • Single-select vs multi-select values
  • Metadata-only handling for file uploads and signatures

This helps ensure your downstream automations and workflows can use the captured data consistently. If you’re using automations to route leads, personalize messages, or qualify requests, cleaner field capture typically means fewer edge cases and manual fixes.

If you want help applying captured fields in automation, visit our Support page.

Important Notes​

  • Hidden or disabled fields are not captured (unless explicitly configured)
  • Third-party widgets or iframe-based inputs are supported only if the value is visible in the DOM and has a name attribute
  • File uploads and signatures capture metadata only; files are not stored

Next Steps​

  • Review your public-facing forms to confirm key fields are visible and use meaningful name attributes
  • Submit a test entry and confirm captured fields are mapping correctly
  • If you see unmapped_field, update field names/labels to align with your CRM field setup

Need a second set of eyes? Request a demo or reach out via our Contact Us page.