Need help with custom API query

[jessem]

Greetings,

I'm trying to get retreive my list growth data from MailChimp. The standard MailChimp content pack unfortunately doesn't give me what I need. Instead, I'd like to create a custom list growth query using MailChimp's API. Documentation found here:

http://developer.mailchimp.com/documentation/mailchimp/reference/lists/growth-history/#read-get_list...

I should be okay once I get an idea of which path I need to take to implement this, I'm just not sure where to even begin in PBI Desktop.  

Forgive me if this has already been explained, I've looked but could not find the answer (maybe I'm looking in the wrong spot).

Thanks!

[ReportGuru]

Hi @jessem I know this reply is very late. Since the Mailchimp service pack was deprecated and also the desktop coonnector is not available anymore, you would 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 (which doesn't have PBI as a destination, so you first have to export to Google Sheets and then export to PBI) and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options

[TPalmer · Accepted solution]

Hi there - the MailChimp connector in the Desktop also offers functions that can allow you to interact with the MailChimp API directly. We included those functions knowing that the tables we offered in the navigation pane were only a subset.

The documenation for these functions is actively being improved, but they take the subset of the API path as you saw in the Mailchimp documention. Try something like this (replacing the list ID):

= MailChimp.Instance("lists/{list-id}/growth-history")

The function will return the raw result which you can open and parse into a table. Using your example also showed a bug in our MailChimp.Collections function which is the preferred function for this operation (Instance is a raw single page vs. Collections will actually page through all the data into a single table). We'll work on fixing that bug in a future update.

Hope that helps!

[leeann_g]

Can we do the same with other Connectors (like for interacting with the Adobe Reporting API and modifying the connector dataset)?

[jessem]

Awesome, thanks!