Thanks for the module, it worked great getting my users imported.
I am unclear on how much the module "synchs" the users, i.e. do new users to my drupal site automatically get subscribed (I would like them to) and if any users unsubscribe, how is it handled in their drupal user profile?
Thanks for the great module!

Comments

konsumer’s picture

Status: Active » Closed (fixed)

I designed the whole thing to be opt-in, meaning that the user has to add themselves to your lists. I hate spam, and I'm not interested in making it easier to create unsolicited emails.

The profile part works like this:

If the user is logged in, the data is stored in the "data" field of their user var. This way you can check for it, later, if you like (like in a custom module, or whatever) The application remembers which users have signed up for which lists, so it won't bug them (by showing a signup block) if they have already signed up.

savmac’s picture

Thanks for the info konsumer. I certainly agree on your viewpoint regarding spam. In the case of my drupal website, any user who registers on it is doing it for the purposes of receiving newsletters, therefeore I do not need the opt-in block. Using the block would be confusing to my users since they already explicitly opted in by registering.
I plan to use the module by importing all users to update Constant Contact before sending out any newsletters. The problem is that I will I run the risk of re-registering any users who have subsequently unsuscribed from my Constant Contact newsletter but remain a user on my drupal site.
Any suggestions to make this work?

konsumer’s picture

I'm thinking about adding an opt-in block on registration. This seems like a good compromise to me. The user can check a box when they sign-in. I talk about this a bit here:

http://drupal.org/node/222156

brenda003 made a great simple patch to add theming support, so when I get a minute or two, I'll add both of these to the next release.

The idea would be that you can turn off "anonymous users may subscribe", and turn on "opt-in on registration" and it would basically do what you want, but the user would still know, explicitly, that they were signing up (because they checked the box.)

I hear what you are saying about signups, and in your case I think it might be a great idea, but I feel like might take the module in a "wrong" direction (it's still an easy patch though, if you really want it that way.) When you signup for google app stuff, for example, you are explicitly making yourself a user, therefore, it may stand to reason that you are opting-in, because you are signing up for their free services, but they still offer a checkbox for their newsletter, and "google may contact you about your service". I like this approach. It seems very non-invasive, and overall more friendly. I checked the boxes when I signed up for my last google app setup, just because I liked how friendly they were about it. Maybe it's just me.