Bangkok studio · Cohort 14

Plan the event. Then instrument.

Most product analytics stacks accumulate synonyms. A tap called checkout_start in iOS, CheckoutStarted on web, and begin_checkout after a vendor import. Apifeaturebase is a teaching studio for app analytics event schema planning: the quiet work of naming objects, locking properties, and agreeing a freeze before anyone ships a tracker.

Enter the Event Schema Atelier
Analytics charts on a laptop during a planning session
A tracking plan is a product artefact, not a spreadsheet leftover.

Studio note

We teach the contract, not the chart.

Dashboards forgive sloppy events for a quarter. Then a localisation pass, a new surface, or a warehouse join exposes three names for the same intent. Our pedagogy starts earlier than a vendor’s recommended event list. Students inventory the objects in the product — order, rider, note, wallet — and only then decide which actions deserve a name that will still read in 2029.

From Bangrak we run small cohorts for teams in Thailand and remotely. Alumni leave with a property dictionary, a deprecation window, and a review ritual that product, engineering, and data can actually keep. If you wanted a tool comparison or a crash course in SQL, this is the wrong door.

612student schema reviews marked in studio
187alumni across fourteen cohorts
2.4average freeze cycles before v1 lock
71%ship a written dictionary within six weeks

Flagship

The Event Schema Atelier

Eight weeks. One app surface. A dictionary you can defend in a product review.

Small working group around a table with notebooks

Cohort · ฿24,800 informational

Inventory, name, freeze, instrument

You will not implement a full analytics stack here. You will produce an object–action map, allowed values for every property, and a deprecation note that engineering can calendar. The atelier is deliberately slow on naming week; that is the point.

Read the syllabus

All programs

From recent cohorts

What people actually changed

These notes mention modules from this studio, not generic praise.

After week five I finally had a written deprecation window. Our checkout_started properties stopped drifting every sprint. Naming drills felt slow; I still think that week could be shorter, but the freeze ritual is what our PM kept.

Nalinee P., Chiang Mai · Event Schema Atelier

The property dictionary template from Taxonomy Studio is now the first artefact in our PR description. Designers stopped inventing event names in Figma comments.

Arthit Boonmee, Staff Product Analyst · ride-hailing, Bangkok

Boundaries

What we insist on, and what we leave out

Insist

  1. Object–action names that survive localisation into Thai and English.
  2. Allowed values listed before the first SDK call.
  3. A freeze date visible to product, not only to data.
  4. Identity and session events that do not double-count.

Leave out

  • Warehouse modelling, dbt, and reverse ETL.
  • Vendor bake-offs and pixel how-tos.
  • Growth-hack funnels dressed up as taxonomy.
  • Urgency timers, fake seats, or “limited cohort” theatre.

Notes from the desk

Recent writing

All notes

Bangkok & remote

If the taxonomy already feels noisy, write to the studio.

We reply within two working days. No automated waitlist.

Contact Apifeaturebase