Mapping defines how your CRM fields match the fields in your All Contacts database. This ensures CRM leads and contacts sync correctly into Audience Center so you can segment, personalize, score, and automate using consistent, reliable data. The steps below guide you through all parts of the mapping process, including standard fields, custom fields, push policy, and sync scheduling.
Quick Reference (Advanced Users) - Click to Expand
- Go to Settings > Data Management > Contact Mapping.
- Map CRM fields to Act-On Standard Fields first.
- Create custom fields when no standard field exists.
- Select a data type for each custom field.
- Edit push policy if you need to control write-back behaviour.
- Save your mapping and run your first CRM sync.
- 🔗 Jump to CRM-specific notesÂ
Before You Start
Confirm your CRM is connected to Act-On. Once connected, mapping controls which CRM fields flow into your All Contacts list.
Next, go to Settings > Data Management > Contact Mapping.
- Some CRM fields are mapped automatically to Act-On Standard Fields.
- Other fields may require creating custom fields in All Contacts.
Map Act-On Standard Fields
Start by mapping CRM fields to Act-On Standard Fields. These fields support key marketing tasks such as:
- Email sends and personalization
- SMS messaging
- Segmentation
- Scoring and automation
Common Standard Fields include name, company, email, phone numbers, addresses, time zone, and primary score. You can expand the full list in your account to review all available Standard Fields.
Show list of Act-On Standard Fields
- First Name
- Last Name
- Company
- Mailing Street
- Mailing City
- Mailing State/Province
- Mailing Zip/Postal Code
- Mailing Country
- Mobile Phone
- Job Title
- Time Zone
- Act-On Primary Score
Additional Standard Fields such as Industry, Segment, Subsegment, Lead Source, Status, and Product are available as needed.
Act-On provides a set of recommended mappings. Review these first. You can remove any pre-populated mapping by selecting the trash can icon.
Add Additional Standard Field Mappings
- Scroll to the first available Select Destination field.
- Select the Act-On Standard Field from the dropdown on the right.
- Choose the matching CRM field in the left column if you want it to sync.
Helpful Notes
- Depending on your CRM, you may see separate columns for Leads and Contacts or a single combined list.
- Standard Fields appear alphabetically in the dropdown.
- You do not need to map every Act-On field. You can store data only in Act-On if needed.
- Email must be mapped for CRM syncing and email sending.
- You may map one or more score fields. CRM admins can create score fields in the CRM.
Create and Map Custom Fields
Create custom Act-On fields when your CRM fields do not match an Act-On Standard Field.
- Scroll to the Act-On Custom Fields section.
- Create a custom field by entering a destination field name. These may represent:
- CRM standard fields
- CRM custom fields
- Act-On only fields
- Fields from other systems
- Select a matching CRM field if one exists.
- If no CRM equivalent exists, leave the CRM column on Select Source.
- Select a Data Type such as Text, Number, Date, Boolean, Score, Email, or Multi-Text.
Tip: Use the CRM Entities tab to preview CRM field data if unsure about data types.
Create custom fields for any values used in personalization, segmentation, or score sheets.
Set Push Policy
Push Policy defines whether Act-On can update CRM fields. By default, two-way sync is enabled:
- CRM updates sync into Act-On on every CRM sync.
- Act-On can push updates back to the CRM if allowed.
- New contacts created in Act-On are not pushed unless configured.
Edit push settings at the top of the Contact Mapping screen:
To control push settings for individual fields, use the Allow Push toggle:
Score fields always sync. Remove the mapping if you do not want scores stored in the CRM.
Save and Schedule CRM Syncs
Save Your Mapping
Select Save to confirm your mapping. Act-On will automatically create CRM-based contact segments such as:
- All Leads
- All Contacts
- Affiliated with Leads
- Affiliated with Prospects
- Affiliated with Customers
- Unaffiliated
Run and Schedule Syncs
Run your first sync by selecting Sync Now under the Sync Schedule tab.
To automate syncing, select a schedule and choose Save.
Scheduled syncs run a full sync every two weeks with incremental syncs in between. A full sync also runs whenever you add a new field to Data Management.
CRM-Specific Notes
The mapping experience differs slightly depending on your CRM. Expand the sections below for guidance specific to your integration.
Salesforce
- Leads and Contacts are separate objects. Map both columns where applicable.
- Lead conversion: When a Lead becomes a Contact, Salesforce manages inheritance. Act-On updates the Contact record during the next sync.
- Owner, Account, and Opportunity relationships sync automatically.
- Multi-select picklists sync as semicolon-delimited text. Consider using Multi-Text fields in Act-On.
- System fields cannot be updated through push.
- Validation rules may block pushes. Check Salesforce error logs if updates fail.
- Custom Salesforce objects can be imported into Act-On, but setup requires assistance from Act-On Support.
Microsoft Dynamics
- Lead and Contact fields appear separately. Map both if you qualify leads.
- Option Sets require matching text values for segmentation.
- Two-way sync: Dynamics may overwrite Act-On values during sync.
- Push limitations: System and workflow-managed fields cannot be updated.
- Lookup fields such as Owner or Account sync automatically.
- Custom entities can be imported with assistance from Act-On Support.
SugarCRM
- Email addresses often live in related records. Map the correct field.
- Multi-select lists sync as comma-separated text.
- Inactive Contacts may still sync unless excluded in SugarCRM.
- Push behaviour varies by module.
- Importing custom modules requires configuration by Act-On Support.
NetSuite
- Contacts belong to Customers (Accounts). Contact relationships sync automatically.
- Email fields may exist in alternate or sub-record fields.
- Field permissions may block push updates. Check role settings.
- Multi-select lists sync as comma-separated text.
- Date fields use SuiteScript formats. Map to the Act-On Date type.
- Subsidiary fields sync automatically.
- Role, Department, and Location fields may reject pushes.
- Inactive Contacts may still sync unless filtered in the NetSuite saved search.