Details and field mappings available in Blastform
🎯 General principle
Each lead generated through Blastform includes a set of standardized fields.
These fields help you track, qualify and automate the processing of incoming data (API, export, external integrations, etc.).
Below is a complete list of fields, along with their meanings and uses.
📑 Table of fields and mappings
| Field | Explanation and mappings |
|---|---|
| ID | Unique lead ID (automatically generated by Blastform). |
| Date | Exact date and time of lead creation. |
| Status | Form status:
|
| emailCheck | Automatic email address verification:
|
| phoneNumberCheck | Phone verification:
|
| ipAddress | Lead's IP address at the time of form submission. |
| source | Name of original file or form. |
| device | Type of device used to submit the form (e.g. mobile, desktop, tablet). |
| callbackDate | Reminder date selected via the integrated calendar (if enabled in form). |
| callbackTime | Reminder time selected via the integrated calendar. |
| dialing_code | International dialing code automatically entered based one the country (e.g. +1 for USA). |
| website_origin | Website or page where the form was submitted. |
Good to know
- All these fields can be exported via API, CSV, or integrations (Make, Zapier, etc.).
- In API connections, the JSON mapping uses these names exactly (case-sensitive).
- You can add your own custom fields from the form editor.
🛠️ Practical tips
✅ Always use the exact names to avoid integration errors.
✅ Only check the dynamic fields (callbackDate, callbackTime) if your form includes a calendar.
✅ The fields emailCheck and phoneNumberCheck are useful for automating validation and quality scoring.
