Flagship course
Attribution Architecture for App Growth
A seven-week lab for marketers and analysts who need Marketing Attribution for Apps systems that hold up under privacy change and budget pressure.
What you will leave able to do
Defend a measurement stack
Document why your MMP, store analytics, and warehouse joins exist — and what each cannot answer.
Choose windows with intent
Select lookback and re-engagement windows tied to your actual purchase latency, not vendor defaults.
Ship a SKAN value map
Draft conversion value schemes with product and finance, then stress-test them against sparse postbacks.
Brief agencies cleanly
Produce readout formats that separate modeled lift from observed clicks without burying caveats.
Module map
- Week 1 — Signal inventory. Catalogue events, partners, and dark social paths already influencing installs.
- Week 2 — Taxonomy surgery. Rename and prune events; write a living dictionary product engineers will keep.
- Week 3 — MMP configuration audits. Revisit postbacks, filtering, and fraud settings with a change log.
- Week 4 — Privacy-era constraints. SKAN, consent prompts, and what disappears when users opt out.
- Week 5 — Multi-touch realism. Compare last-click, position-based, and data-driven stories on the same cohort.
- Week 6 — Incrementality lite. Design geo or holdout tests that fit mid-market budgets.
- Week 7 — Executive narrative. Package uncertainty into decisions leadership can fund.
Instructor
Nalin Phoonthong
Former UA lead for regional lifestyle apps; now coaches teams from Panel Forgehub’s Phuket studio. Focus areas: SKAN scheme design and partner governance.
Informational pricing
THB 18,900 / learner
Includes live sessions, critique hours, and templates. No checkout on this site — request enrollment via contact. Team seats billed separately under Path Mapper or Full Forge plans.
See team plansFAQ
Do I need an MMP already?
Helpful but not required. Week three assumes you can access configuration screens or export docs; if you are vendor-shopping we adapt exercises to evaluation criteria.
Is this only for iOS?
No. Android and cross-store flows are covered, though privacy modules spend more time on Apple constraints because they reshape the rest of the stack.
What is a real limitation of this course?
We do not grant vendor certifications or promise a single “true” attribution number. If your leadership wants certainty theater, this curriculum will frustrate them — and that is intentional.
Time commitment?
Plan for roughly six hours weekly: two live hours plus applied homework on your own product.
Learner notes
★★★★★
Week six’s incrementality lite worksheet forced us to admit our “always-on” Facebook spend had never been tested. Painful, useful.
I wanted more SQL. The course stays conceptual on warehouse joins. Still, the SKAN critique sessions alone justified the seat.