Skip to main content
Early access. Store page tests for art, text and language are rolling out; if they are not open for your game yet, the page says so. Price tests and gameplay tests are not open yet. Until you have a game on Summer Games, this page shows example data, marked Example data.
Open A/B tests at summerengine.com/studio/grow/ab-tests.

Make a test

1

Name it

Under New A/B test, give it a Name (up to 80 characters), such as “Darker key art”. Pick the Game if you have more than one.
2

Choose what changes

Art (key art, wide capsule or tall capsule, from your published images), Text (game name, tagline, description) or Language. Empty text fields keep the published text.
3

Add versions

Version A is your published store page. Add up to three more with Add version. Give each a share of visitors; the shares add up to 100%.
4

Choose countries (optional)

Two-letter codes, such as DE, AT, CH. Empty means everyone. A language test suggests countries for you.
5

Start it

Click Start test, or Save as draft and start it later.
Visitors keep their version on every visit. One test runs per game at a time.

Read the results

Each test shows, per version: visitors, purchases, conversion, revenue and revenue per visitor, and how it compares with A. A difference is marked clear only when it is unlikely to be chance; until then it says Not clear yet. Give each version a few hundred visitors before you decide.

Stop it and keep the winner

Click Stop, pick the winner (or No winner), and confirm. Stopping does not change your store page: to keep the winning art or text, publish it on the game’s store page.

Apply for a test run

Below your tests, Apply for an A/B test asks the Summer team to run a test with you, for things you cannot test yourself yet. It is an application: the team reaches out by email, and nothing is charged when you apply.

With your agent

Ask “test a darker key art against my current one”. The Studio assistant creates the test as a draft, and starts or stops it only when you ask. It reads the results and says when a difference is clear. From another agent: experiments.list, experiments.results, experiments.create (a draft), experiments.start and experiments.stop. For now starting or stopping a test asks you first: Summer Games still asks. Soon, with Prices and live changes on in Agent permissions (the default), it happens at once. See Use the agent.
Does this not help you? Reach out on Discord!