Salesforce Marketing Cloud integration.

Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the Salesforce Marketing Cloud records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.

Resolve the organization relationship and any owner or consent references required by the destination.

Test an email change, two records sharing an email, and a person associated with multiple organizations. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window.

Start with one workflow and a sample record from Contacts / Subscribers and Tracking Events. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.