“The SKAN lock-window module stopped us from publishing a Monday number that would have moved by Wednesday.”
Bangkok · App analytics faculty
Every install needs a paper trail.
Apiauditgrid teaches mobile attribution reporting the way a closing book is written: source by source, window by window, with a named owner for every discrepancy. Growth teams leave with tables that survive a finance review, not slides that only survive a stand-up.
2,140
weekly attribution memos marked in studio
11 days
median from first export to a finance-ready table
18
named source-of-truth conflicts we drill in class
From the room
What reporting looks like after the course
We already had an MMP. What we lacked was a written rule for when the store console, the MMP, and the invoice disagree. After The Attribution Ledger I still wish the sample files included more gaming titles — our catalogue is heavy on hypercasual — but the reconciliation worksheet is now the first tab finance opens.
★★★★☆
“Cohort Studio is slower than a vendor webinar. That is the point. You actually rebuild the join.”
Programmes
Flagship and companion studios
Each course is built around real export shapes: MMP CSV, SKAN postback logs, and cost files from the networks you actually buy.
The Attribution Ledger
Reconcile MMP, store console, and spend. Write the weekly memo finance will actually keep.
SKAdNetwork Postback Studio
Conversion values, lock windows, and what a null postback is allowed to mean in a board pack.
Cohort & LTV from Attribution Files
Build retention and contribution tables from the same export you already trust for install counts.
What changes
Reporting habits we insist on
App analytics without a named source of truth is just a mood. We train the unglamorous parts of mobile attribution reporting: windows, joins, and the sentence you write when two systems will never match.
- 01Window before metric. Every number in class carries its lookback, reattribution rule, and SKAN lock state.
- 02Cost joined last. Revenue and install claims are settled before ROAS is allowed on a slide.
- 03Disagreement is documented. MMP versus store console is a line item, not a hallway conversation.
- 04Thailand buying context. VAT on media invoices, late network files, and regional SKAN sparsity are part of the exercises, not footnotes.
How the studio works
Small rooms, marked homework, no live MMP logins
Sessions run from our Klongtoey studio and online. You bring exports from your own stack when you can; we supply anonymised packs when you cannot. Faculty mark the weekly attribution memo the way an editor marks copy — line comments, not a score out of ten.
We do not take admin access to your MMP. That boundary keeps student data out of our systems and keeps the teaching honest: if you cannot explain the table from a file, you do not yet own the number.
Insights
Notes from the reporting desk
SKAN windows when Thai iOS volume is thin
Sparse postbacks are not a reporting failure. They are a sample. Here is how we write that into a weekly memo without pretending the nulls are zeros.
When the MMP and the store console refuse to agree
A working tolerance, a named owner, and the three causes we see most often in Southeast Asian catalogues.
Next intake
Bring an export. Leave with a ledger.
Informational pricing only. Enrolment is arranged by note, not by checkout.