# Monitor tracking plan data quality in Console
> See how many events matched each tracking plan and event specification over the last 30 days, and how many of them were valid or inferred, had violations, or failed.
> Source: https://docs.snowplow.io/docs/event-studio/tracking-plans/data-quality/
> Documentation index: https://docs.snowplow.io/llms.txt

Console shows the results of [event specification inference](/docs/event-studio/tracking-plans/event-specification-inference/) and [event specification validation](/docs/event-studio/tracking-plans/event-specification-validation/) next to your tracking plans and event specifications. Every event volume figure is split into valid events, inferred events, events with violations, and failed events. You can see how well an implementation matches its specification without querying your warehouse. Use these metrics to confirm that implementations are live, identify unused specifications, and find implementation problems.

Metrics cover the last 30 days for one pipeline at a time. Every view that shows them has a pipeline selector, which defaults to your production pipeline.

## Understand the event categories

Console sorts every event that the pipeline matches to a published event specification into one of four categories:

| Category               | Meaning                                                                                                                                                                                                                                                                                 |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Valid events           | Events that arrived with an `event_specification` entity and passed validation                                                                                                                                                                                                          |
| Inferred events        | Events that the pipeline matched to the specification by inference. Inferred events are valid events too, but the pipeline doesn't validate them                                                                                                                                        |
| Events with violations | Events that arrived with an `event_specification` entity, failed validation, and were loaded to your warehouse with an `event_specification_validation` entity attached                                                                                                                 |
| Failed events          | Events attributed to the specification that ended up in [failed events](/docs/fundamentals/failed-events/). This includes events with schema violations, and events that failed validation in a tracking plan that [sends them to failed events](#send-invalid-events-to-failed-events) |

Only events that arrive with an `event_specification` entity go through validation, so only they can end up as valid events or events with violations. Tracking code generated with [Snowtype](/docs/event-studio/implement-tracking/) attaches this entity for you. Events without it can only be matched by inference.

The total volume is the sum of the four categories. Where Console shows a bar next to a volume, each segment is one category. Hover over the bar to see the count for each category.

Failed event counts come from your [data quality dashboard](/docs/monitoring/), not from the Console API. They are available when the selected pipeline loads failed events into your warehouse, the data quality dashboard is connected to that pipeline, and you have permission to view it. Otherwise the failed events category shows N/A, volumes exclude failed events, and a warning icon next to the volume explains why.

## View data quality for a tracking plan

Open a tracking plan to see its **Data quality** panel. The chart shows the total number of events across all event specifications in the plan, split by category, with the share and count of each. Click **View details** to open the data quality dashboard for the selected pipeline, or the failed events page when the dashboard isn't connected.

![E-commerce Web tracking plan page with a Data quality panel showing a donut chart of 139.78k total events on the prod pipeline over the last 30 days, split into valid events, inferred events, events with violations, and failed events, above an event specifications table with a volume bar per specification](/assets/images/tracking-plan-data-quality-6207f3acf6c4016e5bf00a0025ba7879.png)

The event specifications table shows the same breakdown per event specification in its **Volume** column. The **Last seen** column shows the most recent event for the specification, whether it was valid or failed.

## Compare tracking plans and event specifications

The **Tracking plans** list shows the volume breakdown for every tracking plan in its **Event volume** column. The [Event Catalog](/docs/event-studio/event-catalog/) shows it for every event specification across all tracking plans in its **Volume** column. Both views have a pipeline selector next to the filters.

![Tracking plans list with a pipeline selector set to prod and an Event volume column showing a count and a colored bar for each tracking plan](/assets/images/tracking-plans-list-0020dd1d3f4dd4284bfc40f8cb3f6a20.png)

![Event Catalog filtered to published event specifications and sorted by tracking plan, with a pipeline selector and a Volume column showing a count and a colored bar for each event specification](/assets/images/event-catalog-volume-b232fee4f7b5178d935afa1a8c6dc99a.png)

## Track specification versions and application IDs

Each event specification has a **Tracking summary** tab that breaks the metrics down by specification version and application ID. Use it to check that a new version has reached all applications, or that an application still sends an old version.

![Tracking summary tab of the Add to cart event specification listing versions 1 and 2, the app IDs that sent each version with green, yellow, and gray status badges, the last seen date, and a volume bar](/assets/images/event-specification-tracking-summary-c2b199b431a8c6275fb7a529d4bc8e76.png)

Each row is one version of the specification that the pipeline saw events for in the last 30 days. The **App ID** column lists the application IDs that sent those events, with a status for each:

| Status         | Meaning                                                                                                |
| -------------- | ------------------------------------------------------------------------------------------------------ |
| Green check    | The app ID belongs to a source application of this version and sent events                             |
| Yellow warning | The app ID sent events, but doesn't belong to any source application of this version                   |
| Gray minus     | The app ID belongs to a source application of this version, but didn't send events in the last 30 days |

A yellow status usually means that an application tracks the event without being listed in the specification. Add its [source application](/docs/event-studio/source-applications/) to the specification, or remove the tracking from that application.

## Send invalid events to failed events

Each tracking plan has a **Data quality rules** setting that controls where events that fail [event specification validation](/docs/event-studio/tracking-plans/event-specification-validation/) go. In Console, open the tracking plan and select **Data quality rules**. You need the **Edit** [permission](/docs/account-management/managing-permissions/#tracking-plans) on tracking plans to change this setting.

The default is **Send to valid events and mark as violation**, which keeps those events with your enriched ones. Select **Send to failed events as validation error** to route them to [failed events](/docs/fundamentals/failed-events/) instead, keeping events that don't conform to their specifications out of your warehouse `events` table.

![\&quot;Data quality rules\&quot; dialog for a tracking plan, showing the options \&quot;Send to valid events and mark as violation\&quot; and \&quot;Send to failed events as validation error\&quot;](/assets/images/data-quality-rules-dialog-2fc40cc406f398d4dffc3ff4883c3a5e.png)

The **Data quality rules** setting applies to all event specifications in the tracking plan and all their versions. Changes take effect within a few minutes, with no new specification version to publish and no tracking code to redeploy.

Events routed this way appear in failed events as enrichment failures from the event specification enrichment. They keep both the `event_specification` and `event_specification_validation` entities, so you can inspect why each event failed. In Console, they count as failed events rather than events with violations, as described in [Understand the event categories](#understand-the-event-categories).

If the pipeline cannot find the specification an event declares, that event stays with your enriched events, even when the tracking plan sends invalid events to failed events.
