Closed Bug 1113270 Opened 10 years ago Closed 9 years ago

Connect posting for newsletter sign up

Categories

(Websites :: Shape of the Web, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ckprice, Assigned: ckprice)

References

(Blocks 1 open bug)

Details

(Whiteboard: [kb=1617256] )

This is to connect the posting for the newsletter sign up on Shape of the Web (aka Lorax).

We will be posting to the MoFo newsletter.

We were pointed to the mozilla.org homepage by Andrea Wood as an example of how to write to the newsletter

e.g.
https://www.mozilla.org/en-US/
https://www.mozilla.org/es-ES/
Andrea - can you provide some clarity on the differences between the en-US version and the other locales?

en-US looks to redirect to a sign up page, while other locales have an AJAX response (preferred). Do they both go to the same list?

Also, is it a requirement that we ask for their language? Can we just pass whatever language the user is currently browsing the site in?
Flags: needinfo?(andrea)
Hi Cory, the best person to ask is probably Jen Bertsch who's also familiar with Lorax. She leads mozilla.org and knows answers I bet. 

We have 2 separate email lists, one for Firefox that is translated into various languages; and 1 led by me at the Foundation which is us-en only. It's a good Q where these lorax signups should go. I think for now we should just mirror the setup currently on mozilla.org, but i defer to Jen (flagged her needinfo).
Flags: needinfo?(andrea) → needinfo?(jbertsch)
Yeah I'm guessing they should go to the Mozilla newsletter currently on the Blue State Digital system vs the Firefox newsletter (Exact Target and Basket).

Would be good to confirm with Dia/Greg.

Andrea - is the Mozilla newsletter currently localized?  Or just en-us?

Cory - I think what you see going on with the homepage is for en-us you can subscribe to the Mozilla newsletter but since it is only in en-us, for other locales we offer sign up for the Firefox newsletter.  Again, would probably be best to confirm with use case with Dia/Greg :)
Flags: needinfo?(jbertsch)
:gregoryjost, :dia

Please confirm this is okay:

en-US - posts to Mozilla Newsletter (not translated)
non en-US - posts to the Firefox Newsletter (translated)

This is the current set up on mozilla.org.

:jbertsch

