APPSINITYDiscovery and analytics
Listing traffic and analytics
Analytics on Appsinity is store-side event counting. It describes how your listing performed, not how your app behaved after install.
Open Appsinity StudioOn this pageThe events that are recordedHow counting behavesThe Studio dashboardReading the funnelWhat is not measuredFrequently asked questions
The events that are recorded
| Event | Endpoint | Shows up as |
|---|---|---|
| Listing page load | POST /api/listing-traffic | Visits, and the impression term in CTR |
| Download click | Traffic counters | Downloads, installs |
| Play session (web game) | Play endpoints | Sessions and leaderboard entries |
| Review submission | Review routes | Rating and review counts |
| Report submission | Moderation | Nothing to you |
| Ad impression / click | Ad routes | The monetisation dashboard |
| Licence issue | Licence routes | Nothing in Studio |
Important: Nothing records an open, a launch, a session length or a crash after install. Every figure below is a store figure.
How counting behaves
- The traffic post fires when the listing loads, so a page refreshed five times is five visits.
- Download counters fire on the click, not on a completed transfer, so an abandoned download is still a download.
- Public figures on a listing are formatted with a
+suffix for large values, so "10,000+" may be 10,400 or 19,000. - Traffic counters start at zero with the listing; there is no import of Play or App Store history.
- Bots and crawlers are not excluded by anything described in the traffic path.
The Studio dashboard
A Download analytics control exists but is hidden, so today there is no CSV export. Record anything you need to keep.
| Block | Contents |
|---|---|
| Headline KPIs | Total Visits (All time), Downloads (All time installs), Impressions, Clickthrough Rate (Store listing load), each with a vs previous delta |
| Micro cards | Favorites, Donations, Average Rating, Status |
| Insights | Top performing day, Peak activity hour (last 24h), Avg daily downloads, Download rate (downloads per listing visit) |
| Charts | Page View (1 hr / 6 hrs / 24 hrs), Hourly activity, Downloads per day, Traffic sources, Downloads by country, Impressions & clickthroughs per day, Sessions by device, Ratings breakdown, Conversion funnel (Visits → Installs), Favorites per day, Rating average per day |
| Ceilings | Traffic sources are cut to 20 rows; countries to 50 |
Reading the funnel
| Pattern | Usually means |
|---|---|
| High visits, near-zero downloads | The listing did not match the traffic — art, title or short description |
| Visits and downloads both low | Discovery, not conversion. Re-read Store search and browse |
| Download rate above 1 | Repeat downloaders, or an install failure causing retries |
| A traffic source you did not expect | Someone linked you; check the listing text they landed on |
| Country concentration you did not target | A regional feature or a store rail in that locale |
Watch out: Because a download counter fires on the click, the Conversion funnel is visits → download clicks. It is not installs, whatever the label implies, and it is not opens.
What is not measured
- Retention, DAU, session length, level completion — nothing post-install.
- Revenue from your own store, since Appsinity does not see it.
- Uninstalls.
- Crashes, see Crash reports.
- Device capability data beyond the coarse desktop/mobile/web split.
- A/B results: there is no experiment surface.
Frequently asked questions
How soon do figures appear?
Traffic is written per event, so within a page load rather than a nightly batch.
Can I get raw event data?
There is no export. The Download analytics action is not exposed in the interface today.
Do my own visits count?
Yes. Reload the listing during testing and the number moves, which is why an internal test inflates the baseline.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]