Connect / Constant Contact and Salesforce
+
Constant Contact and Salesforce integration
OpenContact sits between Constant Contact and Salesforce. Capture a contact once, send it to either or both, and keep opt-outs in step.
What each tool can do
| Tool | Connect with | Capabilities |
|---|---|---|
| Constant Contact | OAuth | Send, Import, Suppression |
| Salesforce | OAuth | Send, Import, Suppression |
Set it up
- Connect Constant Contact. Use OAuth. Setup guide.
- Connect Salesforce. Use OAuth. Setup guide.
- Import your Constant Contact contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add Constant Contact and Salesforce as destinations, and map the fields.
- Dry-run it. See which destinations match and which fields would be sent, then switch the rule on.
Good to know
Constant Contact
A Constant Contact destination must target a list. Custom-field mappings must point to fields that already exist in Constant Contact.
Salesforce
Salesforce requires a Last Name on new Contacts; if a contact has none, OpenContact uses the email so the record still saves. Imports read the standard Contact object.
Questions
Does OpenContact sync unsubscribes between Constant Contact and Salesforce?
Yes. When Constant Contact or Salesforce reports an unsubscribe, bounce or spam complaint, OpenContact records it and passes it to the destinations your rules select.
Do I need a CSV to move contacts between Constant Contact and Salesforce?
No. Import contacts from one tool into OpenContact, then send them to the other with a sync rule. To move a whole list, use list migration.
Does connecting Constant Contact and Salesforce cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.