3. Plumbee’s growth
3
Oct 2011
• 3 founders & 3
founding
employees
• 0 in data
March 2012
• Mirrorball Slots
on Facebook
launch
• 15 staff
• 0 in data
Dec 2012
• Mirrorball Slots
on iOS beta
launch
• 29 staff
• 4 in data
Today
• 1.2M MAU
• 250K DAU
• 39 staff
• 5 in data
4. “Build, measure, learn”
4
Timing and targeting of offers
Balancing of the virtual economy
Creation of engaging features
Cost-effective acquisition
5. Goals
5
Never say “we don’t have that data”
Breadth of data use
Depth of data use
Agile data use
Scalable foundation for the future
10. Step #2:
10
3rd party
systems lack
flexibility
Want to own
the data
Don’t know
what we want
to know
Analytics is
strategic
Collect everything
11. What is everything?
• State-changing calls from client to server
• Changes of state
• State-changing calls from client to third
parties (Facebook)
Yes, this is a lot of data: 450m events (45 GB
compressed) per day.
Using Amazon Web Services makes this
possible.
11
17. Why we like it
No need:
– To test instrumentation
– To add instrumentation of new features
– To touch transactional databases
– To worry we won’t have the data
Easy and fast to implement
... but we still miss things.
13
28. Step #5:
21
Want to know
what worked
Can’t
separate
factors
Want
flexibility
In-house split testing
29. It’s easy to serve experiments…
• Server-side random assignment of users
• Second tier allows deep tests (bonus:
canary deployments)
• Tool for configuration-only tests
• Test & variant pairs attached to every
analytics event
22
30. … but it’s hard to analyse experiments
23
Web
analytics
Conversion
rate
Binomial
distribution
Simple
tests
•Measuring variables that don’t satisfy
“conversion rate” assumptions
•The need for an Overall Evaluation Criterion
31. Step #6:
24
All data
processing is
manual
This is getting
expensive
And it takes a
long time to
run
Automation & optimization
32.
33.
34.
35. (Basic) optimization
• Spot instances
• Output compression with snappy
• Python streaming jobs
• There’s a lot more we could do…
26