Bangkok studio · app analytics

Name the tap.
Keep the trail.
Trust the ledger.

Mindagentbase trains product and data teams to instrument mobile commerce event tracking with the same care they give order records. We teach dictionaries, parameter contracts, and the awkward moments between a tap and a paid invoice.

Browse the programmes

A person reviewing a mobile storefront on a smartphone
“After the checkout lab, our catalogue team finally stopped arguing about whether begin_checkout belonged on the cart screen or the address screen. The schema document did more for stand-ups than another dashboard ever did.”
Nalinee P. · analytics manager, Bangkok fashion marketplace

Flagship programme

Checkout Event Instrumentation

A six-module studio course on naming, firing, and reconciling the funnel from view_item through purchase. You work synthetic Thai marketplace traces, not vendor slideware. The cohort includes a critique of parameter contracts and a ledger-matching exercise.

Informational fee: THB 18,500 per live seat. Recordings alone are listed separately on the fees page.

Open the syllabus

Customer completing a card payment at a checkout counter

What the studio actually teaches

Craft that survives a promotion weekend

These are the skills teams bring when a campaign spike makes last month’s “good enough” tracking unusable.

  • Event dictionaries with owners

    Every name, trigger, and required parameter gets a human owner. Ambiguous “click” events are retired in the first week.

  • PII fences before the SDK

    We map what must never leave the device — phone numbers in address forms, national IDs, free-text gift notes — before anyone pastes a snippet.

  • Funnel atoms, not vanity screens

    view_item, add_to_cart, begin_checkout, add_shipping_info, purchase. If your app skips a step, we document the skip rather than invent it.

  • Ledger reconciliation

    Purchase events are compared to order exports. Students learn to explain a 4–7% gap without blaming “the pixel.”

61 storefront schemas reviewed in studio critiques since 2023
14 wks typical span from first dictionary draft to a trusted weekly dashboard
9 maps Thai-language marketplace event references in the reading list
11 markets where alumni currently ship commerce events

Studio method

How a week in the room actually runs

Read the tap

We start with screen recordings and server logs, not a blank spreadsheet. Students annotate where intent actually changes.

Write the contract

Parameters, types, null rules, and firing windows are written as if another team will inherit them in six months — because they will.

Argue with the ledger

A purchase event that cannot be matched to an order id is treated as unfinished work, not a reporting footnote.

Field notes

Recent writing

All notes

Enquire

Tell us which funnel is lying to you.

Describe the storefront, the SDK, and the report nobody trusts. We reply within two working days. Fees on this site are informational only — there is no checkout here.

Write to the studio