Mozilla.com/Newsletters: Difference between revisions
| Line 25: | Line 25: | ||
* Is it all client-side? | * Is it all client-side? | ||
* Do we need notifications and error handling? | * Do we need notifications and error handling? | ||
* How do we implement security? | |||
* Pass a token to the service | |||
* whitelist domains | |||
Revision as of 00:55, 24 May 2011
Email campaigns & Newsletters
This page outlines a new project which aims to standardize our usage of email marketing services.
Purpose
We have several sites which need newsletter subscription functionality, written in different languages & platforms. Instead of maintaining code which interfaces to third party email services across all our sites, it makes sense to create a web service which provides these features in one place with one API.
Currently we use Responsys for email marketing. If we switch email marketing services in the future, we will only need to change one codebase. Additionally, all authentication data is kept in one place. We've had problems keeping our auth keys to Responsys secret, and changing them is currently a hassle because it must be done on all sites.
Web service
- Create a web service at http://subscribe.mozilla.com/
- Include javascript from that domain
- Call javascript to subscribe?
- Written in Python or node.js?
- If Python, use Celery for async tasks
More details to come.
Questions
- What does the API look like?
- Is it all client-side?
- Do we need notifications and error handling?
- How do we implement security?
* Pass a token to the service * whitelist domains