Closed
Bug 1310322
Opened 9 years ago
Closed 9 years ago
Developer newsletter sign-ups
Categories
(Marketing :: Email, task)
Marketing
Email
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: viya, Unassigned)
References
(Depends on 1 open bug)
Details
In support of MDN's OKR of 50,000 sign-ups for Dev Rel's web development focused email newsletter.
Comment 1•9 years ago
|
||
Please check out this doc that has the email signup form code info:
https://docs.google.com/presentation/d/1P9EBDy-i8ULF8cd7k0bN9a38pbI4ketTYMCbKEoEr5Y/edit#slide=id.g136f1b2763_0_0
The Newsletter ID for the Dev email program is "app-dev".
Feel free to start implementing this code for testing, but do not go live with it until:
1) signup form copy has been finalized and legal approved
2) re-engagement email sent to the current list
3) confirm & welcome emails have been updated
We're tracking this work in Bug 1310319.
Let me know if you have any questions.
Depends on: 1310319
Thanks Jess! I created this bug at Stephanie's request, who needed a bug to reference when committing the code for the MDN sign-up process.
I wasn't aware about bug 1310319--sounds like we should use that as the main tracking/reference bug for all work related to this goal? If so we can probably just close this one out that I created?
Comment 3•9 years ago
|
||
Ah! Cool! I started to do that, but then didn't want to muck up your signup form production work (if you needed a separate bug).
Feel free to check with the signup form implementation team, and if they don't need this bug for specific questions, close this one out and add the right people to the main bug please.
Thanks!
Comment 4•9 years ago
|
||
Let's keep this bug open and just about the MDN implementation.
Comment 5•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/34980f184cb672204a42e043f6294cb34c1d396b
Bug 1310322: Newsletter
- included behind waffle
- tested
- styled
- needs English only warning
- waffle switch not flag
- GA tracking
https://github.com/mozilla/kuma/commit/752bfb9ec0e803655c88a5391bba92b86ef33bdc
Merge pull request #4020 from mozilla/1310322-newsletter
Bug 1310322: Add Newsletter Sign-Up r=jwhitlock, schalkneethling
Comment 6•9 years ago
|
||
Hello! Saw the mockups during the Sprint readout.
1) Is there a staging server where I test the form?
2) The privacy policy language & checkbox are missing on the signup. You can find the copy/language in the spec doc (https://docs.google.com/document/d/1VoV9rwUjbpikVVj0YUXc_wUOO1kxtU26MIIOJKoqcqE/edit#):
[_] I'm okay with Mozilla handling my info as explained in this <a href="https://www.mozilla.org/privacy/">Privacy Policy</a>."
Can you add this in?
Thanks!
Comment 7•9 years ago
|
||
Like it does on mozilla.org the privacy policy language and check box appears if you interact with the form.
The staging server is developer.mozilla.org.
Be aware that:
1) this is connected to the *live* newsletter backend
2) the email team has not given us the go-ahead to test the form yet, the emails you receive as a result of signing up with the form may not be the ones you expect.
Comment 8•9 years ago
|
||
Thanks Stephanie! I'm part of the email team - I dig that the message has been internalized that emails still need to be updated. Yay! :D
Just tested the form on developer.allizom.org and it worked as expected! \o/
As soon as we get the other items updated, we'll be ready to launch this live.
Comment 9•9 years ago
|
||
Jessilyn, Does "works as expected" mean the email was added to the correct bucket in the CRM and that the sign up was identified as coming from MDN?
Flags: needinfo?(jdavis)
Comment 10•9 years ago
|
||
Correct!
The email was subscribed to the correct email newsletter program and the Source URL was:
https://developer.allizom.org/en-US/
It'd be good to run another test to make sure that any UTM parameters that are used when sending traffic to MDN are passed through. I just tried to add in some fake ones to the staging URL and they are stripped out. (https://developer.allizom.org/en-US/?utm_campaign=test&utm_content=test)
Do you know if there's a way to test this?
Flags: needinfo?(jdavis)
Comment 11•9 years ago
|
||
I... didn't know that was possible. Does that work on other sites? We might have to do some special code to preserve them.
Comment 12•9 years ago
|
||
Preserving UTM codes in the email signup form process does work on other sites. For example:
https://www.mozilla.org/en-US/newsletter/?utm_campaign=desktop&utm_content=foxbox&utm_medium=snippet
passes through the UTM parameters in the form just fine.
It could be that the MDN site as a whole doesn't keep UTM parameters when visiting the homepage.
Comment 13•9 years ago
|
||
I suspect the problem is that the parameters are not going to be transmitted across domains for user privacy reasons.
(I know they are visually stripped from MDN's address bar but they should still be preserved in the request headers)
I'll re-read the documentation to see if there is a way I can pass this information manually.
Comment 14•9 years ago
|
||
oh fancy! Let me test it again to see if it's preserved and passes through in the request headers. I may have stopped testing seeing that it was stripped in the address bar.
Comment 15•9 years ago
|
||
Herm - I just tested it out by going to:
https://developer.allizom.org/en-US/?utm_campaign=test&utm_content=test
And the UTM paramters didn't pass through. Not a blocker, but would be good to have as we point people to signup (more important for the Apps & Hacks blog and stand-alone Dev signup page).
Speaking of which - does someone know where work is being tracked for a stand-along Dev signup page and the Apps & Hacks signup forms?
Comment 16•9 years ago
|
||
The page is being tracked here on the moz.org board https://tree.taiga.io/project/malexis-mozillaorg-durable-team/us/591?milestone=101432
Comment 17•9 years ago
|
||
I can't disable the code which strips the UTM parameters and I can't see a way to add them back for the newsletter sign up. Sorry.
Comment 18•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/c6975f59f3aa6af72110758c7d0e5ee30c2b7eac
Bug 1310322: Fix thank you message overlapping close button
https://github.com/mozilla/kuma/commit/5d851667af98af92016740518fd3277d18195eb4
Merge pull request #4028 from mozilla/1310322-newsletter
Bug 1310322: Fix thank you message overlapping close button r=self
Comment 19•9 years ago
|
||
Hi,
Is there any archive for the newsletter? I recently discovered the "Subscribe to the Mozilla Developer Newsletter" box on MDN and found this bug.
As a MDN reader (and casual contributor), I'm interested in the newsletter, but I want to see what the newsletter looks like. Thank you!
Comment 20•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/79d78766b1074dbccd4181f0ba8a3802d50811bb
Bug 1310322: Remove close button from thanks
It confuses the analytics if people can dismiss the thank you message, so don't show close button with thank you message.
https://github.com/mozilla/kuma/commit/3b51648bc1ff92be44580590dcb016c7551caa41
Merge pull request #4035 from mozilla/1310322-newsletter
Bug 1310322: Remove close button from thanks r=self
Comment 21•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/59e107f038a10a34fe3c24dbc982e6c973d5848f
Bug 1310322: Make newsletter code more robust
Should be easier to move around the page for A/B tests now.
https://github.com/mozilla/kuma/commit/780202f89b29da5fedf694dc589b20f2f41136f6
Merge pull request #4037 from mozilla/1310322-newsletter
Bug 1310322: Make newsletter code more robust r=self
Comment 23•9 years ago
|
||
(In reply to Xue Fuqiao [:xfq] from comment #19)
> Hi,
>
> Is there any archive for the newsletter? I recently discovered the
> "Subscribe to the Mozilla Developer Newsletter" box on MDN and found this
> bug.
>
> As a MDN reader (and casual contributor), I'm interested in the newsletter,
> but I want to see what the newsletter looks like. Thank you!
Howdy!
There isn't yet, but we will be making one. We haven't actually launched the first newsletter yet (it's venturing out on its brave little way on Thursday). For now, though, you can sign up to receive future ones here: http://developer.mozilla.com (the sign-up form is halfway down the page on the right)
This very bug is the one that will make it so you'll have a handy form to go directly to. As soon as we have a couple archived ones to show, we'll be setting up an archive. :)
Flags: needinfo?(dvincent)
Comment 24•9 years ago
|
||
(In reply to dvincent from comment #23)
> (In reply to Xue Fuqiao [:xfq] from comment #19)
> > Hi,
> >
> > Is there any archive for the newsletter? I recently discovered the
> > "Subscribe to the Mozilla Developer Newsletter" box on MDN and found this
> > bug.
> >
> > As a MDN reader (and casual contributor), I'm interested in the newsletter,
> > but I want to see what the newsletter looks like. Thank you!
>
> Howdy!
>
> There isn't yet, but we will be making one. We haven't actually launched the
> first newsletter yet (it's venturing out on its brave little way on
> Thursday). For now, though, you can sign up to receive future ones here:
> http://developer.mozilla.com (the sign-up form is halfway down the page on
> the right)
>
> This very bug is the one that will make it so you'll have a handy form to go
> directly to. As soon as we have a couple archived ones to show, we'll be
> setting up an archive. :)
I see. Thank you.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•