id.net for Game DevelopersTOOLS TO ENGINEER FUN AND INCREASE CONVERSIONS

Why Collect Data in a Game?o Troubleshooting design problems

o Detecting pattern changes

o Performance testing

o A/B testing design changes

o Understanding users

o Learning how to best sell products

o Adjusting difficultly to boost fun

Case Study: Troubleshooting

18% Player loss from preload time to game play

Case Study: Performance Testing

2% Performance gain in a 30 day period

Case Study: Detecting patterns

A clear pattern showing increased registration ratio

Case Study: Increasing Fun Levels

Increase in user retention at the 30 minute mark by 1% over a 10 day span

Case Study: Difficultly Adjustments

Case Study: Map Deaths

Overview of Rational Game DesignRational development is a way of objectively

creating an experience using quantifiable data.

The data determines the precarious balance

between rage and boredom. To achieve this,

elements are manipulated to perfect the player

experience.

Number of Elements vs Difficultly

Game Elements

• Dynamics (big picture)• Constraints• Narrative• Progression

• Mechanics (drive action)• Movements• Rewards• Competition

• Components• Achievements• High scores• Quests• Avatars

The Ultimate Goal of Rational Design

Crafting the ideal experience

Implementing Rational Design with Feedback Loops

1. Measure actions by collecting data

2. Search for evidence by find patterns in the data

3. Locate the elements that can be modified to change the action

4. Measure the results

5. Rinse and Repeat

Tools Available

Track.id.netRegistrations vs playsGame comparison (admins)Unique players and EngagementBrowser distributionOS distributionCustom events

id.net featuresAchievementsHigh scoresAvatarsPointsGame screenshots

External toolsGoogle AnalyticsLogglyDatacrackerExcel or Google Docs

Tips for Collecting Data

• Schedule a regular time to adjust tracking code

• Use multiple sources where possible

• Discuss the results with someone

• Find a consistent time or place to log data in game

• Plan enough time to measure patterns and results

• Have data collection in and tested before QA

Reaching Goals

• Collect as much data as useful

• Look for patterns

• Modify elements

• Measure results and repeat

• Use id.net social features to reward players

and incentivize ecosystem growth

• Achievements

• high scores

• avatars

• point awards

• game screenshots

• profile views, forum views

• Implement elements strategically to drive actions

• Bonuses and gifts

• Items, unlockables

• quests, challenges, competition

What are your questions?

Ideas, comments, feedback