Families before pixels
We group intents (progress, transact, notify) before anyone debates vendor properties. The grid becomes the contract between product, data, and engineering.
Studio notes · Stronvar, United Kingdom
Name the event once. Teach the app to keep using that name.
Auditmatrixgrid runs programmes in Event Taxonomy Planning for Apps. We treat catalogues as editorial work: families, verbs, objects, and properties agreed before a single tracker ships.
Familyonboarding.progress
Objectcheckout.basket
Verbcontent.opened
Statesession.resumed
From recent cohorts
What people noticed after the naming work
The Event Family Studio forced us to kill three overlapping “tap” events. Dashboards finally matched what support hears on the phone.
I liked the property dictionary more than the lectures. One caveat: if your engineering calendar is already locked, the homework will slip — we had to postpone week four.
Flagship programme
Event Family Studio
Six weeks of live mapping for consumer and B2B apps. You leave with a versioned catalogue, a naming RFC, and a list of events that should never have been instrumented.
Maeve Croft runs the critiques. Places are capped so every team presents an actual schema, not a slide about “best practice”.
Open the studio syllabus
Why teams book a grid before they buy another SDK
Properties with owners
Each key in the dictionary has a steward, a type, and a retirement date. Orphaned “user_type2” fields are treated as defects, not folklore.
Audits you can re-run
The method includes a quarterly pass against production event volume so unused names get archived instead of cloned under a new spelling.
63 app catalogues redrawn
18 closed teaching cohorts
7 naming layers in the house model
11 wks longest in-house mapping
From the notes
Recent writing on catalogues
Planning
When to split an event family
A rule of thumb for product teams who keep adding suffixes instead of admitting the object changed.
Naming
Naming conventions that survive a rebrand
Keep vendor-neutral verbs so marketing can rename screens without exploding Mixpanel.
Bring a messy tracker list. Leave with a grid.
If you already have 400 event names and no owners, start with a conversation rather than a new implementation. The Stronvar studio answers within two working days.
Write to the studio