How to get the complete list of unsubscribed users?

[emr]

I need to get a list of all the users that have unsubscribed from my
list since it was first created.

I thought that "listMembers", "unsubscribed" was the way to get that
but it seems that that is only returning "recent" unsubscribes. (I'm
not sure what the definition of "recent" is)

I'm updating my list daily with new additions and the removal of
people that no longer qualify for this list. But I need to account
for people that have unsubscribed in the past. How do I get that info?

[jesse]

That works, though if you've had tons of them (or are using a small
limit) you may need to page through them:
http://apidocs.mailchimp.com/1.3/listmembers.func.php

You can also dump the whole list at once, likely much more quickly,
using the Export API :
http://apidocs.mailchimp.com/export/


jesse

[emr]

Unfortunately, it does not seem to be working. :(

We had 22 people unsubscribe yesterday, 15 the day before that, and so
on. But today's unsubscribed list only returns 13 people. Looking at
the web page it shows all 13 people have unsubscribed today.

I have tried laving the "since" parameter blank and also tried it with
'2011-01-01 00:00:00' both just return the same 13 users.

Without the list of unsubscribed users we are starting to get
complaints from people that have unsubscribed but are now being
automatically resubscribed.

Note: since the resubscription is through listBatchSubscribe it seems
that MailChimp does not see that person as unsubscribed, but rather as
NOT subscribed.

I'm worried now. :(

[jesse]

The methods I mentioned are working just fine, so you must have some
other issue with your process.

listBatchSubscribe will *not* allow you to push someone back onto a
list once they have unsubscribed.
listSubscribe *will* allow you to do that.

If the unsubscribe is being done through your site somehow and you use
the "delete" flag, all record of the subscriber will go away and you
will be able to push them back on the list using either method.

I think the best thing you can do is take a step back and look at the
various ways you may be doing things to determine where the miscue is.


jesse

[emr]

I think I found the problem. Yes it was on my end. :)

A change I made to the script was to blame. :(

Sorry about that.