Flagship · 12 weeks · ฿48,900
Signal to Send
A working lab for CRM and product operators who need app analytics that explain push notification performance — not a tour of every chart your ESP already offers.
Who this is for
You already send. You can export a campaign report. You are tired of defending open rate in a Monday meeting. Engineering is not going to staff a full-time analyst for notifications this quarter.
You should not enrol if your primary channel is email, SMS, or in-app messages. The lab is push-only on iOS and Android, with a short appendix on web push that we deliberately do not grade.
Modules
Six blocks. Each ends with a worksheet on your live catalogue, reviewed in a small group.
Lifecycle events that actually fire
Accepted, queued, delivered, rendered, opened, influenced, unsubscribed. We map vendor names onto one shared vocabulary so FCM, APNs, and your ESP stop arguing in the same spreadsheet.
Delivery, render, influence
Three different questions. Module 2 is where most teams discover their “reach” includes messages that never appeared on a lock screen.
Quiet hours and local clocks
ICT evenings, provincial morning peaks, Songkran and New Year leakage. Time-to-open is taught as a distribution, not an average.
Token health
Invalid, unregistered, canonical-ID churn after OS updates. You will leave knowing which failures are CRM’s to clean and which belong with mobile engineering.
Sequences without fake lift
Holdouts you can run in a mid-size ESP. Ghost-control windows when true randomisation is blocked. How to brief product when a “win-back” steals from a receipt.
A report two teams can sign
The closing artefact is a one-page definition of influence plus a weekly operator view. Finance does not have to love it; they have to understand it.
What you should be able to do afterwards
- Name every stage in your delivery funnel using language product and CRM share.
- Spot quiet-hour leakage on a Bangkok-heavy audience without a data-science ticket.
- Separate token expiry from copy failure when a campaign “under-delivers”.
- Design a holdout for a three-message sequence using only ESP features.
- Write an influence definition that survives a finance review.
- Brief engineering on which error codes are actually actionable.
Instructor
Nalinee Srisuk
Nalinee led CRM analytics for a Thai super-app before founding the Apieventgrid desk. She still reviews every Signal to Send worksheet herself. Guest sessions with Krit Wongsawat cover token APIs when a cohort has deeper engineering access.
Enrolment, informational only
A Cohort Seat for Signal to Send is ฿48,900 including worksheets, two live reviews, and twelve weeks of studio access. Desk Audit and Operator Circle options sit on the pricing page. There is no checkout on this site — write to the desk to reserve.
Questions we actually get
Do we need a data warehouse?
No. Exports from your ESP plus a spreadsheet are enough for the graded work. If you have BigQuery or a similar store, module 5 can go further, but it is not required.
Is web push covered?
Only as an ungraded appendix. Several token and render modules assume a mobile OS. If your catalogue is mostly desktop web push, Quiet Hours, Loud Data is a better first programme.
What is the real limitation?
We do not teach in-app messaging, email, or SMS. We also cannot rewrite your ESP. If your vendor cannot expose render events, module 2 will stop at a documented gap rather than inventing a proxy that looks scientific.
Can more than one person from a company join?
Yes, up to three seats per company per cohort, so the worksheet conversation stays specific. Operator Circle is the better fit if you want a year of reviews after the lab.
After the lab
“I came in thinking token errors were engineering trivia. After module 4 I could finally explain a 9-point delivery drop the week iOS rotated certificates.”
Rated 8/10 on the internal LMS note: “Clear on incrementality. Still wish module 4 assumed less backend access — we borrowed an engineer for two afternoons.”
Ask about this cohort
Tell us which app you send from and what your current report looks like. We reply within two working days.