Connect / GetResponse and Copper
+
Connect GetResponse and Copper
OpenContact sits between GetResponse and Copper. 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 |
|---|---|---|
| GetResponse | API key | Send, Import, Suppression |
| Copper | API key + email | Send, Import, Suppression |
Set it up
- Connect GetResponse. Use API key. Setup guide.
- Connect Copper. Use API key + email. Setup guide.
- Import your GetResponse contacts into OpenContact, so there is one record per person.
- Create a sync rule. Pick a trigger, add GetResponse and Copper 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
GetResponse
A GetResponse destination must target a campaign. GetResponse stores the standard name as one full-name value; OpenContact combines first and last name when sending and splits the value when importing.
Copper
Copper has no marketing lists or unsubscribe field, so OpenContact exposes your whole people book as one importable source and marks suppressed contacts with an unsubscribed tag.
Questions
Does OpenContact sync unsubscribes between GetResponse and Copper?
Yes. When GetResponse or Copper 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 GetResponse and Copper?
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 GetResponse and Copper cost extra?
Both tools bill you separately. OpenContact plans are priced by limits, and every plan includes all integrations. See pricing.
Related
GetResponse integration · Copper integration · Sync rules · Suppression sync · All pairings