3 common mistakes when looking at freemium metrics

15
3 COMMON MISTAKES WHEN LOOKING AT FREEMIUM METRICS Sunday, 3 February 13

Upload: giaf

Post on 13-Jan-2015

664 views

Category:

Business


1 download

DESCRIPTION

Stam Beremski @ NaturalMotion presentation for 2013 Games Industry Analytics Forum

TRANSCRIPT

Page 1: 3 Common Mistakes When Looking At Freemium Metrics

3 COMMON MISTAKES WHEN LOOKING AT FREEMIUM

METRICS

Sunday, 3 February 13

Page 2: 3 Common Mistakes When Looking At Freemium Metrics

INTRODUCTION

• Product Lead at NaturalMotion

• Previously worked on:

[email protected]

Sunday, 3 February 13

Page 3: 3 Common Mistakes When Looking At Freemium Metrics

OVERVIEW OF FREEMIUM GAMES

Sunday, 3 February 13

Page 4: 3 Common Mistakes When Looking At Freemium Metrics

THE FREEMIUM MODEL

App Store

Engage

Retain

Monetize + Invite

Sunday, 3 February 13

Page 5: 3 Common Mistakes When Looking At Freemium Metrics

Good metrics give you insight into conversion at each stage of the model

App Store

Engage

Retain

Monetise + Invite

Good metrics have explanatory powers

Sunday, 3 February 13

Page 6: 3 Common Mistakes When Looking At Freemium Metrics

MISTAKE #1

NOT FOCUSING ON EXPLANATORY METRICS

Sunday, 3 February 13

Page 7: 3 Common Mistakes When Looking At Freemium Metrics

• Total Revenue / Total Users• Session per player / day• Invites sent / player• Invites accepted / Invite• ARPDAU• DAU/MAU

Vanity Explanatory

• Users• Page Views• Daily Revenue• Total Mins of Play• Total Sessions

• Cohort segmentation• Retention• LTV• Sessions pp / day

Counts Ratios

• Behavioural segmentation• Whales vs Free• Single player vs Multi

• Funnels• Tutorial / Quest• Virality funnel

Segmented Ratios

Sunday, 3 February 13

Page 8: 3 Common Mistakes When Looking At Freemium Metrics

MISTAKE #2

NOT CONTROLLING FOR VARIABLES

Sunday, 3 February 13

Page 9: 3 Common Mistakes When Looking At Freemium Metrics

You have just released an update to your game and you take a look at the metrics to gauge success...

• Did this update improve monetisation?

• How long did it take to us get a conclusive answer?

(Data is fictional)

Sunday, 3 February 13

Page 10: 3 Common Mistakes When Looking At Freemium Metrics

There is a problem if you only look at New Users, Revenue and ARPDAU to gauge the success of an update...

Solution: Look at metrics which isolate what you are interested in and control for other variables (in this case the player’s lifecycle within the app)

Problem: Metrics can be affected by uncontrolled variables• In our fictional game players spend 90% of their LTV within 7 days of first playing the app

• An large influx of new players will cause a revenue spike even if the app remains unchanged

(Data is fictional)

Sunday, 3 February 13

Page 11: 3 Common Mistakes When Looking At Freemium Metrics

The solution is to look at player LTV at specific points in the player’s lifecycle

LTV = Total Revenue from cohort

Total # Player of a cohortDay N LTV = Player LTV N days into

the lifetime of a cohort

(Data is fictional)

Sunday, 3 February 13

Page 12: 3 Common Mistakes When Looking At Freemium Metrics

MISTAKE #3

NOT LOOKING AT THE DISTRIBUTION OF

UNDERLYING DATA

Sunday, 3 February 13

Page 13: 3 Common Mistakes When Looking At Freemium Metrics

We often look at averaged data.

Mean = 3.89Median = 3Mode = 3

{1,2,3,3,3,4,4,5,10}

Sunday, 3 February 13

Page 14: 3 Common Mistakes When Looking At Freemium Metrics

Power-law distribution are common in freemium games

Max: $624Min: $0Mean: $0.57Median: $0Mode: $0Std Dev: 7.12% Payers: 5%

Represents $65,000 revenue from110,000 players

(Data is fictional)

Sunday, 3 February 13

Page 15: 3 Common Mistakes When Looking At Freemium Metrics

But statistics can be misleading...

Property Value

Mean  of  x  in  each  case 9  (exact)Variance  of  x  in  each  case 11  (exact)Mean  of  y  in  each  case 7.50  (to  2  decimal  places)Variance  of  y  in  each  case 4.122  or  4.127  (to  3  decimal  places)CorrelaAon  between  x  and  y  in  each  case 0.816  (to  3  decimal  places)Linear  regression  line  in  each  case y  =  3.00  +  0.500x  (to  2  and  3  decimal  places,  respecAvely)

Sunday, 3 February 13