Name the surface first
Before any SDK discussion we sketch the content object: issue, episode, card, chapter. Interaction tracking that starts in the event bus usually invents nouns nobody on the editorial floor uses.
Bangkok studio · content analytics
The click is loud. The pause is the story.
Model Cloudhub is a small teaching studio for teams who ship articles, shows, feeds, and learning modules inside apps. We train people to instrument content interaction tracking without drowning the warehouse in vanity events.
Most dashboards celebrate opens. We spend our weeks on dwell windows, return visits, skim signatures, and the quiet exits that actually change an editorial calendar.
Flagship track
Interaction Trace
An eight-week studio course on mapping how readers engage with in-app content. You leave with a taxonomy, a sampling plan, and a reporting shape that an editor can argue with — not a wall of charts.
Labs use anonymised session excerpts from news, audio, and long-form reading products. SQL is present, but the argument is always about the content surface, not the warehouse schema.
- 01Signal inventory: what counts as an interaction
- 02Event names that survive a re-org
- 03Scroll, dwell, and tap as mixed evidence
- 04Cohort windows for serial content
1,240
practitioners through Bangkok cohorts since 2019
28
event patterns dissected in the flagship lab
6
office-hour seats each week from Sai Mai
From recent desks
What people actually changed after class
After Interaction Trace we stopped counting “article complete” as 90% scroll. The module on mixed signals made us pair dwell with return visits, and the morning standup finally argued about chapters instead of pageviews. Waranya K., analytics lead · Chiang Mai newsroom app
The sampling week saved our feed from a 40-million-row bill. I still wish the SQL primer had arrived before week two. M. Ortega · client in subscription audio
★★★★☆
Taxonomy clinic on Event Sketch was dry in a useful way. We retired eleven ghost events that nobody could define. Ploy · Bangkok · product ops
Longer case notes live on the reviews page.
How the studio teaches
Four habits we insist on
Treat scroll as a rumour
Depth pixels are cheap to collect and expensive to believe. We teach when they corroborate a read and when they merely prove a thumb was moving.
Sample on purpose
High-volume Thai and regional feeds cannot keep every impression. Students design a sampling contract that still lets a weekly review find outliers.
Report in editorial time
A chart that updates hourly but is read on Monday is a lie. We map cohort windows to how the desk actually plans covers and push alerts.
Also on the shelf
Other programmes
Bring a content surface. Leave with a taxonomy you can defend.
Fees are published without a checkout. Write to the studio if you want a seat, an invoice, or a private run for a Bangkok or remote team.