I am using the Goodnews Email system and it works great overall. One issue I am having is that when someone unsubscribes, they are completely removed from MODX including their MODX user entry. That means you lose all record of this email address having been in your system. This becomes an issue when you want to keep a record of un-subscribes to ensure you don’t add an email (for example during a mass import) that has already unsubscribed in the future.
Does anyone have insight into this?
Thanks in advance!
Not sure how the legal perspective is there, but if I unsubscribe from a service I would expect or atleast appreciate my data and email to be completely deleted from your system. If you face issues for importing data, you will have to first make an export of the current subscriber list and import this wherever you need it, I guess.
I found a partial answer to this. If you use Goodnews or another method of creating subscribers (and thus MODX users by default), if the user doesn’t get assigned to a Access group (for example Members), then if they unsubscribe, they will be deleted from MODX entirely. However, if the user is part of a access level group, then if they unsubscribe, their user account will still show up in both the MODX user table and also the list of Goodnews subscriber emails (although they won’t be part of any mailing group any longer) and not be deleted.
In Goodnews, you can filter the list of subscribers that are not currently assigned to any Goodnews Group (thus they are not subscribed) through their default subscribers view. However, this list is slightly deceiving as it includes emails that are not currently subscribed to any mailing list (but didn’t explicitly unsubscribe) and also emails that explicitly unsubscribed so there is no way of actually differentiating the two when you view them in the backend.
For my purposes, this might be ok since I think we can treat the two groups as the same, but it would be nice if Goodnews had a option to view explicit unsubscribes.
@vibedesign, thanks for your input. I agree I would like my info treated similarly, but the reason I thought it would be important to keep the list is to ensure that explicit unsubscribe emails don’t get accidentally added back again. I agree, I will likely export list prior to importing to maintain the integrity of the list.
2 Likes
Hi, I’m the developer of GoodNews. Could you please post the complete unsubscribe snippet call?
The GoodNewsUnsubscription snippet has a param removeUserData which - when set to 0 - should prevent removal of user data.
https://docs.bitego.com/goodnews/implementation/unsubscription-snippet/
Thanks gadgetto! I will try this param out.