Email Subscriptions


04.08.09 Posted in Courant News, Yale Daily News by Max

This week’s topic of dis­cus­sion at the CoPress forums regards email subscriptions/alerts, some­thing which I’ve given a fair amount of thought to in the past few months. Today’s post will cover how the YDN has used email sub­scrip­tions up to the present and some ideas for email han­dling in Courant News.

YDN Headlines Email Screenshot

YDN Head­lines Email Screenshot

YDN

Since the launch of the cur­rent YDN web­site in Jan­u­ary 2007, we have had a head­lines email sub­scrip­tion avail­able for pub­lic con­sump­tion. Vis­i­tors could either sign up with just an email address, or if they had a YDN.com account there was an option in their user set­tings to sub­scribe. We cur­rently have sev­eral thou­sand sub­scribers to our email list, which encom­passes both the daily (nightly) head­lines and break­ing news sto­ries. To the right is the email for today’s issue.

As I’ve dis­cussed before, our web­site cur­rently runs on a cus­tom sys­tem built on the CakePHP frame­work. Because send­ing thou­sands of emails at once is a time con­sum­ing process, we use a mail queue sys­tem to spread out the work. When the edi­tors click the “Email head­lines” link in the admin inter­face at the end of the night, we queue up all the emails in a table in our data­base. We then use a cron job to pull out a cer­tain num­ber of emails from the queue each minute and send them through our out­go­ing mail server. It can take up to 30 or 40 min­utes to process all the emails in this man­ner, but it pre­vents over­load­ing or slow­ing of the server, and the emails are not really time sensitive.

Courant News

For Courant News, we have also planned to imple­ment a queue-based mail sys­tem. django-mailer plans to do alot of what we want, but is still in an early stage of devel­op­ment. It is part of the pop­u­lar Pinax project, so I’m sure devel­op­ment will con­tinue for the forsee­able future. The queue is just part of the email sys­tem, how­ever, and we have some ideas about how to make emails more use­ful and customizable.

The basic premise is that we wanted peo­ple to be able to sub­scribe to emails like they can sub­scribe to RSS feeds, where they can choose to only receive con­tent from cer­tain sec­tions, or by cer­tain authors, or with cer­tain tags, etc, etc. For exam­ple, a par­ent of one of the staff reporters might want to get an email digest of any arti­cles his/her son/daughter writes, while not nec­es­sar­ily want­ing to have to fil­ter through all the rest of that day’s paper’s con­tents. Or some­one may only be inter­ested in news in a cer­tain sec­tion, such as Sports. The user would also be able to choose a peri­od­ic­ity of the emails, choos­ing to receive such aggre­ga­tions daily, weekly, or monthly.

While many younger peo­ple are com­fort­able using RSS feeds, many less tech-savvy stu­dents, alumni, and par­ents are still unaware of or unsure how to use RSS feeds. Oth­ers, like myself, may sim­ply pre­fer emails to dig­ging through an RSS client. By giv­ing such vis­i­tors the abil­ity to sub­scribe to emails with exactly the con­tent they want, we can increase the like­li­hood that they will fol­low those links to our site and become fre­quent vis­i­tors. By not forc­ing them to sift through a bunch of links they prob­a­bly don’t care about, we can reduce the fric­tion asso­ci­ated with brows­ing our con­tent and help them find what they are look­ing for.

We’ve cur­rently been explor­ing how to imple­ment such func­tion­al­ity, and have sev­eral ideas. Email alerts/subscriptions are one of the next things on the docket for actual imple­men­tion for Courant News, so I wel­come any feed­back or addi­tional ideas and sug­ges­tions from the community.



3 Responses to “Email Subscriptions”

  1. Can Duruk says:

    Hav­ing peo­ple sign up for only the emails that they would like us a noble idea but with that amount of fine-grained details, you’d be mak­ing it hard for users to sign up for what they really want.

    I mean, a huge form with check­boxes for sec­tions and selec­tion boxes for authors and such might work but I’d prob­a­bly make some UI mock­ups before going along with imple­ment­ing it. As you men­tioned, peo­ple sign­ing up for email sub­scrip­tions would be less tech­ni­cally competent.

    Also, make sure you have some sen­si­ble defaults when you have that many selec­tions. Some­times peo­ple just want to sign up for the newslet­ter and be done with it.

    One other thing you should do is have some room for explo­ration. What if there’s no con­tent for that user that day? Do you just not send any­thing? Or do you send an email with some­thing like “No match­ing con­tent for your cri­te­ria?”. Or maybe you should send them stuff they *might* be inter­ested in.

    I think it’s good that you are seek­ing feed­back for Courant. this early in the process though.

  2. Andrew says:

    Nice post Max. That screen­shot that you have there looks great. Much bet­ter than the default kicked out by Feedburner’s email sub­scrip­tion settings.

    I like the idea about allow­ing peo­ple a lot of flex­i­bil­ity as to how they sub­scribe (to cer­tain top­ics, authors, etc.). I think that a lot more peo­ple might actu­ally sub­scribe to things if they could cus­tomize it so heavily.

  3. @Can, Maybe with your HCI prowess, you can help out ;)

    Ulti­mately I think will end up falling in the site’s theme to han­dle it, with a (hope­fully) sen­si­bly default in the default/sample theme.

    My thoughts on design­ing this: a sin­gle check­box (sub­scribe to newsletter/email updates/whatever with some­thing to tog­gle the avail­able sub­scrip­tions avail­able, which would over­ride the default. “Check this for all, or click here to sub­scribe to spe­cific sec­tions of the site”.

    Usabil­ity is some­thing that is going to be really impor­tant in Courant, but it’s going to take work & input from peo­ple. So I think we’ll (even if “we” is mostly Max) con­tinue post­ing screen­shots, thoughts, etc to hear what peo­ple have to say.

Leave a Reply