Tracking plan & validation

Event definitions record events that already exist; the tracking plan records events you intend to collect, including ones not sent yet. They match on event name and each side can generate the other. Deleting a plan row does not delete the definition or the data.

ConsoleAll-platform analyticsDataTracking plan

Event definitions are on the Definitions tab of ConsoleAll-platform analyticsDataEvent inbox, which also holds unclaimed events. There is no QR-code check on the plan screen; verification is a count over the last 24 hours.

Metrics & definitions

• Fields: event name, display name, category, platforms, trigger, properties, owner, developer, status, and notes.
• Status: Proposed, Developing, Accepting, Live, or Deprecated. Accepting means events have arrived and you are still checking properties.
• Platforms: buttons are web, ios, android, harmony, mp, and server.
• Properties: name, type, required, recommended, description, and example.
• Live verification: turning on Live verification (24 h) adds two columns, hits in 24 hours and completeness of required properties. Low completeness is a warning; it does not block intake by itself.

How to use it

• New event, edit, or delete plan rows.
• Generate from definitions: fills the plan from existing definitions without overwriting a row that already uses that event name.
• Sync to definitions: only links a definition that already exists. A plan row whose status is Live marks that definition live.
• Import: CSV or the exported JSON, matched on event name, either overwriting existing rows or skipping them. In CSV, properties are separated with |, and * marks required.
• Export XLSX.

Access & limits

Anyone can view the list. Creating, editing, importing, syncing, and deleting need Analyst or above.

Data quality

A broken tracker makes reports shrink without an error on the chart; this page shows at which step data was lost: a domain mismatch, an exclusion rule, a quota, a rate limit, or a bad payload. It does not change retention days; those are in Retention & deletion.

ConsoleAll-platform analyticsDataData quality

The range is the last several days. Tabs: Ingestion warnings, High cardinality, Stale detection, Quarantine, and Tiered decay.

Metrics & definitions

• Cards: Ingestion warnings, Collector rejects, Blocked events, Blocked properties, High-cardinality props, and Possibly stale.
• Ingestion warnings: aggregated by kind and hour, such as blocked events or properties, out-of-whitelist values, invalid IDs, and clock skew.
• Collector rejects: happen before storage and are listed by reason and day, such as domain mismatch, exclusion rule, monthly quota, rate limit, invalid payload, and bots.
• High cardinality: distinct values over 7 days against a threshold. Keys that have reached about half of it are listed too.
• Stale detection: a confirmed rule is flagged when its hits fall more than 80% week over week (at least 20 hits in the earlier week) while autocapture on the same page falls less than 30%. The page suggests similar selectors and does not edit the rule.
• Quarantine: keeps the latest 300 events whose validation action was quarantine. They are not stored. Clearing cannot be undone, and you cannot release them into storage from here.
• Tiered decay: event rows older than the set number of months have high-cardinality columns such as properties, referrer URL, and title cleared. Trends and funnels still run; breakdowns and drill-down on those columns do not.

How to use it

• High cardinality: click Scan now, mark a property Export only or Back to UI, Unflag it, or add or discard whitelist values that are waiting.
• Stale detection: click Detect now, then fix the rule from the candidate selectors or Dismiss.
• Quarantine: after fixing the tracking, click Clear quarantine.
• Tiered decay: pick the decay months, which must be shorter than the current raw-event retention. It runs daily at 03:40 in batches of 5,000 rows, up to 40 batches per run; you can also click Run a batch now.

Access & limits

Anyone who can open the project can view the page. Scans, property rule edits, whitelist handling, and clearing quarantine need Analyst or above. Setting decay months and running decay need Owner or Admin. The validation rules themselves are configured in Property definitions.

FAQ

Does a warning mean data was dropped? Not necessarily. Warn-only events are stored; collector rejects are the ones that happen before storage.

Is quarantine a recycle bin? No. Clearing it discards events that were never stored.