Start monitoring in 5 steps
No tester marketplace — you bring testers, Dozenflow shows activity.
This is the shortest path to see real closed-test telemetry from anyapp (your app under test) in the Dozenflow organizer app.
-
Install Dozenflow
Get the organizer app on your device. You use it to create tests, activate campaigns, and read stats — testers do not need it for basic telemetry.
Where: Google Play closed testing · dozenflow-closed-test group
-
Create a test
Sign in and create a draft. Set the
applicationIdof anyapp — the APK your testers will install.Where: Dozenflow mobile app
-
Add the Closed Test SDK to anyapp
Add the Maven dependency, optional
publishable_keyin the manifest, and ship a closed or internal test build.Where: Android Studio · SDK integration guide
-
Enable ingest and activate
On the test card, turn on keyless ingest (Base mode) or register a
pk_live_…key (Advanced). Then tap Activate. Package verify via Play Console is recommended but optional — you can activate first and verify later.Where: Dozenflow mobile app
-
Recruit testers and monitor
Distribute anyapp through your channel (Telegram, email, Play internal track). When testers open the app, sessions appear in Stats and the 12×14 campaign window after activation.
Where: Dozenflow mobile app · optional read-only view on this site
What you'll see
- First signal: a successful
POST /v1/initafter a tester opens anyapp — then session events in Stats. - Daily picture: active testers, session counts, and short-session flags.
- Campaign: quorum, streak, and phase toward Play's 12 testers × 14 days rule (after activate).
- Remind: push to participants who installed Dozenflow (not to anyapp alone).
anyapp ≠ Dozenflow. Testers install your APK; organizers use Dozenflow to monitor. Dozenflow does not find testers for you.