Details and field mappings available in Blastform
🎯 General principle
Each lead generated via Blastform contains a set of standardized fields.
These fields let you track, qualify and automate the processing of the data received (API, export, external integrations…).
Below you'll find the complete list of fields, what they mean and how they're used.
📑 Field table and mappings
| Field | Explanation and mappings |
|---|---|
| ID | Unique lead identifier (generated automatically by Blastform). |
| Date | Exact date and time the lead was created. |
| Status | Form status:
|
| email Check | Automatic email address verification:
|
| phoneNumberCheck | Phone verification:
|
| IP Address | IP address of the lead at the time the form was submitted. |
| source | Name of the source folder or form. |
| device | Type of device used to fill in the form (e.g. mobile, desktop, tablet). |
| callbackDate | Callback date chosen via the built-in calendar (if enabled in the form). |
| callbackTime | Callback time chosen via the built-in calendar. |
| dialling_code | International dialing code automatically entered based one the country (e.g. +1 for USA). |
| website_origin | Website or page from which the form was completed. |
Good to know
- All these fields are exportables via API, CSV, or integrations (Make, Zapier, etc.).
- JSON mapping in API connections 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 email Check and phoneNumberCheck are useful for automating validation and quality scoring.