Constant Contact
Anedot integrates with Constant Contact to sync donation and lead data, making it easy to manage contacts and campaigns across both platforms.
Constant Contact is an email marketing and online survey platform that helps organizations create and manage campaigns, grow their subscriber lists, and engage effectively with contacts.
Table of Contents
Connecting Anedot to Constant Contact
To set up the integration:
-
Go to Settings > Integrations > Directory in your Anedot account.
-
Click + New Connection in the top-right corner.
-
Select Constant Contact from the list.
-
Choose which Action Pages to sync:
-
All pages are selected by default.
-
To exclude pages, enter their Action Page IDs (comma-separated).
-
-
(Optional) Limit the connection to a specific Team.
-
(Optional) Add a List ID to send contacts to a specific Constant Contact list.
Find your List ID here. -
Click Save.
-
You'll be redirected to log in to Constant Contact and click Allow Access, this will complete the connection.
You can update Action Pages, Team scope, or credentials anytime.
Data Relays
Anedot sends data relays for both Donation Pages and Lead Pages to Constant Contact.
Relay Behavior and Data Visibility
-
Once a relay is successfully sent, contact and campaign statistics are automatically updated in Constant Contact.
-
If specific List IDs were provided during setup, new contacts will populate those lists.
-
Contact activity and metrics can be viewed in two areas:
-
Performance Tab on your Constant Contact dashboard – for overall contact and campaign stats.
-
Contacts Tab – to view contacts either in a specific list or across all lists.
-
Field Mapping
Contact Fields
Anedot Field | Constant Contact Field |
---|---|
create_source (integration-specific field, always "Account") | Contacts > Contacts > "Source" |
email "implicit" | email_address {address permission_to_send} (may correspond to Contacts > Contacts > "Email status", otherwise not visible on UI) |
first_name | Contacts > Contacts > "First name" |
last_name | Contacts > Contacts > "Last name" |
list_memberships (integration-specific field (corresponds to List ID if specified in integration setup)) | Adds contact to corresponding list in Contacts > Lists > (specific list) |
Payload Data
Request Headers
{}
Request Body (No list IDs setup/sent)
{
"last_name": "Dot",
"first_name": "Annie",
"create_source": "Account",
"email_address": {
"address": "annie@anedot.com",
"permission_to_send": "implicit"
}
}
Request Body (List IDs setup/sent)
{
"last_name": "Dot",
"first_name": "Annie",
"create_source": "Account",
"email_address": {
"address": "annie@anedot.com",
"permission_to_send": "implicit"
"list_memberships": ["9938af78-151f-11ee-9414-fa163ed70180"]
}
}
Response Body (Success, No list IDs setup/sent)
{
"last_name": "Dot",
"contact_id": "b8976f38-2ee5-11ed-b1b3-fa163e3c5d75",
"created_at": "2022-09-07T19:46:09Z",
"first_name": "Annie",
"updated_at": "2022-09-07T19:46:09Z",
"create_source": "Account",
"email_address": {
"address": "annie@anedot.com",
"created_at": "2022-09-07T19:46:09Z",
"updated_at": "2022-09-07T19:46:09Z",
"opt_in_date": "2022-09-07T19:46:09+00:00",
"opt_in_source": "Account",
"confirm_status": "off",
"permission_to_send": "implicit"
}
}
Response Body (Success, List ID setup/sent)
{
"last_name": "Dot",
"contact_id": "b8976f38-2ee5-11ed-b1b3-fa163e3c5d75",
"created_at": "2022-09-07T19:46:09Z",
"first_name": "Annie",
"updated_at": "2022-09-07T19:46:09Z",
"create_source": "Account",
"email_address": {
"address": "annie@anedot.com",
"created_at": "2022-09-07T19:46:09Z",
"updated_at": "2022-09-07T19:46:09Z",
"opt_in_date": "2022-09-07T19:46:09+00:00",
"opt_in_source": "Account",
"confirm_status": "off",
"permission_to_send": "implicit"
},
"list_memberships": ["9938af78-151f-11ee-9414-fa163ed70180"]
}
Response Body (Failure)
[{
"errorKey": "contacts.api.validation.error",
"errorMessage": "email_address[address] is empty"
}]
or
[{
"errorKey": "contacts.api.conflict",
"errorMessage": "Validation failed: Email already exists for contact fd9000d8-a587-11ec-a30f-fa163e7b09ec"
}]
Response Status (Success)
201
Response Status (Failure)
401