Where they are
Each install gets one source on its first launch, and a coarse location: see who has a session now, and which markets each channel brings.
Attribution for iOS, Android, React Native and Flutter apps. Installs, trials and revenue by source, from Apple Search Ads keywords to smart links and organic. No IDFA, no ATT prompt.
Included in Startup, or free self-hosted · iOS+ Android
Store consoles count the install and stop there. Attribution follows it: here is one user from the demo workspace, and what is kept at each step.
On iOS it reads Apple's AdServices token, on Android the Play install referrer, and a smart link from the URL the app first opened with. Everything else counts as organic.
The SDK never reads advertising identifiers. Apple Search Ads comes from Apple's AdServices token.
Installs are never matched by device signals. When the source can't be known, the install counts as organic.
City and coordinates are rounded to about 10 km. The IP address is not stored for location.
Each install gets an id the SDK creates. It is not tied to the device or to other apps.
Start the SDK with disabled: true for a user who opts out, and it collects and sends nothing.
Turning Attribution off for an app deletes its installs, events, revenue, links and postbacks.
Apple Search Ads
6,120installs
1,480 trials · 520 paid
Campaign, ad group and keyword, from Apple's AdServices token.
TikTok Ads
4,310installs
910 trials · 260 paid
Campaigns through ad smart links, with the ttclid kept.
Meta Ads
2,890installs
540 trials · 140 paid
Campaigns through ad smart links, with the fbclid kept.
Smart links
1,240installs
330 trials · 124 paid
Your own links for posts and creators; exact on Android via the Play referrer.
Organic
3,859installs
660 trials · 240 paid
Everything else. No IDFA, no fingerprinting.
Trials and purchases go back to TikTok, Meta and Google Ads with the click id, so bidding learns from payers.
The co-founder and MCP tools read the same data. Ask in plain words and get the answer with the numbers behind it.
A daily check flags installs, revenue, trials or conversion far from the 14-day median, on Telegram.
Open it in the Appeeky desktop app, or read the same data from the Analytics API.
Each install gets one source on its first launch, and a coarse location: see who has a session now, and which markets each channel brings.
Who has a session right now, and the screen, trial or purchase they just reached.
Installs with a session in the last 5 minutes.
Revenue shows net of refunds, with the gross and refunded amounts next to it.
Links for posts and creators that open the right store, keep the click and open the right screen after install.
Pass the RevenueCat or Superwall user id, and every trial, purchase, renewal and refund arrives with the install source that made it.
Copies of SKAdNetwork and AdAttributionKit postbacks land on your domain, by network and campaign, with the conversion value.
Spend from Apple Search Ads, TikTok Ads and Meta Ads next to the revenue the SDK attributed, down to the keyword.
One SDK for React Native and Expo, iOS, Android and Flutter. Pass your RevenueCat or Superwall user id, and every purchase gets its source.

npx expo install @appeeky/analytics-expo \
@react-native-async-storage/async-storage \
expo-application expo-deviceTerminal
One package for React Native and Expo. expo-application and expo-device are optional and add the app version and exact device model.

{
"expo": {
"plugins": ["@appeeky/analytics-expo"]
}
}app.json
It turns on Apple Search Ads, the Play referrer and SKAdNetwork postback copies. Rebuild as a development build after adding it.


import Appeeky from "@appeeky/analytics-expo";
import Purchases from "react-native-purchases";
Appeeky.init({ key: process.env.EXPO_PUBLIC_APPEEKY_KEY! });
// Link each install to its RevenueCat customer so purchases get a source.
Appeeky.identify(await Purchases.getAppUserID());App.tsx
Pass the RevenueCat or Superwall user id so each purchase finds the install that made it.
Free · you pay your Cloudflare bill
The server is source-available. Run one Worker and one D1 database in your own Cloudflare account. Installs, events and revenue never pass through Appeeky.
Includes:
Included in Startup · 2M events / month
Turn it on for an app in Appeeky and add the SDK. Each account's data is kept in its own isolated database, with the same schema as the self-hosted server.
Everything in self-hosted, plus:
2M
events a month, included
Run the server on your own Cloudflare account and pay only your Cloudflare bill. The Workers free plan is enough to start.
Self-hosting guideHow sources are detected, what works on each platform, and how hosting and pricing work.
Each install gets one source on its first launch. On iOS the SDK reads Apple's AdServices token, which names the Apple Search Ads campaign, ad group and keyword. On Android it reads the Play Install Referrer. Smart links and campaign links are read from the URL the app first opened with. Everything else counts as organic. No advertising id and no App Tracking Transparency prompt are involved.
On Android, yes: the link travels through the Play install referrer, so the install is matched to the link exactly and getDeferredDeepLink() returns its destination. On iOS, the App Store passes nothing to a fresh install, and matching a click to an install would need device fingerprinting, which Apple does not allow. Those installs usually count as organic, or as Apple Search Ads if they came from an ad. When the app is already installed, the link opens it and is attributed on that first launch.
Through SKAdNetwork and AdAttributionKit. The config plugin tells iOS to send copies of the postbacks to Appeeky, and the SDK keeps the conversion value up to date. You see installs and outcomes by ad network and campaign. An app can name only one endpoint for these copies, so if another provider already receives them you can keep it with attributionEndpoint: false.
RevenueCat, through the webhook you already connect in Appeeky, and Superwall, through one webhook with a signing secret. Call Appeeky.identify() with the same user id you give them, and every trial, purchase, renewal and refund is matched to the install that made it. Revenue shows net of refunds, with the gross and refunded amounts next to it. You can also report ad revenue with adRevenue().
Yes. The server is source-available and runs as one Cloudflare Worker with one D1 database in your own account, so installs, events and revenue never pass through Appeeky. Features that need your connected ad accounts or Appeeky workspace — ROAS, ad signals, organic posts, and the co-founder and MCP tools — run only on the hosted service.
The hosted service is included in the Startup plan with up to 2M events a month. An event is anything the SDK sends: a session, a screen, a custom event. Installs are never metered. If you need more, write to us. Self-hosting is free; you pay your own Cloudflare bill.
React Native and Expo through one npm package, native iOS apps through Swift Package Manager, native Android apps through Gradle, and Flutter through pub.dev. All four SDKs send the same data, so attribution, revenue and the dashboard work the same way.
Yes. Android installs get the Google Play referrer, smart links with exact install attribution and deferred deep links, and TikTok Ads and Meta Ads ROAS through ad smart links. Apple Search Ads and SKAdNetwork are iOS only.
Events do, but Apple Search Ads, SKAdNetwork conversion values and the Play Install Referrer need the SDK's native module, which needs a development build. Add the config plugin and rebuild, for example with npx expo run:ios or an EAS development build.
Included in the Startup plan, or free on your own Cloudflare account. Add the SDK and see which sources pay back.