Flagship · 11 weeks
Instrumentation Studio
Live cohort for teams shipping events into a warehouse. Taxonomy, identity, QA, and a public schema review.
Charoennakorn studio · Bangkok
Dashboards only tell the truth if the events were honest.
Socket Nodehub trains product, data, and mobile teams to design In-App Event Tracking Analytics that survive renaming, identity changes, and a new warehouse vendor. We start with the payload, not the chart.
This season’s desk
Programs currently on the board
Self-paced
Atlas Reader
Recorded lectures and naming worksheets. Useful before a redesign, or when only one engineer can attend live.
Org desk
House Account
A retained instrumentation desk for multi-app companies that need a shared dictionary across brands.
From recent studios
People who sat in the schema clinic
Each note points at a module on this site, not a generic “bootcamp feeling.”
“Week four’s checkout clinic was slower than I wanted — we spent two sessions on one funnel — but I still pull that worksheet when a PM asks for ‘just one more event.’”
Mira D. · product analytics, Manila · Instrumentation Studio
The identity lecture finally explained why our guest checkout row never joined the logged-in order. We had been blaming the warehouse load.
Client in grocery delivery · Bangkok
Numbers we actually count
17graduated studio cohorts since 2019
1,286event dictionaries reviewed in clinic
63product teams across Southeast Asia
Week 6when most inherited schemas quietly break
What the work actually is
Tracking is a design problem with SQL consequences.
We do not teach dashboard cosmetics. Students leave able to argue for a property, refuse a vanity event, and write a QA checklist a mobile engineer will actually run.
- Object–action naming that survives a rebrand
- Identity graphs that do not over-collect
- Funnel integrity before the BI tool is blamed
- Warehouse-ready types, nulls, and late events
Why Bangkok
The office sits on Charoennakorn. The examples come from SEA apps.
Marketplace checkout, ride-hailing surge flags, wallet top-ups, and bilingual property names show up in class because they show up in the region. Visiting students join from the studio or remotely; the dictionary still has to work in Thai and English clients.
Journal
Field notes, not recap posts
Event naming that survives a rebrand
Why button_click dies on first redesign, and how object–action pairs hold up when marketing renames the screen.
Identity stitching without over-collecting
Guest-to-user joins that respect PDPA expectations, and the fields we refuse to put on the event.
If you already have a tracking plan
Bring the messy version. That is the better starting point.
Write to the desk with a screenshot of the current dictionary, or sit in on a syllabus walkthrough. We answer within two working days.