In this webinar, our experts showcase a variety of demo use cases of how different components of the...
The primary reason is because Constant Contact uses a proprietary email editor for their email campaigns. Constant Contact does not currently license out this technology.
Unfortunately, survey data is not exposed in the Constant Contact API. Once this is available in the API, PowerObjects will add the necessary functionality to support this.
Constant Contact uses the email address as an “index”. If multiple records have the same email address, then there is a risk that a Constant Contact record will get updated with the wrong data. PowerConstantContact Email Duplicates will assist you in finding accounts, contacts, and leads records with the same email address.
PowerConstantContact will only export D365 accounts, contacts, and leads that meet the following criteria:
In addition, if the record exists in Constant Contact, PowerConstantContact will not override the email permissions.
*Currently, PowerConstantContact can synch campaign or lists to a grand total of 100k records. PowerObjects is looking towards removing this constraint in future versions.
Part of the process of sending out campaigns from PowerConstantContact is that it will export data from D365 to Constant Contact. If you send out multiple campaigns, then there is a risk that the processes within Constant Contact will conflict with each other and cause unforeseen results. It is okay to simultaneously send out campaigns that have distinct contact lists.
This is most likely caused by your server-to-server app user account not having the PowerConstantContact AppUser security role. Assign that role to the account and you should be able to authenticate.
Please make sure that you have a successful connection test like the screenshot below.