564826 - Tracking Bug for Email Engagement

Status: VERIFIED FIXED

(www.mozilla.org :: General, defect)

Comment 1

[Tara (musingt)]

In Q2, our goal is to begin email engagement with our users.  This involves adding an email sign-up form to key pages, as well as creating new landing pages, etc.  I've filed this bug to track our progress.

Comment 2

[Pascal Chevrel:pascalc]

Just that you know, email collecting is more strictly regulated in Europe than in the US, you may have to check with legal about it if you want that on non-US pages.

Comment 3

[Tara (musingt)]

Thanks Pascal.  Jane, Eve, and Cbeard have been working on this for several months now, in close collaboration with the Legal team.  We definitely understand (and have accounted for) the various sensitivities around privacy, security, etc., and made sure to follow best practices at every step.  Hope that helps.  Also, I believe that we're rolling this out with an en-US focus first.  Jane can help speak to this more when she returns from her PTO next week.

Comment 4

[Tara (musingt)]

Hey guys.  I'm attaching a sketched wireframe to show the flow between the pages.  This was done really quickly and it certainly lacks many details and proper labels :)  but I'm hoping it'll help give a quick glance at the big picture and workflow.  

Alex, to your point... I can see how we can consolidate a bit here... and create different states that would cover pages F,G, and H, vs. new pages.  I can see us nixing the social media icons on "G", for example.  But I'll have to think about it some more.  Let me know what you think.

A: Default FR/WN page with new engagement button
B: Clicking on the button expands the block into a sign-up form
C: Once you hit "submit", if there was an input error you'll get the pop up notice - there are two states for this.
D: If you've inputted everything properly, then you'll get the confirmation status with a check mark and Thank-you statement, indicating that you should check their email and verify your email address. 
E: This is the email that was triggered, with a link to verify.
F: If the verification link has expired by the time they click on it, they'll get a page indicating this and asking them to re-enter their information.
G: Once they've re-entered their information and hit submit, then the status will change (similar to D) and ask them to check their email.  Here we're also showing them icons for other social media channels, and ways that they can stay in touch.  An email is triggered here again (E) in which they'd have to click on to verify.
I: If verification takes place within the allotted time-frame, they'll get the final "thank you" confirmation page + other ways to stay in touch.

H: This is the current "Stay Connected" page, which will also be updated to include an email sign-up form.

Hope this helps....

Comment 5

[Tara (musingt)]

Attachment: wireframe sketch

Comment 6

[Jane Finette]

Hi there, back at work now. 

Thanks for pushing on with this. I learned from an email between Morgamic, Alex and Eve that we are now pushing for the database fields to be ready for May 31. 

Can you give me the anticipated date to go live to site please? 

Let me know if there is anything else you need to get this moving. 

-Jane

Comment 7

[Jane Finette]

Hi there 

I wanted to update you formally in this bug w.r.t. our email sign / database changes. Due to unforeseen circumstances we are going to start to collect our own email addresses, and self handle sending out an email Welcome Newsletter. We are currently searching for a new large scale email service provider which will likely be on board in the next 4-6 weeks -- we are ramping up this search very quickly. 

So, what does this mean for our project here?

I have added comments in each bug directly - is there a way to put these bugs "on hold" (except bug 564487 ) till we get moving again?

Comment 8

[Alex Buchanan [:abuchanan]]

Closing this tracking bug, it's not used anymore

Comment 9

[raymond [:retornam] (inactive)]

(In reply to comment #8)
> Closing this tracking bug, it's not used anymore

Verifying based on comment #8