The studio

Close reading for people who ship links.

Apipacketbase started as a private critique table in Phan, Bangkok: three growth leads, a printed payload dump, and an argument about whether a LINE sticker campaign should get credit for an install that happened the next morning.

Quiet office interior used for Apipacketbase studio sessions

Mission

Make attribution boring enough to trust.

We exist so Thai and regional product teams can defend a number without hiding behind a vendor’s default dashboard. App Analytics — Deep Link Performance Tracking is the craft: schemes, fingerprints, windows, and the social work of telling finance what a tap actually did.

We do not resell an MMP. We do not certify you on a console. We teach you to interrogate whichever stack your employer already paid for.

Pedagogy

Annotate first. Design second.

Every block opens with a real trace: click ID, store referrer, first-open timestamp, and the fallback page a carrier actually served. Students mark what is missing before they propose a new link template.

Evening cohorts in Bangkok run in English. Examples lean on Play Store hops, iOS Universal Links behind Thai Apple IDs, and QR codes taped to 7-Eleven coolers. Remote seats join the same critique, not a diluted recording.

Small group discussion around a table during a studio cohort

Community

A room that keeps the receipts.

Alumni stay in a quiet mailing list. We share redacted incident notes — never live credentials — when a partner SDK starts double-counting opens after a silent update. There is no public leaderboard and no “student of the month.”

If you need a louder community, this studio will feel too small. That is deliberate. Thailand already has large meetup calendars; we offer a table where a single mis-tagged campaign can take forty minutes.

Student journey

From first dump to a ledger finance will sign

  1. Arrival conversation You send a sample deep-link template and a question you cannot settle internally. We reply within two Bangkok business days.
  2. Placement Self-paced Signal Desk, live Attribution Atelier, or a private Cohort Chamber. We will refuse a seat if your stack is still a slide deck with no production links.
  3. Annotation week You read payloads aloud. Instructors interrupt. This is the uncomfortable part and the reason teams stay.
  4. Dashboard critique You present a cleaned view — windows labelled, exclusions named — to a sceptical guest (often a former finance partner).
  5. Aftercare Thirty days of written questions. No Slack noise. If a partner changes a referrer format, we add it to the next field note.

See what is on the catalogue