Instrumentation · Field note
Device funnels without vanity counts
“Devices online” looks decisive on a Monday slide. It also resets every time firmware reboots a radio. This note is about building an activation funnel that still means something after an OTA.
In 2021 we let a cohort keep “online in the last 24 hours” as their north star for six weeks. The companion app looked healthy. Installers in Isaan were quietly re-pairing devices after every silent firmware bump, which counted as a fresh online event. The board thought activation was rising. It was churn wearing a green badge.
Activation is a first useful sample, not a login
For most connected products we see in Thailand, the first trustworthy product moment is not an account creation. It is the first sensor sample, valve command, or location ping that arrives with a firmware semver the ops desk recognises. IoT App Analytics has to start there, even if the mobile kit wants to start at sign-up.
Write the definition in the telemetry contract before anyone draws a bar chart. Example we now use in Device Signal Studio: activated means a device_id emitted a temperature sample with firmware_semver matching the installed SKU, within seven days of the installer’s completion event. Ugly sentence. Comparable across OTA.
Keep the funnel short on purpose
Mobile playbooks love seven-step funnels. Hardware funnels rot when they include screens the installer never opens. We ask teams to defend every step against a field visit: if a technician in Phra Khanong can complete the job without that screen, it is not a step. Three or four stages is typical: unboxed, paired, first sample, first week of samples.
OTA is a dimension, not an incident
When firmware changes, do not restart the funnel clock unless the hardware capability actually changed. Slice by firmware line instead. If version 2.4 dropped a required field, that is a contract break — treat it as a data incident, not as “users bouncing.”
The vanity count survives because it is easy to plot. The honest funnel is slower to explain in a meeting. That is the trade. Alumni who still open the firmware-cohort worksheets before Q3 reviews made that trade once and then refused to go back.
If you want the worksheets live, the Device Signal Studio syllabus is the long version of this argument. Desk Notes covers the definitions without the critique room.