You can sync a Conversion campaign with a Salesforce campaign to keep members and their statuses aligned across both platforms. This connection can be set up when creating a campaign or added later.
Sync options when creating a campaign
When creating a new campaign in Conversion, you have three options:
| Option | Description |
|---|
| No sync | The campaign exists only in Conversion. No Salesforce connection. |
| Sync to an existing Salesforce campaign | Link the Conversion campaign to a Salesforce campaign that already exists. Members from the Salesforce campaign are synced into Conversion. |
| Create a new Salesforce campaign | Conversion creates a new campaign in Salesforce and keeps the two in sync going forward. |
Syncing an existing Conversion campaign
If you created a Conversion campaign without a Salesforce connection, you can link it to a Salesforce campaign later. When you do, a two-way sync begins:
- Salesforce syncs into Conversion first. Members from the Salesforce campaign are imported into the Conversion campaign.
- Conversion syncs into Salesforce. Members and statuses from the Conversion campaign are pushed to Salesforce.
During the initial sync (and all subsequent syncs), Conversion compares the updated_at timestamp on each member record. The more recently updated value takes precedence.
Campaign type matching
When syncing with Salesforce, the campaign type in Conversion must support the same member statuses as the Salesforce campaign. This is critical for a clean sync.
If a member in the Salesforce campaign has a status that does not exist in the Conversion campaign type, that member will not be synced into Conversion.
If a member in Conversion has a status that does not exist in the Salesforce campaign, an error will be logged during sync.
Before linking a Salesforce campaign, verify that your Conversion campaign type includes all the member statuses used in Salesforce. This prevents sync gaps and errors.
Sync behavior summary
| Direction | Behavior |
|---|
| Salesforce to Conversion | Members are imported. Statuses that don’t exist in the Conversion campaign type are skipped (member is not synced). |
| Conversion to Salesforce | Members are pushed. Statuses that don’t exist in Salesforce log an error. |
| Conflict resolution | The record with the more recent updated_at timestamp wins. |
| Ongoing sync | After the initial sync, records are kept in sync on a regular cadence. |
