Flagship program

The Event Schema Atelier

A cohort for people who own the tracking plan — PMs, analytics leads, and the engineer who will actually call the SDK. You leave with a freeze-ready dictionary for one app surface, not a certificate wall.

8 weeks · Bangkok evenings or remote morning block · ฿24,800 informational

Team reviewing documents during a workshop

Outcomes

What you can defend after week eight

  • An object inventory for one product surface, including the objects you deliberately ignore.
  • Object–action event names with a written rationale for every exception.
  • A property dictionary: type, allowed values, null policy, and owner.
  • Identity and session rules that stop double-counting on resume.
  • A versioning note and a deprecation window product has signed.
  • A review ritual that fits a normal sprint, not a separate “analytics guild.”
  • A freeze checklist used before instrumentation begins.
  • A short aftercare plan for the next surface that ships.

Modules

Eight weeks, one surface

  1. Inventory before invention

    Walk the app as a user. List objects. Mark which actions are product-meaningful versus telemetry noise. No naming yet.

  2. Object–action naming that survives localisation

    English and Thai labels, screen vs component events, and the boring consistency rules that prevent a third synonym appearing after a rebrand.

  3. Property dictionaries and allowed values

    Types, enums, free-text exceptions, and who is allowed to add a new value without a review.

  4. Identity, sessions, and events that must not duplicate

    Anonymous to known, background resume, and the two events almost every mobile app fires twice by accident.

  5. Versioning and deprecation windows

    How long dual-write lasts, who owns the calendar, and what “deprecated” means when a dashboard still depends on the old name.

  6. Review rituals with product and data

    A 25-minute review, a single comment thread, and a freeze vote. Not a committee.

  7. Freeze, document, instrument

    The handoff package engineering actually opens: dictionary, examples, and out-of-scope list.

  8. Aftercare when a new surface ships

    How to extend without reopening every name. Guest critique of two student dictionaries.

Instructor

Portrait of instructor Kwanjai Srisawat

Kwanjai Srisawat

Kwanjai spent nine years in product analytics inside Bangkok consumer apps before opening the Apifeaturebase desk. She still reviews student dictionaries line by line. She does not teach warehouse modelling and will send you elsewhere if that is what you need.

Informational price

฿24,800 for the atelier

Includes live sessions, written critiques on two drafts, and the dictionary template used in studio. There is no checkout on this site. Write to us to reserve a seat for the next Bangkok or remote block.

Enquire about enrolment

Other formats live on pricing.

Questions we actually get

Do we implement trackers in class?

No. Instrumentation is homework against your own codebase or a sandbox you already have. Class time is for the contract.

Can three people from one company join?

Yes, and we prefer it. Product, engineering, and data in the same cohort argue less after week three. Each person still needs their own enrolment note.

What is the real limitation of this program?

We do not cover warehouse modelling, dbt, identity resolution vendors, or dashboard design. The atelier stops at the event contract. If your pain is a messy BigQuery layer, this will not fix it.

Is there a certificate?

We issue a letter confirming completion and the surface you documented. We do not sell badges.

Alumni notes

The identity module caught a double fire on Android resume that our vendor’s default plan never mentioned. I still found week two’s naming drills repetitive, and I would rather have spent that time on deprecation. The freeze vote with our PM was the artefact that survived.

Mira K., product manager · fintech, Bangkok

★★★★☆ · 4.2 · cohort survey

“Dictionary template is usable. Live critique was stricter than expected. Would have liked more Android examples.”

Anonymous response · Event Schema Atelier, cohort 12

We brought a grocery checkout flow. After the atelier the event count dropped from 38 to 19 on that surface, mostly by killing screen_view clones. Kwanjai refused to let us name an event after a Jira ticket, which annoyed engineering for a day and then saved us.

client in grocery delivery · Thailand