Responsys

Registration Forms

There are few different ways of getting subscription data into Responsys. You can set up a Responsys hosted form, build your own form and POST data to Responsys, use their API, etc.

POSTing directly to Responsys

1. Build your form HTML. Here's an example
2. Send a POST request to Responsys with your subscription data. The example form uses Curl to send this request.
   1. POST to this URL: http://awesomeness.mozilla.org/pub/rf
   2. Include the following in your POST data...
      1. _ri_ = some unique form ID. This basically tells Responsys where to put your data.
         1. for production, _ri_ = X0Gzc2X%3DUQpglLjHJlTQTtQyTQ3qQ0OQQzgQvQviRVwjpnpgHlpgneHmgJoXX0Gzc2X%3DUQpglLjHJlTQTtQyTQ3qQ0NQQGQvQvH3
         2. for dev/stage, _ri_ = X0Gzc2X%3DUQpglLjHJlTQTtQ1vQ2rQ0bQQzgQvQy8KVwjpnpgHlpgneHmgJoXX0Gzc2X%3DUQpglLjHJlTQTtQ1vQ2rQ0aQQGQvQwPD
      2. A flag to indicate which newsletter the user is signing up for. For example, the about:mozilla newsletter uses, "ABOUT_MOZILLA_FLG = Y". about:mobile is "ABOUT_MOBILE_FLG = Y". This field needs to be set up in the Responsys schema before use.
      3. A similar flag marks when the user signed up. For example, "ABOUT_MOZILLA_DATE = 2010-09-30 10:00:00"
      4. You can include any other data that maps to an existing Responsys field. For example, about:mobile includes the subscribers name using "FIRST_NAME" and "LAST_NAME"

Forms on mozilla.com

If you're building a registration form on mozilla.com, many of the steps above are already built for you. There is a library for POSTing to Responsys, and some classes that hopefully make building forms easier. Also, the _ri_ config is handled in mozilla.com's config file. Most of the work falls into building the actual form HTML and any validation rules. The about:mozilla, about:mobile, and mainstream newsletters are all good examples you should work from.

Viewing subscriptions in Responsys

1. Log in
2. Go to the "Folders" tab
3. Go to the "!MasterData" folder
4. Production subscriptions are kept in "CONTACTS_LIST" (obviously, be extremely careful with this list)
   1. There is a testing list "TEST_CONTACTS_LIST"