1 / 9

EMA

EMA. IT Arch Meeting, 5/2010. EMA’s History. Pitched 10/2008(!) as lightweight split testing Received positive interest from all verticals except Redball Designed several components, couple of which were built Shelved Q109, resources diverted to Graffiti. EMA Today.

vera-bray
Télécharger la présentation

EMA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMA IT Arch Meeting, 5/2010

  2. EMA’s History • Pitched 10/2008(!) as lightweight split testing • Received positive interest from all verticals except Redball • Designed several components, couple of which were built • Shelved Q109, resources diverted to Graffiti

  3. EMA Today • Support running tests for customers that can do the site side instrumentation • Use DW/Redball tracking fields • Supported 5 tests over the last year • Have interest from sites that can’t handle site side (Findarticles, Gamespot)

  4. EMA Components DW DW Tracking Convention TES (server) Client Lib (js) EVA (reporting) TMI (Tools)

  5. 40% development done

  6. EVA • Runs significance test on tracked DW data • Requires manual setup • Needs tie-in to user tools (TMI)

  7. TES • Prototyped using POME (Rubics’ Python stack) • Takes affiliate_id, test_id • Decides • Whether the user is in the test • Which variant user should see • Returns payload based on test variant

  8. TMI and Client • No significant development for either component • Bulk of development is here • Also, a couple outstanding design issues: • Automatic set up/tear down for tests (SQL generation, etc.) • DW Cookie synchronization

  9. Deployment • Finish TMI and Client • Solve remaining design/integ issues • Documentation • Pilot partner (FA?)

More Related