Mobile measurement, self-hosted
Know what an install is actually worth.
Lodestar connects an ad click to an install, and that install to every lira it earns afterwards. Attribution, revenue and cohort LTV in one place — running on your own infrastructure, with no per-install fee between you and your numbers.
| Campaign | Installs | Spend | d0 | d1 | d7 | d30 | d90 | ROAS |
|---|---|---|---|---|---|---|---|---|
| daynote_de_troasgoogle_ads | 4,812 | $1,204.60 | $0.11 | $0.28 | $0.63 | $1.42 | — | 1.34× |
| daynote_us_troasgoogle_ads | 2,190 | $881.30 | $0.09 | $0.24 | $0.51 | — | — | 0.92× |
| organicorganic | 7,431 | — | $0.07 | $0.19 | $0.44 | $0.98 | $1.71 | no spend |
Numbers we can show you
Not case-study percentages from someone else's campaign. These are properties of the software, and you can check every one of them.
- 406,481bytes
- added to a minified release APK
- Measured by measureSdkApkDelta on every release of the SDK, against a 512,000-byte budget.
- 210,064bytes
- release AAR on Maven Central
- com.ertechsoftware.lodestar:sdk — no manual repository setup.
- 0 · 1 · 7 · 30 · 90
- cohort checkpoints, per campaign
- Day-grain LTV split by network and campaign, measured against real spend.
- $0.00
- per install, forever
- It runs on your own infrastructure. There is no meter between you and your data.
A different arrangement
The established platforms are hosted SaaS billed per install. That is a real product with real advantages — a support contract, compliance paperwork, integrations we do not have. It is also a meter on your growth and a copy of your users on someone else's infrastructure.
Hosted, per-install SaaS
- Cost scales with the growth you are trying to measure.
- Event data lives in the vendor's warehouse; you query what they expose.
- Raw events age out on their retention schedule.
- Mature integrations, certifications and a support contract.
Lodestar, self-hosted
- No per-install fee. Cost is the server you already run.
- Events land in your Postgres. Ad-hoc SQL is a query, not a support ticket.
- Every accepted payload is archived verbatim and can be replayed.
- Younger, narrower, and honest about it: Android SDK, Google Ads and AdMob today.
How it fits together
- 01
Embed the SDK
One Android dependency from Maven Central. It reads the install referrer, tracks sessions, and forwards AdMob paid events. Two fields to configure: your app key and your endpoint.
- 02
Connect your ad accounts
Authorize Google Ads and AdMob once, read-only. Cost and revenue are pulled on a schedule and reconciled against what the SDK reported, so an API total that disagrees with the device is visible rather than silently averaged away.
- 03
Read the cohorts
LTV and ROAS per cohort, network and campaign. A cohort too young for a checkpoint reads as unknown, not as zero — the difference matters when you are deciding where the next budget goes.
Your data stays yours
Lodestar runs on infrastructure you control. Connecting Google Ads or AdMob grants read-only access to your own campaign cost and ad revenue, used solely to produce the reports in your dashboard. Those credentials are stored encrypted and are never shared with anyone else.