Using Interseller with Copper
In this guide we'll cover how to:
| Adjust the default and
individual sequence sync settings
| Disable syncing
| Enable and disable deduplication
|| Set up custom field mapping
Interseller's integration with Copper allows you to automatically sync contacts into Copper whenever they're added to a sequence on Interseller.
To connect the integration, head to the Integrations page and select Copper. You'll then be prompted to enter in your Copper email and the API Key. You can generate an API Key within your Copper account settings.
Adjusting the default sync settings
After Copper is connected to Interseller, you can choose to sync contacts as a "Lead" or "Contact". You can choose how all contacts sync over from Interseller to Copper by selecting one of the following sync options:
- Off - Contacts will not sync over to Copper
- Sync contacts when added to a sequence - Contacts will sync over to Copper when they are added to a sequence
- Sync contacts only when they reply back - Contacts will only sync over to Copper when they reply to a sequence
Adjusting the sync setting per sequence
You can override the default sync setting for each individual sequence. To adjust this setting for each sequence, open up the sequence's settings and select the sync option from the drop-down menu in the "Sync As" section.
It's important to select whether contacts sync as a "Lead" or "Contact" in the sequence first since this can't be re-synced if contacts are added first and then a sync option is selected for the sequence at a later time.
Disable syncing sequences to Copper
You can also disable syncing individual sequences over to Copper by toggling on the "Disable Sync" feature in the "Syncing" tab within the sequence's settings.
If you do not want contacts to sync over to Copper, you will need to make sure this setting is enabled first before adding contacts into the sequence.
Enable/disable deduplication for Copper
You can toggle on the "Deduplication" setting for Copper to be warned if a contact already exists in Copper. This will mark the contact with the error "Exists in Copper" if we find the same email address already exists in Copper prior to being added into Interseller.
If deduplication is turned off, then we will not warn you if the contact already exists in Copper.
Below are two common scenarios of when a new contact record will be created and when it won't be created when the contact has synced over to the integration:
- If the same email address exists in both Copper and Interseller, a duplicate contact record will not be created in Copper.
- If there are two different email addresses for the same contact (one in Copper and one in Interseller), a second contact record will be created with the second email address when they sync over from Interseller to Copper.
Custom Field Mapping
You can also customize how the field mapping from Interseller syncs over to Copper. These settings are an advanced feature so we only recommend customizing them if you're familiar with setting this up. If you need any assistance with setting up the custom field mapping, we recommend reaching out to a member of our support team.
If you see any integration errors regarding custom field mapping, feel free to get in touch with our team and they can help you out further.