Core concepts
Organization
Section titled “Organization”Your company’s account in Cimka. The team, applications, data, settings and wallet all belong to an organization. One person can be a member of several organizations with a different role in each, and switch between them from the dashboard header.
Application
Section titled “Application”One mobile app (one package id) registered in an organization. Each application has its own:
- Application ID — identifies the app.
- SDK API Key (
cmk_…) — authenticates the SDK. Shown once when you register the app. - Data collection settings — an SDK master switch plus nine log-type toggles.
All applications in an organization share the organization’s License Key, which the SDK uses to sign requests. The three values go into cimka_config.json.
An application is active (in development) or live (published, with a store URL).
Session
Section titled “Session”One run of your app on a device, from coming to the foreground until it goes away.
| Status | Meaning |
|---|---|
| Live | The app is in use right now |
| Sleeping | The app is in the background |
| Ended | Closed, or inactive for more than 10 minutes |
A session with 1–5 errors is flagged Warning; more than 5 is Problematic. Starting a new session costs €0.10 from your wallet.
Events
Section titled “Events”Everything the SDK records is attached to a session:
| Event | Example |
|---|---|
| Lifecycle | App launched, went to background, Activity resumed |
| Screen view | Home → Checkout |
| Interaction | Tap on checkout_button in Cart |
| Network call | POST /v1/orders → 201 in 184 ms |
| Trace log | error [Checkout] Payment failed |
| Crash | NullPointerException on the main thread |
Crashes with the same message and origin are grouped into one issue, with an event count and first/last seen times. An issue is open, resolved, ignored or regressed (resolved, then seen again).
Release
Section titled “Release”An app version, registered automatically the first time a session reports it. Each release shows its crash-free rate (Excellent ≥ 99%, Good ≥ 95%, Fair ≥ 90%, Poor below) and the libraries it ships.
App user
Section titled “App user”An end user of your app, identified by the value you pass to Cimka.identify(). Sessions without one appear as anonymous / “Not logged in”. Not to be confused with dashboard team members.
Device
Section titled “Device”A phone, tablet or emulator running your app, identified by a random id generated by the SDK. Each device is flagged Rooted, Simulator, Corrupted (tampered system) or Clean, and can be blocked — the app then shows a blocked screen with your organization’s contact details.
Masked properties
Section titled “Masked properties”Header names and JSON keys (e.g. password, token, card_number) whose values are replaced with [MASKED] in logs. Every organization starts with a default list you can extend.
Wallet
Section titled “Wallet”A prepaid euro balance per organization. Sessions and paid AI analyses are charged to it — free credit first, then paid balance.