When two languages share one event name
English and Bahasa Malaysia copies often collapse into a single “campaign_open” row. That convenience is how push notification analytics lose the language that actually got tapped.
A ride-hailing team in our workshop sent the same promo in English and Bahasa Malaysia, then wondered why “the BM version underperformed.” The export had one event: promo_may_open. Device language, copy identifier, and even the deep link differed. None of that survived into the row the analyst received.
Fixing it is not a philosophy. It is a suffix: _en and _ms, or a copy ID that the writer already uses in the CMS. Until that exists, you cannot honestly retire a language.
We would rather see a slightly uglier glossary than a confident chart that has already mixed the two lock screens.