Hey there, thanks for stopping by to check out how to map Constant Contact custom fields in your integration while using the EventSpot feature "Sync Constant Contact Events " in Step 1?
SyncApps currently supports Constant Contact Version 2 and Version 3 API.
But if you're using both Custom Fields and EventSpot then please select Version 2 API first in Step 2 of the Sync Profile as Version 3 API does not support EventSpot yet.
Basic Fields Premapped
Additional field mapping is optional. Basic Contact fields such as all below are already mapped for you;
- Email address
- Company name
The phone number is pre-mapped. If having multiple phone numbers in a CRM record then only the number under "Phone" will be synced to Constant Contact "Work Phone" field.
If the "Phone" number field is left blank even if other phone numbers are filled in then no phone number will be synced to Constant Contact "Work Phone".
What we’ve done is put together an easy-to-follow step-by-step guide that will ultimately enable you to sort out tricky field mapping issues, such as:
- Which custom fields specifically in Constant Contact can be mapped in Step 4 of your Sync Profile
- Which custom fields created in Constant Contact do not show up over in SyncApps Constant Contact Field list even after refreshing fields.
- How to see the Constant Contact custom fields in the additional field mapping while trying to map custom fields in both systems. This could be giving you problems even after refreshing so that the newly created fields do not show up.
- What to do when Fields are being displayed with Standard Naming in Cazoomi (custom_field_1-- custom_field_15) but not with the name you used to create in Constant Contact.
- How to import Custom Fields from the signup form, back to the Contact/Account/Lead/Targets
- What to do when a Custom Date Field you named "Subscribed Date" in Constant Contact is not available in the Cazoomi Field Mapping Section to map it to Salesforce.
- Please do not rename or relabel the fields in Constant Contact (For Version 2 API) as it will recreate a new field in Constant Contact and sync to those new fields instead of the relabeled ones as this is one of the Constant Contact Limitations.
Let’s start off by looking at the pre-mapped fields from to Constant Contact below shown in blue. The red #7 field is how Custom Fields 1-15 will be shown when designated which we will explain coming up.
For Custom Fields let’s start off with mapping back Bounce Reason and Bounce Date to CRM.
Are you trying to write back the bounce fields from Constant Contact to CRM?
Constant Contact does not explicitly have a "Hard Bounce" field. They instead have a "Bounce Reason" field which is populated with both soft and hard bounces. To map this field head to Step 4 and use a Text Field Type. For Bounce Date use a Data Type field.
Note: Sync Campaign Response must be selected in Step 1 in order for these fields to be available for Field Mapping and to be synced back to CRM.
If you run into issues be sure to check the field type in CRM and if using an existing field then try changing your field on the CRM side to a Text field to capture "Bounce Reason" which is text type in Constant Contact and Bounce Date is a Date field type in CRM.
Do you need to use a Custom Unsubscribe field in CRM?
If you do, then that’s fine, just use our Add-On just for this feature in your Add-Ons tab, and once subscribed it will instantly turn this feature on to map in Step 4 today. Simple, right?
It gets even better.
Check this out.
You can also choose to do Additional field mapping or not.
We’ve made it easy for you by mapping the Basic Contact fields including Email Address, Name, Address, Company Name, and Phone.
This makes it convenient.
Here’s another interesting bit.
Do you wish to use Custom Fields in Constant Contact?
No worries, we’ve got you covered! Listen to this - 15 custom fields for you to choose from! Now that’s a whole lot to choose from, which is great.
However, if you choose to add a custom field in Constant Contact, it will not add any functionality to the 15 already available Custom Fields that the current Constant Contact API allows.
In Constant Contact, only 15 Custom Fields are allowed when using their V2 API.
However, it’s not all gloom and doom for those willing to add since you can map the 15 fields to match your fields in CRM.
In order to get this rolling, this is what you need to do:
Here are the steps:
- Add a new Custom Field and name it Custom Field 1
- Add a new Custom Field and name it Custom Field 2 and continue as needed
When doing all this, make sure you jot each field label (COMM STEM = Custom Field 1) down to be used in your Sync Profile.
This will help map the 1-15 custom fields available to your CRM field(s). You will need them as Constant Contact only supports the naming of custom fields 1-15 as shown above.
Check out our Subscriber’s Story below on how SyncApps helped them save time!
Did we answer your question? I hope we did.
Have you tried setting up your own Sync Profile with SyncApps?
Let us know if you hit any more snags by emailing us at firstname.lastname@example.org. We are ready 24/7 to answer all your questions.