Sage CRM 2020 R2: Mailchimp Logs and Settings

The mailchimp configuration settings available in the meta data table custom_SysParams.

You can inspect these using the query

select * from Custom_SysParams where Parm_Name like '%MailChimp%'

The integration is carried out by the main CRM webapp. 

The webapp logging levels for the MailChimp Integration are controlled in logging file:

In Sage CRM 2020 R2 the location and name of the file has changed.

In Sage CRM 2020 R1 and earlier

To control logging on the Sage CRM server you would need to locate and open the following file:

<Sage CRM installation folder>\tomcat\webapps\<InstallName>j\WEB-INF\log4j.xml

where

<Sage CRM installation folder> is the folder you specified when installing Sage CRM. By default, this is %ProgramFiles(x86)%\Sage\CRM\CRM.
<InstallName> is the Sage CRM installation name. By default, this is CRM.

Example:

%ProgramFiles(x86)%\Sage\CRM\CRM\tomcat\webapps\crmj\WEB-INF\log4j.xml

In Sage CRM 2020 R2 onwards

On the same Sage CRM server file has changed location and name

<Sage CRM installation folder>\tomcat\webapps\<InstallName>j\WEB-INF\classes\log4j2.xml

Example:

%ProgramFiles(x86)%\Sage\CRM\CRM\tomcat\webapps\crmj\WEB-INF\classes\log4j2.xml

<logger name="com.sage.crm.mailchimp" additivity="false" level="ERROR">
<appender-ref ref="mailchimp" />
</logger>

The logs should be output to the Logs\mailchimp.log file

C:\Program Files (x86)\Sage\CRM\CRM\Logs

Fiddler can be used to monitor the traffic to the Mailchimp server using Mailchimp's RESTful API.

The information is passed between Sage CRM and Mailchimp in JSON format instead of XML. The messages will have the typical structure.

Request body: {"apikey":"73e0b89dc278f402dd06c253ad547915-us9"}
Response body: {"msg":"Everything's Chimpy!"}