First, check out PMPro-MailChimp for integrating PMPro with MailChimp.
https://github.com/strangerstudios/pmpro-mailchimp
That plugin do what you need per se, but may be useful.
Second, if people clicking on the link in the email are members, they would be able to login to view the content you are linking them to.
Are you asking about that, or are you asking for a way to maybe build a special URL that allows a page to be viewed even if you are not logged in (with the understanding that that special URL is only sent out via the mailing list)?
Does that plugin unsubscribe them from the specified list when their membership level is cancelled/removed?
johnrau, it does.
You can 0, 1, or more lists for non-members to be subscribed to. So if you chose no list there, they would be unsubscribed from everything.
Hi – I’m having a weird problem and can’t figure out if it is the pmp chimp integration or a setting over at mailchimp – hoping you can help.
When someone joins my website – they are being subscribed to the correct list. The problem is they are also being unsubscribed at mailchimp to an unrelated list. This is obviously a problem.
Hoping you can help shed light on where and why this might be occurring so I can fix it.
Thanks!
Hi JentheHumanist,
Mailchimp can tell if a member is subscribed via an API, so I think they would be able to tell if unsubscribed via an API which would help to isolate the issue.
I suggest you strike up a chat with Mailchimp support and see if they can help you isolate that, if you find out any more, please let me know.
I’m replying so I get notified of updates to this thread (we recently had to deactivate the PMPro Mailchimp plugin since it started subbing/unsubbing a little aggressively and we haven’t had time to investigate yet).
Hi essaysnark –
Can you post an issue on Github – I think a better place for this one since not in the regular PMPro plugin. Will help to get a fix in the queue.
Hi Lisa – I still haven’t had time to research the issue that we were having on this but I suspect now that it may have been a plugin conflict on our site. I’ll post on Github if it turns out to be otherwise. Thanks!
