Support inbox
Admin
Users, usage and cost.
From our own database, so it counts every account ever created.
The phone creates an account by itself on first launch, so a person uses Qenzo before giving any email. Those accounts live on a lifetime allowance of free dictations; an email raises it to fifty, once, for good.
| Month | Accounts | With email | Dictated | Paying | Sign-up → dictation |
|---|
Installs, countries and campaigns come from Google Analytics: the download happens in Google Play and never reaches our server.
| Campaign | Source | Impressions | Clicks | Installs | Active | Spend | Per install |
|---|
Google Ads shows a bigger install number than this page, and both are right: Ads counts INSTALLS, this counts FIRST LAUNCHES. The gap is people who installed the app and never opened it - plus the conversions Ads models rather than observes. Nothing here can see a phone where the app was never started.
The three grey rows are not campaigns: "direct" means the person opened the store page themselves (a link, word of mouth, or an ad Google could not match), "Google Play search" means they found the app by searching the store, and "source unknown" is everyone whose first visit predates analytics. Only the paid rows have a spend.
Counted per account, from the Install Referrer the app itself reports. Google counts devices and cohorts, so these numbers are not the same as the ones above and should not be compared head-on.
| Source | Tags | Sign-ups | Dictated | Paying | Reached dictation |
|---|
| Status | Plan | Provider | Dictations | Events | ASR tok | Styling tok | Total tok | Cost | Last active |
|---|
Token + cost tracking started when the usage_events table was added; dictations (all-time) come from the fair-use counter. Cost is derived from a configurable price table, not billed amounts.