Campaign member sync, and opportunities
Campaign members now sync in both directions with Salesforce. A status change made in either system appears in the other on the next sync, so nobody has to export a list to reconcile the two.
Bidirectional campaign member sync
Creates, updates, and deletes all move through the syncer. Campaign member fields are available in Liquid, so an email can personalize on where someone sits in a campaign.
Linking an existing Salesforce campaign to a Conversion campaign preserves the membership already on it. You no longer rebuild it from scratch.
Opportunities across the data model
Opportunities and opportunity contact roles are real objects now, with their own schema, default variables, and relationship endpoints to contacts and companies. Segmentation and reporting can reference pipeline directly rather than through a workaround.
Deletions propagate. An opportunity removed in Salesforce is removed in Conversion.
Sync logs
Every sync run now writes a log you can open. When a record fails, the reason is on the record instead of somewhere in a batch summary.
Improvements
- Email One-click unsubscribe is on for every workspace, and the flag that gated it is gone.
- Email Operational email can send without an unsubscribe link, which is what compliance teams expect for transactional messages.
- Data Model Communication limits apply per recipient email rather than per contact record.
- Campaigns Duplicating a campaign brings its assets with it.
- Admin Sync settings respect workspace permissions.
- Audiences Statement evaluation moved off the legacy engine, and the old path is deprecated.
Fixes
- Campaigns Deleting a campaign member uses the member id rather than matching on contact, so the wrong record is no longer removed when a contact appears twice.
- CRM Sync Contacts missing fields Salesforce requires are filtered out before the create attempt instead of failing the batch.
- CRM Sync All fields are written to the field map when unmarshalling contacts, leads, and accounts.