★★★★☆
Warehouse week assumed BigQuery. We are on Redshift. I translated the type examples myself over a weekend. Still used the QA checklist on every release after that.
Arthit Phan · mobile lead, Chiang Mai
Reviews
What people said after they shipped the dictionary, not after week one.
These notes were collected after students had time to implement. We kept one mild reservation on purpose. If you want a sales page of unbroken praise, this is the wrong studio.
The forbidden-events list from Taxonomy Bench stopped our growth team adding hero_impression_v3. That alone paid for the seat in political capital.
N. · Ho Chi Minh City
Client in digital banking. Identity stitching module. We had been storing a hashed national ID on a client event “just in case.” The lecture made the legal team visibly uncomfortable, which was the correct outcome. We removed it before the next store review.
Anonymous · financial services
I came in thinking Instrumentation Studio would be SQL. It was mostly naming fights. That was what we needed. Our Mixpanel project had 400 events and 40 that anyone trusted.
Priya S. · analytics manager · Singapore
8.4 / 10 · cohort board
Clear on PDPA implications for in-app telemetry. A bit Bangkok-centric in the checkout examples — our app is ride-hailing — but the object model still mapped.
Farhan · Jakarta
Case study 01
Marketplace checkout, four apps, one object list
A Bangkok marketplace ran buyer, seller, logistics, and wallet apps with four separate tracking plans. Funnel reports disagreed on “order placed” by as much as 18% on the same calendar day.
Two Studio seats and a House Account workshop produced a single Order object with explicit states: draft, placed, paid, handed to logistics. Client events stopped carrying derived revenue. Warehouse models now read state transitions instead of guessing from page names.
Case study 02
Subscription app that blamed “drop-off” on the paywall
An education subscription product in Thailand saw a steep fall between trial start and first invoice. Growth had already rewritten the paywall copy twice.
Instrumentation Studio’s funnel-integrity week showed the trial_start event fired on screen view, while invoice_created lived only on the billing service. Users who never reached the paywall still looked like trial starts. After moving trial_start behind a confirmed entitlement flag, the “drop-off” halved — because half of it had never been a funnel.