Closed
Bug 1465620
Opened 7 years ago
Closed 7 years ago
Enable about:addons welcome & subscription confirm process
Categories
(Marketing :: Email, task)
Marketing
Email
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jdavis, Assigned: bhaack)
References
Details
Opening this bug to track the implementation of the "about:addons" email welcome and double opt-in process.
Welcome email in SFMC:
MoCo_GLOBAL_AMO_2018_NEWS_HTML_WELCOME-TO-ABOUT-ADDONS_ALL_EN_EML
Notes here:
https://docs.google.com/document/d/10rrMM-aJXTmA4ez1C041tZ8xyqbx5WoLh1lrj_5UTi4/edit#heading=h.vj62f55b07is
Related:
Bug 1371816 - about:addons newsletter - signup form integration
Need to:
1) Test AMO integration on *stage* to ensure double opt-in parameter override is working from AMO interface (https://github.com/mozilla/addons-server/issues/8320)
2) If 1 works, Turn on double opt-in setting in Basket Admin for Prod
3) Set up confirm trigger in SFDC
4) Set up welcome journey in SFMC
5) Make sure AMO teams know they can put signup forms on webpages that aren't behind Firefox Account's login user preferences.
| Reporter | ||
Comment 1•7 years ago
|
||
Action items 1 & 2 are complete!
Remaining tasks for LCM team:
3) Set up confirm trigger in SFDC
4) Set up welcome journey in SFMC
5) Make sure AMO teams know they can put signup forms on webpages that aren't behind Firefox Account's login user preferences.
Comment 2•7 years ago
|
||
Woot!
Jess, is there a how-to guide for creating a signup form on a webpage? I've got a few spots flagged right now for signup forms and can start filing issues if there's documentation folks can reference for implementation.
| Reporter | ||
Comment 3•7 years ago
|
||
There is! I can send over after bit. I want to clarify that you cannot enable standalone signup forms for this yet - not until we have the confirm and welcome triggers in place. (Otherwise, people will signup and never be able to confirm their subscription - aka we can never actually email them.)
Comment 4•7 years ago
|
||
Hey Jess! Any chance I could get on the next email team sprint for help setting up the welcome trigger and signup forms?
| Reporter | ||
Comment 5•7 years ago
|
||
Thanks for checking in, Caitlin! I've flagged this for Michele and I to review. We'll keep you posted. Thanks!
| Reporter | ||
Updated•7 years ago
|
Assignee: nobody → bhaack
| Reporter | ||
Comment 6•7 years ago
|
||
Hey heeey! Happy Monday, Caitlin!
We have a present for you:
Your email subscription confirmation & welcome emails and workflows are live!
You are now free to put your email signup form any/everywhere.
Details on how to implement a signup form using our code + legal best practices:
https://docs.google.com/presentation/d/1P9EBDy-i8ULF8cd7k0bN9a38pbI4ketTYMCbKEoEr5Y/edit#slide=id.g1e076a3623_0_0
Your newsletter ID:
about-addons
Also, since this is a new public-facing signup form, please file a Legal bug to have the copy & form reviewed. (If you follow the best practices in the doc above - you shouldn't have any problems ;) ).
To know if your signup form works, you should be able to subscribe a brand-new-to-our system email address (ie yourLDAP+uniquekeyword@mozilla.com ) and go through the subscription confirmation + welcome email process. You can also ping us if you'd like to check it out.
Please Let us know if you have any questions.
Thanks!
Jess
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment 7•7 years ago
|
||
\o/ Yaaayyy thank you, Jess!
This looks pretty straightforward from our end. I think I just need to find some resources to make a prettier design for the sign up form (is that something I can ask for from the marketing team?) in order to get this rolling. If we run into any implementation questions or issues we will be sure to holla.
| Reporter | ||
Comment 8•7 years ago
|
||
Sweet!
For help with implementation & design - you can reach out to the www.moz.org team if they have reusable code snippets they can work with, or have design bandwidth to help. Likely you'll need to work with your team that runs addons.mozilla.org to design + implement.
You need to log in
before you can comment on or make changes to this bug.
Description
•