Features
Everything needed to judge an app campaign
Where users came from, whether they stayed, what they paid, and what the spend returned.
Attribution you can defend
Each install is credited to the click that caused it, using evidence a platform confirms. On Android that is the Google Play install referrer, which carries your link’s click ID through the store. On iPhone it is Apple’s Search Ads token, a creator code, or an advertising ID the user agreed to share. Anything else is reported as unattributed rather than guessed at.
- Exact matching on Android, with no permission prompt
- Apple Search Ads attribution without asking the user for anything
- Click injection caught by comparing click and download times
- Last click wins inside the window you set per app
Retention, per source
Sessions are recorded from the first launch: when the app opens, how long it stays on screen, and when a session was cut short by a crash or a kill. Day 1, 7 and 30 retention then exists for every campaign, creator and link — not only as an app-wide average.
- Sessions resumed within 30 minutes count as one visit
- A session interrupted by a kill is closed at its last heartbeat
- Reporting days follow the app’s own time zone
Revenue and what it returned
Purchases arrive with their amount, currency, product and transaction, counted exactly once however often a device retries. With spend imported from the ad platforms, cost per install and return on ad spend come out of real numbers rather than a spreadsheet.
- Every purchase counted once, by transaction ID
- Test and sandbox purchases flagged and excluded by default
- Any currency, as the store reported it
Creators, links and codes
Not every source has an API. Creators, newsletters, websites and QR codes get tracking links, and codes for iPhone users who arrive without one. Both give exact credit, and neither needs a tracking prompt.
- A link per creator or campaign
- Codes your users type in the app, matched exactly
- Clicks recorded with the time, link and device type
Privacy as a default, not a setting
The SDKs collect what reporting needs and nothing else: no names, contacts, location or screen content. Consent and opt-out are built in, remembered across launches, and honoured before anything is recorded.
- No fingerprinting, on either platform
- waitForConsent for apps that must ask first
- IP addresses erased after 30 days
- Children’s apps never read an advertising ID
SDKs that stay out of the way
One call at launch. Events are written to disk before they are sent, so nothing is lost when the phone is offline, the app is killed or the device restarts — and what is still unsent goes once the network returns, even if the app is never opened again.
- iOS 15+ (Swift) and Android 5.0+ (Kotlin)
- One small dependency on Android, none on iOS
- Batched, compressed sending every 30 seconds while open
- Every call returns at once and never throws
See where your users really come from
Add the SDK to your app, connect your ad accounts, and watch the first installs land.