#4236 - Followon from #4209 - Still not syncing MailChimp activity in the main pane of Sugar.
So I thought we had nailed this one down - but I am still having issues.
We sent out a mailout on the 13th of September at 9am Sydney time (2019/09/13 23:00 UTC). The list was configured correctly with WebHooks within Mailchimp.
I can see the call come into the Webhook to confirm the send at 9am in our Apache Logs. I tested the Webhook after receiving the email by updating my name via the link in the email - this pushed through to Sugar correctly.
![Sugarchimp02.png](https://www.sugaroutfitters.com/assets/img/support/SugarChimp/c9acc4e47b03ad4826313ab69fcd22fd/Sugarchimp02.png "Sugarchimp02.png")
I gave it a couple of days just in case - but I am still not seeing the Open/Click information populate in the main pane:
![Sugarchimp01.png](https://www.sugaroutfitters.com/assets/img/support/SugarChimp/c9acc4e47b03ad4826313ab69fcd22fd/Sugarchimp01.png "Sugarchimp01.png")
Is there something else I am meant to be doing?
5 years ago
Happy to help. It might help to see Sugar logs related to this process and put SugarChimp into debug mode. Can you follow the steps below and send the logs to us via email?
Send us logs via email, put in debug, send campaign, send logs.. 1. From within SugarChimp's Health Status page, right click on your browser and select "Inspect". 2. Switch to the "Console" tab, and then paste the following text: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/debug') 3. Send a test campaign and wait 15-20 minutes. 4. Navigate to the Sugar Logs (Sugar Admin > System Settings > View Logs > All) and copy/paste the logs that appear into a .txt file 5. Send those along to us at mailchimp@fanaticallabs.com
When completed, you can return the logger level to normal by pasting the following into the Console tab: SUGAR.App.api.call('get',SUGAR.App.api.buildURL('SugarChimp/setting/logger/normal'),{},{})
Please let me know if you have any trouble with the above process.
Thanks, Heidi
4 years ago
I just wanted to follow up on this ticket and close it out since we communicated a bit through email. It looks like the error that was in your logs was actually already resolved in a more recent version of SugarChimp. Getting the most recent version of SugarChimp installed appears to have resolved this issue.
Please let me know if you have any other trouble!
Thanks, Heidi