Custom field note
User Acquisition Cost Analytics, as a ledger rather than a tile.
This page is the studio’s working map: what we mean by UAC analytics, which artefacts we insist on, and where teams in Thailand usually get stuck. It is not a product page. Courses sit next door.
A definition we will defend
User Acquisition Cost Analytics is the practice of turning paid and partnership spend into a cost per acquired customer that survives three rooms: media, finance, and whoever owns retention. If only one room recognises the number, it is not analytics yet — it is a screenshot.
At Mirror Flowcore the practice has four artefacts. A join key that exists in the ad account and the warehouse. A window policy written in dates, not vibes. An incrementality stance (what you will test, and what you will not pretend to know). A fatigue watch, because creative decay masquerades as rising efficiency until contribution margin files a complaint.
Where Bangkok teams usually stall
- Checkout lag treated as a tracking bug COD and bank transfer push recognised revenue past the 7-day dashboard. The cost did not get worse. The window was wrong.
- Platform lift studies used as finance evidence A vendor study can inform a test design. It cannot replace a holdout you can describe to internal audit.
- Blended CAC that hides search harvesting Brand terms and Line chats absorbing prospecting spend will flatter any tile until you split the ledger.
What we refuse to call analytics
A single last-click CPA exported on Monday. A “true CAC” invented by multiplying a platform number by a secret factor. A model that cannot show its join. Those can still be useful hunches. They are not User Acquisition Cost Analytics in the sense this studio teaches.
If you want the curriculum that operationalises this map, start with the CAC Measurement Studio. If you only need a written verdict on your current file, book a Ledger Review from Pricing or write via Contact.