I did a brief search but did not find any existing requests for handling multiple MailChimp accounts.
Problem/Motivation
I have a use case in which I need to add multiple MailChimp accounts to be used on one Drupal site. I have group A that needs to manage List A, and group B that needs to manage List B, but group B should not have access to List A.
Right now in this scenario, the lists have to be in separate MailChimp accounts. This is because within a MailChimp account, there is no way to restrict access to manage only a specific list (or segment), the existing access levels are account-wide. You either get access to all the lists, or none.
Proposed resolution
Allow adding multiple MailChimp accounts/keys. This would permit group B to have a subscription form that populates List B, and group A to have a subscription form for List A.
Comments
Comment #2
asrobComment #3
acbramley commentedThis would be great, I have a use case where a site needs to have a testing account used on some environments and a production account on others. We're using mailchimp_signup forms and It's not really feasible to override settings via the $config array in settings.php since there's a lot of data in the mergefields and mc_lists keys that would need overriding.
Comment #4
dabley commentedI'd like to do this too. I found this description of how someone approached it at Cornell University (by the looks of it on D7). I've not yet tried to implement this, but I'm building a site where this is going to be needed before long. It would be good if Mailchimp provided official support for this capability.
Comment #5
mattjones86I also have this requirement. Does anyone have a solution? As far as I can see the 8.x version does not provide the same hooks as 7.x to make this possible with a custom module.
Comment #6
xenophyle commentedThanks for submitting this ticket — and sorry we didn’t get back to you about it sooner. We are cleaning up old issues and issue for old versions and are going to close this one. If this issue is still relevant for you, please re-open it and update the “Version” field, and include any updates to the behavior you are seeing.With a smaller issue queue, we’ll have an easier time getting back to you.