telemetry-events
Telemetry events
Choose the minimum collection scope that answers the named question.
| Mode | Scope |
|---|---|
| off | no product telemetry |
| funnel-only | session and named funnel milestones |
| domain-events | explicitly approved gameplay/economy/reliability events |
Event schema
Each event type has a stable name plus schema_version. Define field names/types, timestamp/clock semantics, session/account/device identifiers at the minimum necessary granularity, environment/build version, and provenance such as QA/capture status when relevant. Schema changes are versioned or backwards-compatible; dashboards do not silently reinterpret old rows.
Every reported rate publishes numerator, denominator, eligibility population and time window. Trial start is not paid conversion; an impression is not revenue; a missing event is not automatically a user action.
Sampling and quality
Publish sampling policy and weight sampled rows correctly. Record dropped/buffered event counts where transport can fail. Validate duplicate/retry handling, client-clock anomalies and schema rejection. Small or biased samples are labeled accordingly.