Planning engagement
Tracking Plan Audit
Most apps we see in Kuala Lumpur already send hundreds of events. The problem is not volume. It is three names for checkout, properties that mean different things on iOS and Android, and a funnel that quietly died after a rename.
Who it is for
Teams who inherited an event list, or who have been adding tracker calls for more than a year without a shared dictionary.
What you leave with
An annotated inventory: keep, rename, merge, or retire. Each recommendation cites the screen and the conflicting name we found.
In scope
- Import of the current event and property lists
- Duplicate and near-duplicate clustering
- Property type and cardinality checks
- Identity and user-property review
- A retire / rename / keep table with owners
Included
- Written audit with a keep-rename-retire table
- Ninety-minute readout with product and analytics
- A one-page naming convention you can adopt immediately
Not included
- Rewriting the full tracking plan (that is Schema Planning)
- Changing tracker calls in the app
How the work proceeds
-
Collect the list
You export event names and property keys. We do not need raw user records.
-
Cluster and contradict
We group names that describe the same action and mark properties that collide across platforms.
-
Readout
You leave with a table, not a slide deck of principles.
Preparation
An export of event names, property keys, and (if you have it) the last known owner of each event.
Constraints
We audit one production app. Staging-only events are out of scope unless you ask in writing.
Next step
Send the export and a note on which funnel you no longer trust. We confirm whether an audit or a full plan is the shorter path.