Flagship studio · 6 weeks
Signal Without Identity
A live studio for product and data pairs who need app analytics after identifiers leave the warehouse. You rewrite one surface — usually onboarding or checkout — until the funnel still reads when consent is no.
Included as the primary program under a Cohort Bench seat, or as one of the five seats in Atelier Year. Signal Reader does not include this studio. There is no checkout on this site.
See seats Ask for datesLearning outcomes
- Publish an object–action event grammar that survives an SDK bump and a consent reset.
- Split at least one funnel by consent state without dropping declined users from the story.
- Define a cohort window from first-party timestamps only, and explain where it dies.
- Produce a 31-day deletion runbook counsel can attach to a PDPA memo.
- Run a weekly review with four panes: consented funnel, declined funnel, crash surface, deletion log.
Who should not enrol
Growth teams whose only question is paid UA attribution. We will not teach SKAdNetwork, MMP identity graphs, or fingerprint joins. If that is the brief, this studio will frustrate you on purpose.
Solo founders with no event stream yet may prefer Event Schema Craft first. Write the desk; we will say so.
Modules
- 01
First-party event grammar
Name objects and actions. Ban “user_did_x.” Version the list. Homework is a pull request or a warehouse migration note, not a quiz.
- 02
Consent as a dimension
Model consent state on every event that needs it. Practice rebuilding drop-off when a third of sessions arrive declined.
- 03
Cohort math without user_id
Windows from install or first meaningful action. You will likely watch a vanity retention number fall. We keep the lower one if it is true.
- 04
SDK surface and what to refuse
Inventory crash, engagement, and analytics kits. Cut fields that re-identify. Treat vendor shadow copies as your warehouse.
- 05
Reports legal can sit through
The four-pane weekly review. Product still argues about copy. Counsel can see that names are not in the room.
- 06
Desk critique
Live review of your taxonomy with Kamonwan. One surface must ship or be scheduled. Alumni hour starts after this week.
Instructor
Kamonwan Prasert
Studio Lead at Mindtracegrid. Previously ran first-party analytics for a Bangkok super-app and sat through enough PDPA reviews to stop treating identity as a default column. She still refuses vanity dashboards in critique.
Studio voices
“Module 03 is where our day-7 story died. We published 19% instead of 41%. Finance grumbled for a week. The board pack got shorter because we stopped explaining the fingerprint.”
★★★★☆The desk critique is blunt. I wanted a side-by-side with our old vendor funnel in week three and did not get it. Everything else held.
We only rewrote checkout. That was enough. Support still finds people when they write in. Measurement no longer pretends to.
FAQ
Does this studio cover paid user-acquisition attribution?
No. That is a real limitation, not a tease. We do not cover SKAdNetwork campaign optimisation, MMP identity graphs, or fingerprint-based paid joins. Growth reporting that depends on those tools stays off the first-party warehouse we teach. If paid UA is your only brief, do not enrol.
Can we use production data in class?
Only if counsel has cleared it. Otherwise we work in a sandbox with realistic volume. Several Bangkok teams arrive with production frozen; the sandbox still teaches the grammar.
How many people per seat?
Cohort Bench is one named person. A second colleague may observe silently if they share a screen. Atelier Year allows five named seats across the year.
What if we already took Event Schema Craft?
Bring that grammar. Module 01 becomes a short recap and we spend the extra time on consent splits and the deletion log.