如何收集注册用户的邮箱并将其发送到邮件列表(如 Mailchimp)进行电子邮件营销?
同时,如何设置让用户同意订阅邮件列表的功能?
此外,是否可以在 Discourse 中添加一个邮件订阅弹窗和输入字段?
如何收集注册用户的邮箱并将其发送到邮件列表(如 Mailchimp)进行电子邮件营销?
同时,如何设置让用户同意订阅邮件列表的功能?
此外,是否可以在 Discourse 中添加一个邮件订阅弹窗和输入字段?
Although this has been requested many times, there are only workarounds to what you want, I think.
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 ![]()
https://meta.discourse.org/t/data-explorer-plugin/32566/124?u=bartv
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
If its broken, it wont work right now?
我正在使用 Communiteq(原 DiscourseHosting),他们会为我安装所有插件。那么您所说的“亲自动手”具体是指什么呢?Communiteq(原 DiscourseHosting)的支持团队能否成功为我设置这个插件?
您当然应该向 Communiteq(前身为 DiscourseHosting)团队咨询他们如何管理托管服务,而不是在这里的 Meta 上询问。
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 ![]()