Campaign Mapping and User Mapping serve different purposes:
Campaign Mapping writes Campaign and engagement information into Zoho fields.
User Mapping chooses the Owner for compatible records and activities.
Neither of these mappings widens the Integration user's permissions.
Campaign Mapping
Campaign Mapping is optional. It writes data into Contact or Lead fields, but it does not create records in the Zoho Campaigns module.
Sequence
Property | Content |
Campaign Sequence Details | Information about the sequence steps |
Campaign Engagement Status | Engagement states associated with Campaigns |
Sequence Status | Sequence states |
Campaign Reply Analysis | Information about replies |
Property | Content |
Campaign Opens | Number of opens recorded |
Campaign Clicks | Number of clicks recorded |
Campaign Open Analysis | Opens broken down by message |
Campaign Click Analysis | Clicks broken down by message |
General and Conversation Tags
You can map Campaigns, Senders and Activities through Campaign Mapping. Conversation Tags and Conversation Tags Categories use their own mappings.
If a contact takes part in several Campaigns, some fields can contain several aggregated values. Do not read them as a single overall status. Test with a contact who has been in more than one Campaign and check the format received.
Use a Text field when the content can include several values. For Picklist or MultiSelect, create and validate the options in Zoho first and use their exact values. Enginy does not explicitly create or rename picklist definitions.
User Mapping
Identities Mapping
Connects an Enginy Identity, such as an email sender or a LinkedIn profile, with an active Zoho user.
Users Mapping
Connects an Enginy user account with a Zoho user. It is used to determine the Owner in compatible operations.
Default CRM owner
Acts as the fallback Owner when no specific mapping exists.
A manual export may let you choose a different Owner. Review the value shown before confirming.
Important: Owner does not mean Integration user. Zoho still runs the requests as the user who authorized OAuth. User Mapping does not let you act with someone else's permissions.
Emails and LinkedIn messages
Enginy can associate emails with a Zoho Contact or Lead. LinkedIn messages, InMails and connection requests are also represented through the associated emails feature.
For it to work:
The contact must be linked to a Zoho Contact or Lead.
The Integration user must be able to see the record.
The authorization must still include ZohoCRM.modules.emails.ALL.
The Campaign flow must allow sending the activity.
Zoho Notes are not supported.
Note: The initial historical export does not include messages from before July 1, 2025.
Campaign Mapping can write opens and clicks into fields, but that does not replace the associated email. They are different operations.
Tasks
Compatible flows can create a Task associated with a Contact or Lead, update it, mark or reflect its status, and delete it when the corresponding operation requires it.
Zoho Setup does not show a specific Tasks panel. Enginy does not import every Task from the CRM. The refresh checks the Tasks already being tracked by Enginy.
A Task deleted directly in Zoho may not be detected automatically.
Calls
Compatible flows can log completed Calls with an inbound or outbound direction, date, duration, description and Owner.
The Call must be associated with a Contact or Lead visible to the Integration user. Campaign Mapping on its own does not create Calls.
Engagement fields
Engagement fields updates a field when Enginy logs a compatible activity. This is not the same as creating an Email, a Task or a Call.
Choose a compatible field and use a value Zoho accepts. The Engagement fields section appears in Contacts and Companies, but not in Leads.
Recommended test
Create test fields in Zoho.
Configure Campaign Mapping.
Review Identities Mapping, Users Mapping and the Default CRM owner.
Click Save Changes.
Export a test Contact or Lead.
Run only the activities your workspace actually uses.
Check the fields, the Owner and the related record in Zoho.
Review Activity > Prospecting if an error appears.
When campaign fields reach Zoho
Two things changed here recently, and they are worth stating plainly because the old behaviour caught people out.
Campaign Mapping fields do not depend on message logging
Conversations CRM Export controls whether messages are logged as activities. It does not control whether Campaign Mapping fields are written.
Important: The two used to be coupled. Turning conversation export off also stopped Sequence Status from updating, silently. They are now independent, and campaign fields mirror every send and reply whatever the message-logging setting says.
Sequence Status also syncs on enrollment, so it appears when the contact enters the campaign rather than only after the first message is logged.
Status also syncs on lifecycle changes
Status used to reach Zoho only on message events. It now also syncs when you:
Pause or resume a contact.
Block a lead.
Add contacts to a campaign, or remove them from one.
A blocked lead is reported with a blocked status rather than dropping out of the sync.
Good to know: These syncs never fail the action that triggered them. Pausing a contact still works if Zoho is unreachable, and the failure surfaces in the sync status instead.