Event Naming Conventions That Prevent Data Decay

The Compounding Cost of Ad-Hoc Instrumentation

In rapidly growing engineering teams, application telemetry is often treated as an afterthought during feature sprints. One developer instruments user_signed_up, another creates Account Created, and a third registers auth:signup_success.

Within twelve months, product analysts are left with fragmented data tables, broken downstream dashboard calculations, and conflicting retention figures. This condition—known as telemetry data decay—destroys confidence in customer journey analysis.

The Object-Action (Noun-Verb) Architecture

To establish an immutable, intuitive event tracking taxonomy, Console Vertex Point enforces the Object-Action design pattern across all client codebases.

Every event name must consist of two fundamental components formatted in lower snake_case:

The Object (Noun): The entity, interface element, or lifecycle domain being acted upon (e.g., workspace, document, subscription, payment_method).
The Action (Past-Tense Verb): The verified state transition that just occurred (e.g., created, updated, submitted, failed, viewed).

Good vs. Ineffective Event Syntax Examples

Flawed Ad-Hoc Syntax	Standardized Object-Action Syntax	Rationale
`Click Search Button`	`search_query_submitted`	Tracks the state outcome rather than raw UI click.
`User Upgraded Plan`	`subscription_tier_updated`	Follows standard domain noun and precise state verb.
`error_modal_popup`	`error_dialog_displayed`	Eliminates ambiguity between trigger and presentation.
`kyc_step3_done`	`identity_document_uploaded`	Names the action rather than ephemeral screen index numbers.

Structuring the Context Envelope

Event properties should be logically segmented into global context properties (attached by SDK middleware) and event-specific domain properties.

{
  "event": "identity_document_uploaded",
  "timestamp": "2026-07-02T10:14:22.104Z",
  "context": {
    "app_version": "3.14.2",
    "platform": "ios",
    "locale": "en_TH",
    "network_type": "wifi",
    "session_id": "sess_94f82a10b"
  },
  "properties": {
    "document_type": "passport",
    "file_size_kb": 1840,
    "ocr_confidence_score": 0.96,
    "is_retry_attempt": false
  }
}

Establishing Engineering Governance

To prevent tracking decay as new engineers join your squad:

Maintain a Single Source of Truth Schema: Store event definitions in a version-controlled repository using JSON Schema or TypeScript interfaces.
Integrate CI/CD Telemetry Linting: Run automated schema validation in your pull request pipelines to reject unapproved event names or missing required properties before code merges into production.