Enginy can store Campaign and conversation data in TribeCRM.

Conversations are logged as Activities. They do not become Notes.

When a conversation is exported

Each Campaign's configuration can block the export, always allow it, or wait for the Contact to reply.

When the reply condition is used, Enginy does not export the Contact or the conversation until it detects a qualifying reply.

The Contact has to exist in TribeCRM and Enginy has to know its CRM ID before it can create the Activity.

Properties available in Campaign Mapping

You can match Campaign data to TribeCRM fields.

Group	Properties
Sequence	Campaign Sequence Details, Campaign Engagement Status, Sequence Status, Campaign Reply Analysis
Email	Campaign Opens, Campaign Clicks, Campaign Open Analysis, Campaign Click Analysis
General	Campaign, Senders, Activities
Conversation Tags	Conversation Tags, Conversation Tags Categories

Some properties hold several comma-separated values when the Contact has taken part in more than one Campaign.

Set the destination field in Campaign Mapping and test the result with one Contact before using it across all your Campaigns.

How messages are stored

Message in Enginy	Object in TribeCRM
Email sent or replied to	`Activity_Email`
LinkedIn	`Activity_LinkedInMessage`
InMail	`Activity_LinkedInMessage`
Connection message	`Activity_LinkedInMessage`
Other supported message	`Activity`

Emails are created as closed Activities and use the phase matching sent or replied.

LinkedIn requirement

The environment has to include the module and the Activity_LinkedInMessage type.

If it is not available, Sync Configuration shows a warning. Click Open Account Settings, enable the module and come back to Enginy. Then click Recheck.

Without that type, Enginy cannot log LinkedIn, InMail or connection messages. Other records in the same process can still go through.

Configure Campaign Mapping

Open Integrations.
Find TribeCRM and click Configure.
Go to Campaign Mapping.
Choose the Campaign property.
Select the TribeCRM field.
Save with Save Changes.
Test with a Contact that already has a CRM ID.
Check the Activity and the fields in TribeCRM.

Campaign Mapping does not switch on a general sync between both systems.

Identities, Users and owners

Setting	Used for
`Identities Mapping`	Matches the profile running a Campaign with a TribeCRM Employee
`Users Mapping`	Matches an Enginy user with a TribeCRM user
`Default CRM owner`	Used when there is no specific match

Depending on the flow, Enginy uses those IDs in TribeCRM fields:

AccountManager for the owner of Contacts and Organizations.
Creator when creating certain records.
Employee to attribute LinkedIn messages.
Assignee for a Task's owner.

Note: The mapped user does not contribute their permissions. TribeCRM applies the permissions of the user who authorised OAuth.

Why an Activity might be missing

Check:

The Contact has a CRM ID.
The Campaign allows the conversation to be exported.
The mapping is saved.
The OAuth user can create Activities.
User Mapping or Identities Mapping has the matches it needs.
Activity_LinkedInMessage exists if this is LinkedIn.
TribeCRM has not applied an API limit.

One message failing does not mean they all fail. Review the Contact and the report before retrying.

Current limits

Conversations are not stored as Notes.
Enginy does not export messages for Contacts without a CRM ID.
There is no continuous bi-sync of conversations.
Activities created directly in TribeCRM do not automatically appear as new conversations in Enginy.
A conversation can sync partially.

When campaign fields reach TribeCRM

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

The Campaign setting that controls conversation export decides 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 TribeCRM 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 TribeCRM is unreachable, and the failure surfaces in the sync status instead.

Campaign Mapping, conversations, Activities and Owners in TribeCRM