¿Cómo puedo recopilar los correos electrónicos de los usuarios que se registran y enviarlos a una lista de correo (como Mailchimp) para marketing por correo electrónico?
Y configurar algo que haga que el usuario acepte suscribirse a la lista de correo.
Además, ¿es posible agregar un pop-up de suscripción por correo electrónico y un campo en Discourse?
Oh, and as for making the user agree, the first link above discusses how to add a checkbox on user signup, if the mailinglist membership is optional, or simply adding a notice to your signup page and/or your terms and conditions or something like that if it’s not optional.
Alternatively, use the Data Explorer and set up a cron job that posts a JSON feed to Zapier with the information you need. No other plugins required (but you do need to get your hands a little dirty on your server
But lets say I export users today. And get 15 new users tommorow. If I export again, will it export every single user? or will it only choose the ones that are new, is there an option for this? If not, will mailchimp recognize that that email has already been added, and not add it again?
I cant do this because I am letting discourse handle my user logins
Estoy usando Communiteq (anteriormente DiscourseHosting) y ellos me instalan todos los complementos. Entonces, ¿qué quieres decir exactamente con «mancharme las manos»? ¿Podrá el equipo de soporte de Communiteq (anteriormente DiscourseHosting) configurar este complemento correctamente para mí?
The Communiteq (formerly DiscourseHosting) guys install the data explorer plugin by default on every forum, so you should be able to use that method if you host your forum with us.
Be careful, because admins can query out cookies and password hashes with this tool. We actually don’t recommend that data explorer be enabled everywhere for that reason. At minimum it should be an “upon request, we will enable it for you” type thing, to reduce your total exploit surface area.
Thanks for the advice.
Since we cannot disable/enable it on a per forum basis on multisite, we were (once) considering building a locked down version that does not support the “sensitive columns”, but we never got to it. Will put it higher on the to-do list