Note: Enginy can send Campaign information into a Person's attributes and save messages as Notes in Attio. These are two different features and they are configured separately.
What controls a Campaign's sync
In the Campaign settings you will find two options:
Contacts CRM Sync decides when to create or update the Person in Attio.
Conversations CRM Sync decides when to send the conversation.
Depending on the option chosen, you can sync never, always, or only when a contact replies. The reply option appears as Only when a contact replies.
Important: To save a conversation, the Person must exist in Attio and Enginy must know their CRM identifier. If the contact has not been exported yet, the Note has no destination record.
Configuring Campaign Mapping
Campaign Mapping lets you write activity data into People attributes. It is useful for seeing the sales context without leaving Attio.
Go to Integrations.
Open Attio and click
Configure.Go to Campaign Mapping.
Turn on only the data you need.
Select the Attio attribute that will receive each value.
Click
Save Changes.Test the configuration with a test Campaign and Person.
The available fields are grouped like this:
Group | Data available |
Sequence | Sequence details, engagement status, sequence status and reply analysis. |
Opens, clicks and their analyses. | |
General | Campaigns, senders and activities. |
Conversation Tags | Conversation tags and their categories. |
For Campaigns and Senders you can keep the aggregated history or turn on the overwrite option to store only the most recent value.
How messages are stored
Each synced message is created as a plain text Note on the corresponding Person. The title helps you recognize the channel and the sender:
For email, it uses the subject when available.
For LinkedIn, it identifies the channel and who sent the message.
When the message is part of a sequence, it can include its position.
Notes are not native Attio activities. They do not create calls, emails, meetings or timeline events as separate objects. They also do not support rich formatting from this integration.
Campaign Mapping and Notes are not the same
Feature | Where it appears in Attio | What it is for |
Campaign Mapping | In Person attributes | Checking statuses, metrics, Campaigns, senders and tags. |
Conversation sync | As Person Notes | Reading the content of messages sent and received. |
You can use one feature without the other. For example, store metrics in attributes without copying conversations, or send Notes without mapping all the Campaign data.
What happens with Owner and User Mapping
Attio needs a workspace member for User type attributes, but Enginy's generic Owner selector does not change the Person record's owner and does not attribute the Notes to another user. The authorization still belongs to the account that connected the integration.
Tasks in Attio
Even though the general CRM configuration may show a Tasks section, the current Attio connection does not request the specific scope needed to work with tasks. For that reason you should not count on Task creation or syncing in this integration.
Recommended test
Before turning on syncing for a large Campaign:
Create a test Person in Attio.
Confirm that Enginy recognizes it through matching.
Map one or two simple text attributes.
Run a test Campaign.
Check the record, the attributes and the Notes.
Adjust the configuration before widening its use.
That way you can quickly tell whether a problem comes from matching, from Field Mapping or from conversation syncing.
When campaign fields reach Attio
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 saved as Notes. 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 Attio 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 Attio is unreachable, and the failure surfaces in the sync status instead.