Field Mapping
Field mapping tells Calimatic Connect how to translate data between your tools. Think of it like a dictionary: it converts field names from your ad platform into the field names your CRM expects.
Example
Your Facebook Lead Ad collects a field called "phone_number", but your CRM expects it as "mobile". Field mapping handles this translation automatically, so your leads always arrive in the right format.
How It Works
When a lead is sent to your CRM, Calimatic Connect:
- Takes the clean, normalized lead data (email, first name, last name, phone, etc.)
- Applies your field mapping rules to rename or transform fields
- Includes any custom form fields that match your mapping rules
- Sends the final, correctly formatted data to your CRM
Default Mappings
Calimatic Connect comes with sensible defaults that work out of the box. You only need to customize mappings if your CRM uses different field names:
| From (Lead) | To (CRM) |
|---|---|
| firstName | first_name |
| lastName | last_name |
| fullName | full_name |
| phoneNumber | phone |
| company | company |
Custom Mappings
Need different field names? You can customize mappings in the admin panel under Field Mapping for each account. Common use cases:
- Rename fields — For example, map
phoneNumbertomobile_phoneto match your CRM - Map custom form fields — Route answers from custom lead ad questions (like "What course are you interested in?") to specific CRM fields
- Include or exclude fields — Control exactly which data gets sent to your destination
Custom Fields from Lead Ads
Lead ad forms often include custom questions beyond the standard name, email, and phone fields. For example, a question like "What course are you interested in?" creates a custom field.
These custom fields are captured automatically. Use field mapping rules to route them to the correct fields in your CRM so nothing gets lost.
Setting Up Field Mapping
- Go to Field Mapping in the sidebar
- Select the account you want to configure
- Add your mapping rules: pick a source field name and set the destination field name
- Save your changes
Your new mappings take effect the next time a lead is synced. You can test them by triggering a manual CRM push for an existing lead.
Tip: Custom mappings take priority
If you create a custom mapping for a field that already has a default mapping, your custom mapping wins. This gives you full control over how data is translated.
Per-Flow Field Mapping
Flows support their own field mappings, independent of the account-level mappings described here. This lets you customize data translation for each automation without changing your global settings.