Confirmed users
1,022
edits
CloudServices/Roadmaps/Campaign-Manager: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Roadmaps/Campaign-Manager (view source)
Revision as of 15:57, 17 October 2012
, 17 October 2012→Issues and Concerns
| Line 148: | Line 148: | ||
* TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do | * TODO: do we have a query param on the redirector to allow tracking? Talking with JR I think we do | ||
** Not so sure about that. The tracking param would be integrated into the click URL (e.g. the many redirectors out there that then boot to a proper URL) | ** Not so sure about that. The tracking param would be integrated into the click URL (e.g. the many redirectors out there that then boot to a proper URL) | ||
= Operations = | |||
== Hardware Request and Status == | |||
The project is expected to require: | |||
* A central db (SQL based) | |||
* Memcached | |||
* web heads: | |||
** campaign data delivery (to devices) | |||
** redirect servers (to handle tracking links from users) | |||
* Connection to the Services Metrics system. | |||
===System Demands=== | |||
Remote clients request Announcements that match a given set of criteria. The servers provide a set of announcements that the client places on pages for user action. When a user selects a link associated with the announcement, the user is directed to a tracking URL that records the user action and delivers the original destination URL. | |||
No individual user information is recorded. Privacy has already been briefed. | |||
===Current undetermined elements=== | |||
I do not have full information for the following: | |||
1. Expected QpS or Customer load. | |||
The target audience currently is "Android", with "B2G" expected shortly after. Devices would poll for updates at first launch, then again at an undetermined period beyond that (~24+ hr). A connect failure is non-critical, but the device will retry afterwards. Redirect links will record data associated with the campaign to metrics and return a 302 for the correct, associated link. | |||
2. Number of active campaigns. | |||
The number discussed currently is "20". I expect that, the number will probably be closer to "100". Data records are not expected to be over 1K each and should fit within memory | |||