Notes
From walks we have already done
These pieces are written from instrumentation reviews: a missing revenue event, a consent dialog that swallowed first_open, two SDKs announcing the same screen. They are not general essays about “being more analytical.”
-
Walking checkout with the debugger open
How we actually sit with a release candidate: a test wallet, two devices, a proxy, and a printed journey, not a gallery of charts.
Arjun Menon
-
Name the event after what the person did
Button copy changes. The human action does not. Event names that quote the label on the button rot the first time a designer rewrites the CTA.
Lim Wei Shan
-
Two screen_view events, one screen
Firebase and a second SDK both firing screen_view on the same Android activity doubled every step of a funnel without doubling the number of people.
Nur Aisyah binti Rahman
-
Consent on first open, and the events that never leave
An Android first-open event that fires behind a consent dialog is not a first-open event. It is a delayed one, and it quietly breaks every cohort that starts on day zero.
Arjun Menon
-
When purchase_success never left the phone
A Kuala Lumpur subscription app kept a healthy paywall view count and a dead revenue event. The cause sat one screen later than anyone was looking.
Lim Wei Shan
