App growth teams

Your store is a growth channel nobody is watching.

Acquisition gets measured to two decimal places. The listing every install passes through gets looked at when something is obviously wrong, which is usually a while after it was.

  • Store health beside acquisition
  • Your knowledge base
  • Review before send
You

How is the store doing, and is it costing us installs?

Reading Play Console vitals, ratings and acquisition reports

One threshold is being crossed.

SignalNowThreshold
Crash rate2.4%1.09%
Rating3.63.5
Reviews unanswered312none set

Above the threshold an app risks reduced store visibility, which raises install cost.

Read fromPlay ConsoleYour ad platforms

What it costs today

The store moves your install cost, and nobody owns the number.

A rating that slips costs you installs twice over, once in store ranking and again in the people who see the listing and decide against it. Those figures, with their sources, are on Review responder. What matters here is that none of them appear on any dashboard your team opens, so nothing moves until somebody eventually looks.

Two dashboards

One of them is watched every day. The other is opened when something breaks.

Watched
  • Cost per install, to two decimals
  • Channel mix, daily
  • Creative performance, weekly
Not watched
  • Crash and error rates against the store's own thresholds
  • Rating drift, which raises install cost without anyone changing a bid
  • Hundreds of public reviews nobody has replied to

Both sets of numbers decide what an install costs. Only one of them has an owner.

The first hour

What connecting a store console actually turned up.

An Android crash rate of 2.4 percent against Google's 1.09 percent threshold
Weeks of paying more per install than you needed to, on an app whose marketing team had no reason to be looking, because the number belonged to nobody.

What this is made of

Read it first. Answer it second.

In that order deliberately. Reading changes nothing and almost always finds something before anyone has decided to trust us with a reply.

Before you ask

Three that come up every time.

Our engineering team already watches crash rates.

They watch them as a stability problem, which is correct and different. Nobody is reading them as an acquisition cost, and that is the gap: a rating or a vitals threshold moves what you pay per install without appearing on any marketing dashboard.

Do we have to let it reply to reviews?

No. Reading the store changes nothing, needs nothing applied for, and is where we suggest starting. Answering is a separate decision you make after you have seen what it would be answering.

What does it need from us?

Read-only access to the store console, created by you in your own account and revocable by you in one click. Most of what this page describes needs nothing applied for.

Start here

Let us read your store before you decide anything.

It changes nothing, it needs no application, and you keep whatever it finds.

Usually 45 minutes  ·  APAC (GMT+6), working across time zones