---
title: "Data Manager: tracking plan and event validation · Countly"
description: "Plan events before a release ships, catch what arrives that doesn’t match the plan, and fold messy names together as data comes in."
url: https://countly.com/feature/data-manager
last_modified: 2026-11-04
---

Data Manager

# Decide what your apps send, before they send it

Plan events before a release ships, catch what arrives that doesn’t match the plan, and fold messy names together as data comes in. Every report reads the schema you keep here.

In this demo bank, validation caught an event nobody planned and a segment sending the wrong type of value, each with how often and when it last happened.

Part of data control

## Five statuses decide what gets through

Every event in the schema has a status, and the status does the work on the way in: what passes cleanly, what gets flagged, and what stays out of the reports.

- 01 Unplanned Sent by an app, never planned. Recorded as an error, so somebody decides what it is.
- 02 Created Written into the plan while the tracking is being built. Kept out of reports, and flagged when it arrives.
- 03 Approved Confirmed working, not yet in circulation. Kept out of reports without being flagged.
- 04 Live In use. Passes through untouched and shows up everywhere.
- 05 Blocked Deliberately shut out, and kept off every report.
Validation

## Bad data, caught on the way in

Validation compares what an app actually sent with the plan, and lists each mismatch with how often it happened and when it last did. Expand one to see the plan beside what arrived.

Unplanned

### Not in the plan

An event or a segment the schema has never heard of. Approve it if the schema was simply behind.

Unexpected

### Not live yet

An event or a segment that is not Live or Approved, such as one whose tracking is still being built.

Data type mismatch

### The wrong kind of value

A number planned and text sent, or the other way round.

Missing segmentation

### A required field left out

A segment marked as required that did not arrive with its event.

Global validation

### Personal data where it shouldn’t be

A value that matches the server’s pattern for personal information.

Segment validation

### A value that breaks your rule

A value that matches a pattern you set on one particular segment.

In practice

## Clean data, kept clean

Plan events before they ship, tidy what is already there, and fold duplicates together as they arrive.

- Plan an event before it ships Write the key, a description and its segments into the schema. It waits at Created until the release is ready.
- Tidy the event list Filter to the events without a category, describe one, and sort many at once.
- Merge two events into one Fold an old key into the current event as data arrives, without touching the app. The summary says what will happen before you save.
- Read the schema at a glance How many events are described and categorized, which are unplanned, and what each one carries.
Works with

## Data Manager, with the rest of Countly

Every feature reads the same live data, so an answer in Data Manager doesn’t stop there. These are the handoffs built in.

All features

Drill

Omit a segment from event charts and its raw data stays queryable in Drill. Hidden events keep recording.

Open

Profiles

Manage the properties stored on a person, their data types and what they mean, next to the events.

Open

Core Analytics

The names, descriptions and categories you set here are what the everyday event reports show.

Open

MCP Server

An AI assistant’s implementation plan is kept here as planned events, set live once the data arrives.

Open

Data ownership

## Your schema, on the server that holds your data

Plans, validation records and transformations live next to the data they describe, not in a separate tracking-plan tool that has to be kept in sync.

Data privacy

### Self-hosted, or dedicated

Run Countly in your own cloud, your data center or an air-gapped network. Or let us run a single-tenant instance in the Google Cloud region you choose.

### One schema, read everywhere

A name, description or category set here is what every chart, picker and report shows. Nothing to sync.

### No default vendor access

On Enterprise, Countly has no access unless you grant it. On Flex, access is limited, granted by you and logged.

ISO 27001 Certified

ISO 27017 Certified

ISO 27018 Certified

SOC 2 Type II examined

TISAX® Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax