On this page
Install Drengr Analytics
Add the dependency, call start() once, and the signals below arrive on their own. There is no event taxonomy to design first and no tracking plan to keep up to date.
Pick your platform
Flutter
pub.dev · drengr_flutter_sdk
iOS
Swift Package Manager · CocoaPods
Android
Maven Central · dev.drengr:analytics-android
Web
npm · drengr-js
What every SDK captures
You do not instrument any of these. They are captured from the moment start() runs.
| Signal | What it records |
|---|---|
| screen_view | Every screen or route the user lands on |
| tap | Taps, with the element's own label when it has one |
| net / net_fail | Outgoing requests: host, path, status, duration, size |
| crash | Uncaught exceptions with their stack |
| rage_tap / dead_tap | Repeated taps that did nothing — the friction signal |
| rage_scroll / dead_scroll | Scroll thrash and scrolls that moved nothing |
| app_foreground / app_background | Lifecycle, which is what sessions are built from |
| identify | Your own user id, when you choose to send one |
What never leaves the device
Emails, phone numbers, card numbers and government ids are detected and sealed on the device before the first byte leaves it. What our servers store is ciphertext they cannot open. Most autocapture tools promise not to look; this one is built so we cannot.
Not installing an SDK?
See what you’re missing first
Drop a .har of traffic you already have. Runs in your browser, nothing uploaded.
Point an existing pipe at us
Amplitude, Segment, GTM, server-side, or import your history.
Everything on one page
All four platforms in one document, for searching or printing.
Drengr Actuator
The MCP server that gives an agent eyes and hands on a real device.