Method
Paper on the table before a single tracker call.
This is the sequence we use for event schema planning. Audits and reviews borrow pieces of it. A workshop is the naming slice, run in one morning. If you want the full dictionary, this is the path.
-
Walk the product as a person would
We do not start in the export. A product owner takes us through the current build on a test account. Each tap that might become an event has to correspond to something a person meant to do: place an order, choose a slot, pay, open a locker. Screens that only display state stay as screens. Internal staff PINs stay out of the customer dictionary.
-
Write the inventory, including refusals
Actions are sorted into events, screens, and a parking lot. The parking lot is for features that do not exist yet. High-cardinality fields — search strings, full SKUs, formatted timestamps — are marked forbidden before anyone argues that they might be useful. Curiosity events on every tooltip wait for a later version of the plan.
-
Lock names, properties, and identity
Names follow object_action in the language the three clients already share, usually English. Click, tap, submit, success, and done are banned as event names; they may appear as properties when a layout test needs them. Identity is written once: anonymous, signed-in, and how a session should stitch. User properties do not repeat on every event.
-
Handoff sheets, then a version stamp
iOS, Android, and web receive the same event names and different trigger notes. A blank is allowed when a client cannot fire yet. The plan is stamped v1. A change of meaning later is a new event or a definition property, not a quiet overwrite. Last quarter’s funnel keeps a name it can still be called by.
What this is not
It is not a catalogue of tracker vendors. It is not a weekly reporting retainer. It is not permission to put identification numbers in a payload. Priya will send a draft back if two platforms still disagree on the person’s action.
If you already have hundreds of names, the method still starts with a walk, but we cluster the export first. That is the audit, and it can feed schema planning without repeating the clustering.
Ask for a date
Bring the app name, whether events already fire, and who will own naming disputes. We will tell you which engagement fits and hold a first morning with a deposit.