Closed Bug 1387542 Opened 8 years ago Closed 8 years ago

CRM/Email Marketing Request: AMO - Email to Add-on Developers with Contributions

Categories

(Marketing :: Email, task)

Product:
Marketing
Component:
Email
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: caitmuenster, Assigned: amora)

Details

>> Mozilla Team/Department Add-ons Community Experience Team (ACE) >> What kind of relationships are you looking to develop? This is a non-newsletter, one-off email to a specific subset of add-on developers. We’re changing the way the Contributions feature works on AMO. We want to inform developers who use this feature that the change is coming, and also ask them to help us gather payment sites they would like to use for contributions. >> How will you nurture these relationships? Email, blog post, social support, direct outreach >> How will success be measured? Responses to amo-admins and the specified Discourse thread will determine the success of this email. >> What is the risk to not doing this? We would not be able to reach as many developers through other channels, and this could impact our ability to provide adequate and thoughtful response to changing the contribution channels. >> What's the timeline for launch? Looking to send this email out the week of August 7. >> Any other info we should know? - Doc with content and list info: https://docs.google.com/document/d/1p70LvfH5Fhu-boLjHBLStcJoXo9ddiikz8SJiV6QEWY/edit?ts=5983b797# - we need to file a bug for legal review
Thanks, Caitlin! You're on the agenda for Monday's LCM intake mtg. See you then!
Hey Caitlin - thanks for coming today! This audience size & transactional email in nature can be handled easily with a Cirrus Insight send. CC'ing Andrew for more info on next steps to help you/the team launch this. Thanks! Jess Notes from intake mtg here: https://docs.google.com/document/d/1hB-PHqLmWhjsoxmbP5Y-Tt0R6YqXoiy9cpmDcYrVhSA/edit#heading=h.za0hgdvwe8lu
Assignee: nobody → amorales
Awesome! Thanks, Jess!
Just checking in -- wasn't sure if I needed to add this to the Email calendar since the list is so small. If so, I'll go ahead and follow that flow; otherwise, I'll plan to get this out. Thanks!
Hi Caitlin! The general rule is, if you are going to use Marketing Cloud to (manually) send the email, then it should be added to the email calendar :) Brynne
Hey Caitlin, Was in SFMC (Marketing Cloud) this am pulling some screenshots for reporting. Ran across this email: My Emails > AMO > MoCo_GLOBAL_AMO_2017_TRAN_HTML_CONTRIBUTIONS_ALL_EN_EML If you haven't sent it already, please add in more context to the footer that explains where/how to modify this opt-in setting to unsubscribe: You have received this email because you are a registered add-on developer on addons.mozilla.org and you have Contributions enabled in one of your add-on listings. If you do not want to get updates about your x, then do y. Thanks!
Thanks Jess! We were intending this to be a transactional email (and didn't include opt in in the list criteria) - do we still need to offer the opt out option?
We recently had a transactional email sent using our standard language, that ended up in some confusion online if we were breaking anti-spam laws in Canada. In an effort to be crystal clear about our transactional emails & *why* someone is getting it, our standard language now is: You have received this email because you are a <insert why here, ie: registered contributor on support.mozilla.org.> If you do not want these updates in regards to your <x> Account, please <do this - ie go to x platform and do y to opt-out>. So there's not really an opt-out mechanism - other than if they want to stop getting emails from us - they'll have to <remove their addon?>. We don't really want them to do that, but this clarity in language helps drive home what "transactional" and "no need to include an opt-out mechanism" means for our end users. We get why it's okay. This is our way to help them understand better. Does that help?
Ah, yes, thanks for clarifying! I'll talk to Jorgev about what action they can take and add it to the footer. Thanks, Jess!
Sweet! Thank you, Caitlin! And feel free to finesse the copy however you can to balance the making-of-the-situation-clear and not seeming too blunt like we want them to stop being an add-on developer. (A personal fear of mine, but you might be all good on it!)
Caitlin, is this good to close?
Flags: needinfo?(cneiman)
You got it, Jess! Closing it down.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(cneiman)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.