Now the CRM maps the contact types and the standard fields for you, shows you exactly what it did, and lets you choose which record types sync — one at a time.
Contents
1. Before You Start
2. Open the iCampaign Mapping Screen
3. Choose Which Records Sync
4. Map the Contact Types
5. Map the Fields
6. Reading the Mapped Data Tables
7. Frequently Asked Questions
1. Before You Start
You will need:
An administrator login for the CRM.
The iCampaign integration already activated for this instance, with the iCampaign instance address saved.
A reachable iCampaign subscriber — the CRM reads the available contact types and fields from it. If it cannot be reached, the CRM tells you so instead of guessing.
Access requirements: this screen lives under Settings and is available to administrators only.
If you cannot see the iCampaign mapping screen at all, or the buttons described below are missing, the integration has not been activated for your instance yet — contact Dazos support to enable it.
2. Open the iCampaign Mapping Screen
From the CRM, navigate to Settings → Configuration → CRM iCampaign Mapping. The screen has several sections, top to bottom:
Section | What it is for |
Subscriber sync | Choose whether records are sent to iCampaign, and which record types |
CRM iCampaign Contact Type Mapping | Match each CRM module to the contact type iCampaign uses for it |
CRM iCampaign Mapping Settings | Match individual CRM fields to iCampaign fields |
Contact Type Mapped Data / Mapped Fields | The tables showing what is currently mapped |
3. Choose Which Records Sync
Switch on Enable iCampaign subscriber sync to turn sync on at all. Underneath it there is one switch per record type — Leads, Referral Sources, Accounts, Intake Opportunities, Referral Contacts and Donors.
Switch on only the record types this client should send. Everything you leave off stays off.
Control | Purpose |
Enable iCampaign subscriber sync | The master switch. Turning it off stops every record type at once |
Record type switches | Turn one record type on or off without touching the others |
Tip: You can pick the record types before switching the master on. While the master is off your choices are just choices — nothing is sent. When you switch the master on, only the record types you picked start syncing. You no longer have to turn everything on and then go back and switch things off.
Two things worth knowing:
Turning a record type off stops future syncing for it, including the bulk Sync Records action. It does not remove records already sent to iCampaign, and from then on deleting one of those records in the CRM will no longer unsubscribe it in iCampaign.
If a record type shows a Custom workflow active badge, someone has built their own workflow for it. That workflow keeps sending regardless of this switch, and has to be turned off under Settings → Workflows.
4. Map the Contact Types
In the CRM iCampaign Contact Type Mapping section, click Default mapping at the top right.
The CRM proposes the contact type each module normally uses in iCampaign — for example Leads to Lead , Referral Sources to Referral Source , Users to Staff . It only proposes contact types your iCampaign subscriber actually offers; anything it does not offer is listed under Not proposed with the reason.
Review the list, untick anything you do not want, and click Save selected. Nothing is saved until you do.
Important: Intake Opportunities is intentionally not mapped to a contact type. You will see it listed under Not proposed as "Not mapped by design". That is expected.
5. Map the Fields
In the CRM iCampaign Mapping Settings section, click Auto map fields at the top right.
The window lists every field pairing the CRM already knows how to make, already ticked. Each iCampaign field is shown the way it reads plus its system name in brackets — for example Last Name(last_name) — so you can find it on either side.
Control | Purpose |
Search box | Filter the list by module, CRM field or iCampaign field. Filtering only hides rows — it never unticks them |
Header tickbox | Tick or untick everything currently shown |
Not proposed | Expand to see what was skipped and why |
Save selected | Save the ticked rows. Nothing is written until you click this |
Rows that change an existing mapping
Some rows carry a Changes current mapping badge and are deliberately left unticked. That means the iCampaign field is already receiving a different CRM field today, and the row tells you which one.
Tick one of these only if you genuinely want to change what gets sent. Leaving it unticked is the safe choice and changes nothing.
Tip: You can run Auto map fields and Default mapping as often as you like. Neither ever creates the same mapping twice, and neither ever changes or removes a mapping you made by hand.
6. Reading the Mapped Data Tables
Both Contact Type Mapped Data and Mapped Fields now have a Source column:
Badge | Meaning |
Auto | The CRM created this mapping for you |
Manual | A person created this mapping through the form |
Everything behaves the same way regardless of the badge — you can edit or remove an automatic mapping exactly like one you made yourself. Use the bin icon at the start of a row to remove it; the row disappears straight away without reloading the page.
7. Frequently Asked Questions
Q: I clicked the button and it said everything is already mapped. Did it do anything? No, and that is the correct result. The CRM never creates a mapping that already exists. If everything it knows about is mapped, it tells you so and offers nothing to save.
Q: What happens if iCampaign cannot be reached? The window says it could not read the iCampaign field list and offers nothing to save. It will not show you an empty table and let you wonder. Check the iCampaign address and that the integration is active, then try again.
Q: Will automatic mapping overwrite the mappings I made by hand? No. A field that already has a mapping is skipped, and the reason is shown under Not proposed. Your own mappings are never changed or removed.
Q: Why is one of my fields listed as "No matching field in the CRM"? The CRM knows a pairing for that iCampaign field, but this instance does not have the CRM field it expects — usually because it was renamed or never created. Map it by hand using the form above the table.
Q: I turned a record type off. Why are records still appearing in iCampaign? Check whether that record type shows a Custom workflow active badge. A workflow someone built by hand keeps sending regardless of the switch, and has to be turned off under Settings → Workflows.
Q: Does turning a record type off delete anything from iCampaign? No. It stops future syncing only. Records already sent stay in iCampaign, and from then on deleting one in the CRM will no longer unsubscribe it there.
Q: Can I undo an automatic mapping? Yes — remove the row with the bin icon, exactly as you would a manual one.
Need Help?
If you run into issues:
1. Open the Auto map fields window and expand Not proposed — it usually explains why something you expected is missing.
2. Confirm the iCampaign integration is active and its address is correct, then try the button again. 3. Contact Dazos support with what you saw on screen and reference CRM-3885.