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.
Data Manager
Decide what your apps send,
before they send it.
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.
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 featuresData 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 privacySelf-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 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type 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