#4289 - Mailchimp activity module reports 0 activity
The mailchimp activity module is not reporting any activity yet I have mailchimp activity set to show up on my dashboard and I am seeing it there.
The mailchimp activity module is not reporting any activity yet I have mailchimp activity set to show up on my dashboard and I am seeing it there.
4 years ago
Thanks for reaching out. I'm curious if just activities aren't coming through, or if all syncing from Mailchimp isn't working as it should. Can you make a change to an active record, such as adding a character to record's first name in Mailchimp, and let me know if that change is reflected in Sugar?
Secondly, can you confirm the webhook on Mailchimp matches the one on Sugar? You can see your Sugar webhook by navigating to the Health Status page. To see the webhook in Mailchimp, you can follow the directions below:
This webhook should be active and should exactly match the webhook that appears in SugarChimp's Health Status page within your CRM.
Thanks, Heidi
4 years ago
Yes the change was reflected in Sugar and the webhooks match. Activities are coming thru on my dashboard when I create them via a Sugar Dashlet they just don't appear in the Mailchimp Activities tab on the contacts page or when I click the Mailthimp Activities on the Admin page
4 years ago
Thanks for this insight. I had reviewed the logs from your other ticket to see if there was an issue there, and I'm not seeing anything obvious. To confirm, are these individual campaigns or are they opens/clicks from automated campaigns?
Can you follow the steps below and let me know what you see?
If you prefer, you can also schedule some time for us to look at it together:
https://calendly.com/fanaticallabs_support/sugarchimp-support-meeting
Thanks! Heidi
4 years ago
Just wanted to quickly update this ticket with the information we chatted about through email and during our call:
Based on what we saw on the call, it looks like the activities are being received by Sugar, but aren't displaying or syncing to the record itself. I chatted with Jon, our developer, with what we found and he says it sounds like there's an internal CRM process that's conflicting with our ability to save the data to the Sugar record. Looking through the log and seeing those BallAPI errors over and over, I'm inclined to think that error may be affecting many areas of the CRM unknowingly. With this knowledge, can you let us know when that BallAPI issue is resolved and we can take another look and troubleshoot further, if needed?
Thanks!