<aside> <img src="/icons/home_gray.svg" alt="/icons/home_gray.svg" width="40px" /> Menu

Latest News

Homa Belly SDK

N-Testing

Games

Ideas

Fast Market Validation

Homa Lab FAQ

Homa Academy

Contact Us

Map

</aside>

Table of Contents

Notes: This part is handled by our team. If you are part of a studio, get in touch with your publishing manager to assist in deploying winning configs to new players.

• Homa team members can modify parameter values and apply these modification into scope (OS, country).
• Studio teams can only see the value parameters for their game.

When can we say that a test is done?

In the previous page we showed how to create and launch an A/B Test. Homa publishing managers (in collaboration studio teams) can decided to conclude a test or continue to collect more data. All test viewers however can see the results. Some reasons why it may be a good idea to let a test run for longer after you've obtained some initial results are:

• Reviewing longer term metrics. For instance, maybe Retention D3 has +10% but maybe Retention D14 could be -5%
• Allowing more data to collect and potentially find more conclusive results for different metrics

Otherwise, here are some general guidelines for ending tests:

• Tests should run for a minimum of 7 days to evaluate if they can be stopped
• A significant number of players/installs should be included in the test (at least 2000-3000 players in the defined scope) to have enough relevant data for engagement metrics

Step 1: How to end a test

• https://lab-v2.homagames.com/n-testing/app-config/list
• Click on your game
• Once satisfied with the results of the test and you want to stop it, you can stop it by clicking Stop experiment
• And click on the button YES to confirm the choice

Note: By ending a test, the value of parameters is not updated in the “production” configuration yet.