CiviCRM Community Forums (archive)

Just want to make sure I have this clear:

Scenario 1: A user receives a newsletter and chooses to unsubscribe from that newsletter. They click the unsubscribe link and are removed from the group. There is no flag set on their account that they did this, and if a site administrator adds them back to the group, they will get the emails again even though they unsubscribed.

Scenario 2: A user receives a newsletter and chooses to opt-out from everything at the domain. They click the opt-out link and are removed from all groups that are mailing lists. They also get the 'User Opt Out' checkbox checked. This will prevent any mailing list emails from going to them even if they are added back into the groups? Does the 'do not email' preference also get checked?

If I am correct in this, I am thinking about the issues with scenario 1. An admin may add them back into the group not knowing they unsubscribed and then we could have angry people on our hands. Do you think it makes sense to have an unsubscribe flag similar to the 'user opt out' flag that is on a per-group basis?

One thing that might be handy, though, would be a bit more information in subscription history about why this happened.

It turns out that the system really does save the information you need, but there's no UI for it: it's in civicrm_mailing_event_unsubscribe,  and with a lot of hand waving, you can figure out exactly what mailing annoyed the user enough to unsubscribe, and when the user clicked on that link.  For some people, this is useful information.

Right now, subscription history doesn't keep a lot humanly useful tracking information.  But it might be useful to keep a bit more, or create a hook that would let a developer capture events in CiviMail so that a developer could create a custom tracking or auditing feature on a site.