Access Mapping Settings
Navigate to Integrations, then click Dotdigital.
Select Mappings.
If you have multiple Dotdigital accounts connected, use the Accounts multi-select field to choose which account(s) the mapping should apply to.
You can apply a mapping to one or several accounts at the same time.
What Donorfy Data Can Be Mapped
You can map any of the following constituent data types to Dotdigital:
Any data field available in a constituent List.
Tags, including any custom fields associated with those tags.
Channels.
Purposes.
Mappings are applied whenever data is synchronised to Dotdigital, whether:
During a bulk sync.
As part of a triggered program enrolment.
Important Notes About Mapping Behaviour
Tag Mappings
When a Tag is mapped, the tag value is synced for every Dotdigital contact.
The value will be True (contact has the Tag) or False (contact does not have the Tag).
Purpose Mappings
If a Dotdigital contact unsubscribes, mapped Purposes are set to Blocked (Red) in Donorfy.
Activities added to the constituent timeline include:
Dotdigital contact suppressed.
Dotdigital unsubscribe request.
A Purpose will show as a Marketing Preference in Dotdigital only when it is Green in Donorfy.
Amber or Red Purposes do not appear as Marketing Preferences.
This ensures marketing consent remains consistent and compliant across both systems.
Add a New Mapping
Choose the type of Donorfy data you want to map (data field, tag, channel, or purpose).
Select the corresponding destination in Dotdigital (data field or preference).
In the Accounts list, select the Dotdigital account(s) the mapping applies to.
Click Add to save the mapping.
You can create as many mappings as needed.
πNote:
Some Data Fields will be available by default, however for additional Data Fields to map your Donorfy fields to, you will need to create them. See this Dotdigital documentation on how to do that: How to create more DataFields in Dotdigital.
Creating Additional Dotdigital Data Fields
Some Dotdigital DataFields exist by default, but you may need to create new ones in Dotdigital before they appear as options for mapping.
Mapping Tags with Extra Fields
If a mapped Tag includes extra custom fields, these can also be mapped to Dotdigital.
Open the mapping for the Tag.
You will see the extra Tag fields and options to map them individually.
Each extra field must map to its own Dotdigital DataField.
You may need to create these DataFields in Dotdigital before mapping.
This allows richer segmentation by passing detailed tag-based data into Dotdigital.
β οΈImportant: To access the Dotdigital integration you'll need to raise a support ticket.
