Mailchimp Connection Error: "Failed to update data source credentials"

[Kiyan]

I'm trying to create a dashboard connected to my mailchimp account, but whenever I enter my account details I get an error message that says "failed to update data source credentials." What should I do?

[QueryWhiz]

Hi @Kiyan I know this reply is very late. Since there’s no built-in connector for Mailchimp to PBI anymore, you will have to look for another way. As a workaround, maybe you can use a 3rd party connector, it can save you a lot of time compared to other options. I've tried windsor.ai, supermetrics and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Mailchimp connector in the data sources list:

After that, you will have to first create a secret API key in your Mailchimp account and then using your credentials add your account to the platform.

Once you’ve done this, you can proceed and go to the “Preview and destination” step

There just select the fields you need. Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url. 

[v-ljerr-msft]

Hi @Kiyan,

503 – Service Unavailable is Internal Error while making calls to API/Endpoint. Similar issue was reported by others on Power BI Issues forum here. And the issue appeared to be a problem on MailChimp End. So I would suggest you contact help@mailchimp.com for better assistance on this issue. 

The team have looked into some traces provided by some other users who have the same problem. They suggest you to contact help@mailchimp.com for help, you need to work with Mailchimp support to understand why Mailchimp is returning a 500/503 for this customers data

Following is a response from MailChimp support for one of the users.

Laura (MailChimp)
Feb 10, 1:17 PM EST

Hi Mark,

Thanks for following up with this. This time I was able to get some information from the API , and it looks like the issue is actually something on our end. To be totally transparent, I am not sure exactly where the issue lies, but it appears to be related to unsubscribers of a particular campaign. I went ahead and passed these details to our developers so they can do some investigating. While I'm not able to provide a timeframe for the fix, you're welcome to check in any time with ticket ID 1668389 about our progress.

Again, thank you so much for your patience while we work on this.
Thank

Regards