First-party signals: naming events like you mean it

Good names encode object, action, and scope. Vague names like "engagement_event_v2" age poorly when analysts rotate.

Co-create a dictionary with engineering early. Marketing-only dictionaries drift within a quarter.

Add a deprecation note when you sunset an event. Ghost events confuse downstream teams for years.

KR teams often juggle English schema with Korean dashboards — pick where translation lives and keep it consistent.