Who This Is For / When to Use
This feature is for:
Admins configuring forms and lead capture.
Teams using custom fields beyond name and email.
Businesses submitting leads from external or embedded HTML forms.
Use this when you need accurate, structured capture of custom field data for automation and reporting.
Overview
Form tracking captures more than basic contact details. External Tracking can:
Detect custom fields on Kyrios forms and standard HTML forms.
Capture values with improved field-level accuracy.
Map fields reliably to existing CRM properties.
Supported Custom Field Types
Enhanced Form Tracking supports capturing the following field types:
Single-line text
Multi-line text
Dropdowns (single-select)
Dropdowns (multi-select)
Checkboxes
Radio buttons
Ratings and scores
Number fields
Monetary fields
Date picker fields
File uploads (metadata only)
Signatures (metadata only)
Source fields
Captcha fields
Boolean fields
Fields are captured only if they meet capture requirements.
Field Capture Requirements
A field is captured only when all of the following are true:
The field is visible on the form.
The field has a valid name attribute.
The field value is present in the DOM at submission time.
Not captured by default:
Hidden fields
Disabled fields
Hidden fields are captured only if explicitly configured.
Smarter Field Mapping Logic
Captured fields are mapped to CRM fields using the following priority order:
Field name matches a Kyrios property or custom field key.
Field label matches a Kyrios display name.
Field name matches the label text (case-insensitive).
If no match is found:
The field is stored as an unmapped field.
This allows admins to identify and correct mapping issues.
Data-Type Aware Storage
Captured field values are stored with awareness of their data type:
Text fields store string values.
Number and monetary fields store numeric values.
Choice-based fields retain selection structure.
Single-select and multi-select values are handled separately.
This ensures consistent usage across workflows, filters, and reporting.
File Uploads and Signatures
File uploads and signature fields:
Do not store the actual file.
Capture metadata only, such as:
File name
File type
Submission reference
This applies to both Kyrios forms and standard HTML forms.
External and Third-Party Form Support
Enhanced tracking supports standard HTML forms when:
Input values are visible in the DOM.
Fields include a valid name attribute.
Limitations:
Third-party widgets or iframe-based inputs are supported only if their values are accessible in the DOM.
Important Notes and Limitations
Hidden or disabled fields are not captured unless explicitly configured.
Iframe-based or script-rendered inputs may not be captured.
File uploads and signatures never store file contents.
FAQ
Does form tracking still capture name and email?
Yes. Name and email are still captured, along with supported custom fields.
What happens to fields that cannot be mapped?
They are stored as unmapped fields so mapping issues can be reviewed and corrected.
Are Kyrios forms and external HTML forms handled differently?
No. Both use the same enhanced detection and mapping logic.
Can hidden fields be captured?
Only if they are explicitly configured to be captured.
Are uploaded files stored in the CRM?
No. Only metadata is captured. Files are not stored.