Everything downstream inherits the quality of this one object. A well-formed event has a stable name, a consistent user identifier, an accurate timestamp and properties chosen so that tomorrow’s breakdown is already possible.
More in Data
- AutocaptureRecording interactions automatically instead of instrumenting each one. Quick to start with, expensive to govern once the schema drifts.
- Customer Data Platform (CDP)A system that unifies customer data from several sources into one profile. Countly builds those profiles in the same store the analytics runs on.
- Data governanceThe rules for what is collected, how it is named, who may see it and how long it is kept, decided before the data becomes a report.
- Data pipelineThe path an event takes from the SDK to the store: validation, transformation, consent checks and masking, in that order.
- Event propertiesThe attributes carried by an event (plan, screen, version, value) that make it possible to break a metric down later.
- Event trackingDeciding which actions matter, naming them consistently, and sending them from every platform the product runs on.