Closed
Bug 647326
Opened 15 years ago
Closed 15 years ago
[basket] Implement Responsys API (phase 2)
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 663530
Future
People
(Reporter: wbowden, Assigned: jlong)
References
Details
Attachments
(2 files)
We’ve been noticing problems with our Responsys integration. There are rare cases where the form fails. Aside from the problems, whenever Responsys has down time, we lose any opt-ins.
Information about Responsys API:
- Attached you’ll find the API documentation
WSDL:
https://ws2.responsys.net/webservices/wsdl/ResponsysWS_Level1.wsdl
Soap Address location:
https://ws2.responsys.net/webservices/services/ResponsysWSService
Login information sent to James Long / Winston Bowden
Notes from Responsys:
The login should NOT be used to login into the front-end application. The first front end login starts the password expiration.
I have attached our standard API guide as well as some examples of code used for API. This code includes an API login call, merging a recipient into a list and then triggering a campaign. I’ve also included examples of the SOAP request/responses for each of these API calls as well as Java versions. The sample environment is setup to using Axis2.
If the trans message is something like ‘order confirmation’ and that transaction does not implicitly opt the recipient into promotional mailing, then apply the following logic for the merge into CONTACTS_LIST:
1. On match do not update (this assumes that any extra data needed for personalization is included in the TriggerCampaignMessage optional data object.) This will help to improve performance.
2. On NO match, insert record
3. Default permission status = Opt Ou
Quick flow diagram of API call attached.
| Reporter | ||
Updated•15 years ago
|
Assignee: nobody → jlong
| Reporter | ||
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 2•15 years ago
|
||
| Reporter | ||
Comment 3•15 years ago
|
||
Also - can you advise on a timeline for implementation? Thank you!
Updated•15 years ago
|
Target Milestone: --- → 2.1
| Assignee | ||
Comment 4•15 years ago
|
||
It would be great if we could get PHP examples using the standard SoapClient. It will save a huge amount of time and guarantee that it'll generate the correct body (not sure what WSDL version it's compatible with).
If we get that the integration is pretty simple. As far as I know, we aren't very familiar with Soap so there's a steep learning curve.
Updated•15 years ago
|
Target Milestone: 2.1 → 2.2
Comment 5•15 years ago
|
||
Assigning to Winston until he can provide PHP examples to help dev along.
Assignee: jlong → wbowden
Target Milestone: 2.2 → Future
| Reporter | ||
Comment 6•15 years ago
|
||
Sorry - should have commented in here a while ago. James has the PHP samples. Assigning back to him.
| Reporter | ||
Updated•15 years ago
|
Assignee: wbowden → jlong
| Assignee | ||
Updated•15 years ago
|
Summary: Implement Responsys API for all newsletter sign ups → [basket] Implement Responsys API (phase 2)
| Assignee | ||
Comment 7•15 years ago
|
||
This bug has a confusing beginning, but it is now to implement all of the SOAP features required for the email pref center in the Python email web service:
https://github.com/mozilla/basket
We have one SOAP method working (subscribing users) and we just need to flesh it out. We also need to solidify the HTTP API and figure out the best way that forms should interact with it.
| Assignee | ||
Updated•15 years ago
|
| Assignee | ||
Comment 8•15 years ago
|
||
Closing this as it has been superceded by https://bugzilla.mozilla.org/show_bug.cgi?id=663530.
Updated•14 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Updated•13 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•