Kuala Lumpur · event dictionaries

A tracking plan your engineers can actually ship.

We sit with product, analytics, and one engineer per client, then write the event names, properties, and identity rules before anyone adds another tracker call. The document is the work.

Request a planning date

Colleagues in a bright office talking through papers at a long table — Working sessions at Wisma Shaw, and on product floors across the Klang Valley.

button_click

checkout_started

signup_success on three platforms

account_created, one name

raw search string on every tap

leave search out of the payload

The work

Schema planning for clean app event tracking

We do not sell software. We write the dictionary that iOS, Android, and web are supposed to share, then check the build against that dictionary when you ask.

Planner spreading paper notes and a printed inventory across a wooden table

Three to six weeks

Event Schema Planning

A written event dictionary for one app: names, properties, identity rules, and an engineering handoff that iOS, Android, and web can share.

How this engagement runs

Person reviewing printed tables and handwritten notes at a desk

Ten to fifteen working days

Tracking Plan Audit

A review of the events you already fire: duplicates, silent properties, and names that no longer match the screens they claim to describe.

How this engagement runs

Small team comparing notes around a laptop in a bright meeting room

One to two weeks after a build is available

Instrumentation Review

A pass through the live app to check that events fire on the trigger named in the plan, with the properties the dictionary allows.

How this engagement runs

People seated around a conference table during a working discussion

Half day (four hours) plus a written recap within three working days

Naming Workshop

A half-day working session that leaves the product squad with a naming convention and a first list of events they will actually keep.

How this engagement runs

Four people in discussion around a table in a loft-like meeting room — Discovery is a walk through the product, not a dump of the current export.

How a plan is written

Inventory first. Names second. Tracker calls last.

Most messy event lists begin as last-minute tickets. Someone needs a chart, an engineer adds a string, and the next squad copies the pattern. Schema Pulse Point reverses that order.

We list the actions a person can actually take in the current app and the next named release. We throw out clicks that only describe a control. We write properties that a QA session can still read. Then we hand engineers a sheet with the trigger for each client.

Read the method

From a grocery app in Petaling Jaya

Payments, fulfilment, and growth each had a different word for placing an order. After the dictionary, finance stopped asking which export was the real one.

From the client story on the stories page — Event Schema Planning

Journal

Notes on naming, properties, and version stamps

All entries

Open notebook with a handwritten checklist beside a cup of coffee

11 March 2026 · Aisha Rahman

Stop naming events button_click

If the name describes the control, not the action, the funnel dies the moment the designer moves the control.

Read the note

Close view of a person writing on lined paper with a black pen

1 April 2026 · Wei Liang Tan

Properties that drown the dictionary

Search strings, full SKUs, and concatenated timestamps look harmless in a test payload. In production they make every report a unique snowflake.

Read the note