Governance sounds bureaucratic until the third quarter, when nobody can say whether two similarly named events mean the same thing. Naming conventions, ownership and a place where PII rules are written down cost little early and are close to impossible to retrofit.
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 pipelineThe path an event takes from the SDK to the store: validation, transformation, consent checks and masking, in that order.
- EventOne recorded action with a timestamp, a user and a set of properties. The unit everything else on this page is built from.
- 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.