Do you know if there's an AJAX sample of the Mozilla Newsletter signup? On the mozilla.org homepage it redirects to a separate Thank You page. Do we have someone from Blue State we work with on the tech side?
Flags: needinfo?(jbertsch)
Flags: needinfo?(gjost)
Flags: needinfo?(dbondi)
(In reply to Cory Price [:ckprice] from comment #4)
> 
> :jbertsch
> 
> Do you know if there's an AJAX sample of the Mozilla Newsletter signup? On
> the mozilla.org homepage it redirects to a separate Thank You page. Do we
> have someone from Blue State we work with on the tech side?

Hannah and Andrea are probably the best contacts for that.
Flags: needinfo?(jbertsch)
Flags: needinfo?(hannah)
Flags: needinfo?(andrea)
Whiteboard: [kb=1617256]
A few things.  For now, if the above option is the best choice than let's go with it.  Although this presents a hole in our strategy as the Mozilla newsletter content strategy and ownership has been a mystery to me.  

If Mozilla newsletter is it for US- this might be the reason to push it out to other geos and to tie it together with a the wider Moz content strategy.  

Andrea- you own that newsletter now?  thx,
Flags: needinfo?(dbondi)
+1 for a more unified, strategic email communications strategy. As an organization with lots of various email lists, we're slowly moving toward a better strategy, and a better experience for supporters, but it does not exist yet.

In the interim, Mozilla has its own list (just to be clear: it isn't a newsletter and isn't formatted like a newsletter). I lead content strategy. We send a variety of email communications including advocacy calls to action, Webmaker updates, fundraising; etc. Right now that list is 1.5 million deliverable emails. List growth is primarily from people taking action on campaigns (not organic site signups, which tend to be a low % of signups for most nonprofits). For a variety of reasons, we aren't resourced to manage localization for our outgoing emails.

The best approach is to understand the audience and why they are signing up, and add them to a comms channel that gives them value. The Firefox newsletter is primarily geared toward people who are most familiar with and use Firefox. Mozilla's list is focused on advocacy and movement building. I'm not sure signing people up to the Firefox newsletter makes the best sense given the nature of where they are signing up and for what (people who care about the health of the Web vs. Firefox). Sadly, we don't currently have the capacity to localize our outgoing Mozilla Foundation communications. Though it's not a perfect solution, the immediate solution is to send non-EN signups to Firefox, and EN signups to Mozilla's list. Not ideal, but it's what we got right now. 

Dia I know you and I are going to chat next week, but I thought I'd drop this here as it's important info on the bug.
Flags: needinfo?(andrea)
Flags: needinfo?(hannah)
(In reply to Cory Price [:ckprice] from comment #4)
> en-US - posts to Mozilla Newsletter (not translated)
> non en-US - posts to the Firefox Newsletter (translated)
The Mozilla Newsletter redirects users to a Thank You page[0]. This would obviously be a poor UX for someone coming from Shape of the Web. Unfortunately, we couldn't find an AJAX implementation of this submission form. We may be able to modify the current script to post in an elegant way to match the transitions on SoTW, but we'd like to first discuss an alternative.

Going back through this thread, this doesn't appear to be an approach that is aligned with what users will be expecting by signing up on SoTW[1]. As Andrea pointed out, I imagine receiving Firefox updates after signing up on SoTW could be a bit jarring.

Dia, what are your thoughts on simply collecting submissions from this form until we are more comfortable with our communication channel? This would give us a pure SoTW list we can act on depending on where we are with content strategy and the volume of submissions we receive. Logistics on this approach would involve collaboration with the email marketing team, but we first wanted to get your impression on this approach.

Let me know, thanks.

[0] Mozilla sign up thank you page: https://sendto.mozilla.org/page/st/sign-up-for-mozilla
[1] SoTW newsletter form: http://cl.ly/image/1D0I3g0f2a3n
Flags: needinfo?(dbondi)
Per a meeting with Dia/Greg today, let's save these emails into a dedicated list until there is a detailed plan for these subscribers.

Ben - we'd like to use basket to send these subscribers to. Could you set something up for us?
Flags: needinfo?(gjost)
Flags: needinfo?(dbondi)
Flags: needinfo?(bniolet)
Flags: needinfo?(bniolet)
Update from Ben:
--
Hi Cory.

I have a little more testing to do on my end, and I've checked with pmac about how to make sure everything is fine on my end, but it's close enough for you to get started.

I have created the correct data fields in our production version of ExactTarget and created a "newsletter" in the staging instance of basket that you can connect your webpage to.

The basket slug (staging is basket.allizom.org) is "shape-web"

What languages will this page support? Our email program supports:
de,en,es,fr,id,pt-BR,ru,pl,hu
--

Let's move forward with integrating the email support form.
To confirm, I have tested and basket staging is now subscribing signups to shape-web to ExactTarget. Let me know when you are ready for live form testing / pushing to prod basket.
Assignee: nobody → pmac
Hi  Ben,

I added a few tests to 'shape-web'. Please confirm these were received and look good.

Thanks
Flags: needinfo?(bniolet)
Hi Cory. 

It would be much helpful if you could supply the emails you used to test. Also which version of basket did you send them to, dev, stage or production? 

^ which form did you use to send them or did you use a curl to send them to ET?
Flags: needinfo?(bniolet)
^forgot to flag you
Flags: needinfo?(cprice)
(In reply to Ben Niolet from comment #13)
> Hi Cory. 
> 
> It would be much helpful if you could supply the emails you used to test.
> Also which version of basket did you send them to, dev, stage or production? 
> 
> ^ which form did you use to send them or did you use a curl to send them to
> ET?

cory.k.price@gmail.com
cprice@mozilla.com

newsletter was 'shape-web'

endpoint was https://basket.allizom.org/news/subscribe/

I was using a test form locally, but was receiving 200 OK's
Flags: needinfo?(cprice) → needinfo?(bniolet)
Assignee: pmac → cprice
Priority: -- → P1
Cory,

I am not seeing your email addresses in ExactTarget. They do not appear in the Double_Opt_In Data Extension, nor in Master_Subscribers. 

I did my own test, sending a test email address to the https://basket.allizom.org/news/subscribe/

The address appeared in the correct Data Extension (Double_Opt_In) with a "Y" flag for the "shape-web" newsletter. It's hard to diagnose why your addresses didn't appear. Can you tell me more about how you tested?
Flags: needinfo?(bniolet)
Blocks: 1154768
No longer blocks: 1154768
No longer blocks: 1156466
Commits pushed to master at https://github.com/mozilla/lorax

https://github.com/mozilla/lorax/commit/c775aa1c0c9de002cf3392ebfe941376ebdda543
[fix bug 1113270] Connect to mailing list

https://github.com/mozilla/lorax/commit/7bab387e836d72b1b78cab2e28f6a5d61f63a70b
Merge pull request #36 from ckprice/bug-1113270-post-mailing-list

[fix bug 1113270] Connect to mailing list
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.