A map of everything the SDK can send, grouped by how it is produced. Most of these fire automatically; the rest you report through the manual API.
Captured for you after init - see Automatic Tracking.
| Group | Events |
|---|---|
| Session context | app launch, platform, OS, RAM, screen resolution, system language |
| App lifecycle | app pause, app resume |
| Input | button click (Pressable), Android back button |
| Navigation | scene loaded / unloaded (via useKeewanoNavigation) |
| Deep links | deep link activated |
| Errors | error message (uncaught JS errors) |
| Network | internet connected / disconnected (opt-in) |
Reported by you through Keewano.report* - one short guide each:
| Group | Events | Guide |
|---|---|---|
| Windows | window open / close | Windows and Buttons |
| Progression | onboarding milestone, A/B test assignment | Tutorial Tracking |
| Attribution | install campaign, game language | Marketing Campaign |
| Purchases | product id, price, timestamp, items granted | In-App Purchases |
| Ads | ad offered, ad revenue, items granted | Ad Revenue |
| Subscriptions | revenue, items granted | Subscription Revenue |
| Economy | items exchange, items reset | Item Economy |
| Identity | user id assigned, pre-SDK registration date | Existing App Integration |
Events you declare yourself, on top of the built-ins. See Custom Events.
Note
A few identifiers exist in the protocol but are never emitted by this SDK because React Native has no equivalent API for them (for example GPU type and VRAM size). They are reserved so the wire format stays compatible across all Keewano SDKs.
Related: Automatic Tracking | Custom Events | Data Format