Naming events so finance and product share one funnel

Analytics vendors love their own nouns. One calls a paywall view an “opportunity”. Another calls a successful charge an “subscribe”. Finance, meanwhile, speaks in invoices, refunds, and chargebacks. When those three dialects sit in one Bangkok meeting, the funnel becomes theatre.

Apiqueuegrid’s Event Ledger module starts on paper. We ask each pair to write five verbs only: seen, started, confirmed, failed, left. Everything else is a property. A family plan is not a new verb. A student discount is not a new verb. A restore-purchase is a started or confirmed with a source property, not a mystical sixth action.

Properties carry the Thai mess

Regional billing, bilingual screens, and promo codes belong in properties: partner_id, locale, sku_code, promo_flag. If you mint a new event name for every combination, you will never reconcile an export. Revenue Taxonomy Workshop exists because catalogues drift; the verb list should not.

Vendor changes should be boring

A healthy taxonomy is one you can re-implement in a new SDK over a long weekend without renaming the business. If switching tools requires a glossary the size of a novel, you did not name events — you named implementation details. That is the test we use at the end of Funnel Bench: could finance read last month’s packet if the logo on the dashboard changed?

None of this is glamorous. It is also the only way subscription funnel tracking survives the next reorg.

Back to the journal