Flagship
Signal Pipeline Fundamentals
A working sandbox from ingest to alert. You leave with a written instrumentation plan, not a vendor pitch. The generator is synthetic on purpose — production keys stay off our floor.
Bangkok · App analytics atelier
Watch the event as it happens — then decide what it meant.
Agent Gridhub teaches App Analytics through Real-Time Event Monitoring: taxonomy, sampling, SDK latency, and alerting that a night-shift engineer can still trust at 02:10.
2,180practitioners through live labs since 2019
37shipping apps using the taxonomy worksheets
11 minmedian time-to-first-dashboard in the flagship lab
4.3 / 5last Bangkok evening cohort, unprompted scores
SDK Instrumentation Studio
iOS, Android, and web hooks that survive a release train without doubling payload size.
Funnel Integrity for Product Teams
Keep conversion events honest when marketing renames screens every sprint.
From a 2025 pair
A travel marketplace stopped trusting a live funnel during ship week
A PM and an iOS lead from a Bangkok travel app sat Funnel Integrity, then stayed for Stream Alerting Without Page Fatigue. Their live funnel collapsed every Thursday deploy. The dwell window was missing; canary users looked like drop-off. They pinned alerts to app version and stopped paging on step-through wobble.
They still ship on Thursdays. The siren does not. The weekly taxonomy review they added afterwards is theirs, not ours.
How the room works
Small cohorts, paper first, then the stream
Write the contract
Every seat starts with a one-page event contract: name, trigger, required properties, owners. No dashboard until the page is boring enough to defend.
Run a dirty stream
The lab generator is intentionally messy — duplicate taps, late batches, missing user ids. You practise reading residue, not a polished demo reel.
Defend an alert
On the last evening you present one page and one rule to the room. If the rule would wake a stranger, it does not ship.
What you take home
Skills that survive the next vendor change
Taxonomy that a new hire can read
Naming rules, versioning, and a kill process for zombie events. Useful whether you stay on your current stack or not.
Sampling without hiding outages
Head-based and tail-based sampling patterns, plus when not to sample payment and auth paths at all.
Latency budgets for mobile SDKs
Where the queue lives, what blocks first paint, and how to prove a flush policy to a sceptical iOS lead.
Alerts a human can explain
Thresholds tied to user harm, not chart aesthetics. Quiet hours and escalation that match a Bangkok on-call rota.
Voices from the studio
Not every seat was a standing ovation
“Office hours on Suriwong were more useful than the flagship’s first evening, which I already knew. Bring an incident write-up, not slides. We left with a kill date on three zombie screen_view names marketing still loved.”
Estate License for twelve. Quiet-hours copy now names Chiang Mai and Bangkok instead of a global siren. I wanted the warehouse day included in the license; it was extra. Three stars from finance, five from on-call. Split the difference: we will renew the office-hour tables, not the full floor, next year.
“Latency Budgets for Mobile SDKs — the note, then the studio — is what I hand iOS leads before they argue flush. The mid-range Android in the cupboard is petty and correct.”
Next evening cohort
Nineteen office-hour seats remain on the Bangrak calendar
Fees are informational; there is no checkout on this site. Write to the desk if a pair or a floor should sit together.
Ask the desk