Classification happens on the receiving server before the event enters the queue. A known app marker takes precedence over the embedded Chrome/Safari rendering engine. Browser/app name, version, operating system, OS version, and device class remain separate fields.
Examples include WeChat on Android or iOS; WeCom, QQ, Alipay, Weibo, Douyin, Taobao, Baidu, Bilibili, and Xiaohongshu; Instagram, Facebook, X/Twitter, TikTok, LINE, LinkedIn, Reddit, and other apps that include a recognizable marker. Xiaomi, OPPO/HeyTap, Vivo, Huawei, Samsung Internet, and UC browser markers identify the browser itself.
{
"site_id": "example.com",
"metrics": ["visitors"],
"date_range": "day",
"dimensions": ["visit:browser", "visit:browser_version", "visit:os"],
"pagination": {"limit": 100, "offset": 0}
}
An app may omit its name from the User-Agent or open the external system browser. Evumi does not infer an app from a referrer, device manufacturer, or an unmarked Chrome/Safari string. Unnamed mobile WebViews remain “Mobile App”. Explicit HarmonyOS/OpenHarmony markers identify HarmonyOS; a Huawei device name alone does not.
Electron has precedence over embedded app and Chromium markers and is recorded as Electron + its Electron version, alongside its desktop OS. App versions are recorded only when the client exposes them reliably.
These classifications apply to newly received events. Existing records are not guessed or rewritten from incomplete historical data.