Flagship programme

Checkout Event Instrumentation

Four weeks, eight live sessions, synthetic Thai marketplace traces. You leave with a written dictionary, a parameter contract, and a purchase-to-order gap you can defend in a finance meeting.

Signal Desk · THB 18,500   Field Notes · THB 4,900

Shopping bags on a wooden surface beside a phone

Who it is for

Product analysts, mobile engineers, and revenue-ops partners who already have an SDK in the app and cannot explain why purchase counts disagree with the order ledger. You should be able to read JSON. You do not need to own the release train.

Teams still choosing a vendor should wait. This programme assumes a storefront exists.

Learning outcomes

  • Write an event dictionary with a named owner for each commerce atom.
  • Specify parameter types, null rules, and firing windows for checkout.
  • Fence PII on address and payment screens before payloads leave the device.
  • Reconcile a purchase sample against an order export and document the residual gap.
  • Explain a promotional coupon parameter without breaking item revenue roll-ups.

Modules

  1. 01

    Dictionary hygiene

    Inventory every custom event that claims to be “commerce.” Retire duplicates. Assign owners. Produce the one-page map the rest of the course will edit, not replace.

  2. 02

    Funnel atoms

    view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info, purchase. We document real skips (for example, buy-now that bypasses cart) instead of forcing a textbook funnel onto the binary.

  3. 03

    Parameter contracts

    currency, value, item_id, item_name, quantity, coupon, affiliation. Type rules, Thai baht formatting, and what happens when a guest cart has no user_id.

  4. 04

    PII fences and SDK timing

    Address fields, gift notes, and national ID prompts. Also: when the SDK initialises relative to first paint, and why late init drops begin_checkout on slower Android devices.

  5. 05

    Ledger reconciliation

    Match purchase events to a synthetic order export. Classify gaps: duplicate fires, missing guest checkouts, timezone drift, refunds posted after the event window.

  6. 06

    Critique lab

    Each student presents one storefront dictionary. The room argues. Graduation artefact is the revised document plus a one-page gap note for finance.

Instructor

Portrait of instructor Kamonchanok Saetang

Kamonchanok “Mon” Saetang

Former analytics lead at a Bangkok marketplace operator. Mon spent six years reconciling campaign dashboards with warehouse invoices before joining Mindagentbase as studio faculty. She teaches the ledger lab and reviews every Signal Desk dictionary in writing.

Guest privacy reviewers join module 04 when a cohort includes pharmacy or insurance add-on storefronts.

Informational fees

Signal Desk live seat: THB 18,500. Field Notes recordings of the same modules without critique: THB 4,900. Amounts are published for budgeting. Enrolment is arranged by email; this page does not charge cards or issue invoices automatically.

VAT, if applicable, is stated on the offline enrolment note. See studio fees and the refund notice.

Ask about a seat

FAQ

Does the programme include a production SDK or marketplace access?

No. That is a real limitation, not fine print. You will not receive a tracking snippet, a Shopee or Lazada partner key, or any live merchant data. Labs use synthetic checkout traces and publicly documented event dictionaries. Teams expecting a drop-in implementation still need their own engineering sprint afterward.

What language are sessions in?

Live critique is in English. Thai examples appear in reading and in parameter names when a storefront’s UI is Thai-first. Homework may be submitted in either language.

How much time outside class?

Plan three to five hours weekly. The ledger exercise in module 05 is the heavy week. Managers who only attend live sessions without homework do not receive a written dictionary review.

Can two people from the same company share a Signal Desk seat?

No. One seat, one dictionary review. If several people need to sit in the room, Catalogue Studio is the correct format.

What past seats said

Module 03’s null-rule worksheet stopped our Android client from sending value as a string during guest checkout. Finance noticed the same week. I wanted more LINE mini-app coverage; we mapped that internally after the cohort.

Arthit S. · product analytics

8.1 / 10

The critique lab is slower than a vendor workshop and more useful. Bring a dump that is actually redacted. Mine still had phone numbers in shipping notes and we lost twenty minutes to that.