Understanding the Data Integrity Overview

To navigate to the Overview:

• In the left navigation, click Data Integrity, then select Overview.

The image above shows the Overview page, with the four headline metric cards across the top and the Coverage Trend and Drift Trend charts below them.

	Coverage Coverage is the percentage of governed records that match your Blueprints — a record is covered when the template's matching connects it to a row in the Blueprint. Low coverage points to one of three causes, worth checking in order: not enough of your database is being monitored (consider activating additional templates), your Blueprint has gaps (records that should match, but no row matches them), or your records hold data that doesn't fit your data strategy at all.
	Records Drifting Records Drifting is the number of governed records that hold field values your Blueprint says should be different. Coverage tells you a record matched the Blueprint; Records Drifting tells you its values no longer agree with what that matched row says they should be. A record counts once here, even if several templates flag it — so this number reflects how many actual records need attention, not how many times a record was flagged across templates.
	Fields Governed Fields Governed is a count of how many fields are governed by a Blueprint, counted per object type. Unlike the other three metrics, Fields Governed isn't derived from per-record evaluation — it measures how much ground your data governance covers, and it grows as you govern more fields. It doesn't decline even if data quality gets worse, since it's tracking scope, not conformance.
	Records Governed Records Governed is the number of records being evaluated at all, out of the total in your account. It's determined by the filters on your observable Data Logic templates — only the records those filters include are governed. Records outside this number aren't being evaluated, so no problem with them will ever appear on the Overview or anywhere else in Data Integrity. A Data Logic template is observable when its Observability toggle is turned on, which makes it eligible for evaluation and reporting across Data Integrity.

How the Change Indicators Work

An ingestion cycle runs each time your CRM data flows into Insycle — on every sync, and whenever an update operation runs — and it's what re-evaluates your observable templates against their Blueprints. Each top-line metric shows its change against roughly 90 days ago — for example, "−161 vs 90 days ago" under Records Drifting. The comparison uses the ingestion cycle closest to that date, so on newer accounts, where 90 days of history doesn't yet exist, the actual gap may be shorter.

For Records Drifting, a negative change is an improvement — it means fewer records are out of line with your standards than before.

Reading the Metrics Together

The four top-line metrics answer four different questions, and they're worth reading together rather than in isolation:

• How much of my data is governed at all? Records Governed, against your account total. Growing this number is how your data strategy expands.
• Of what's governed, how much matches the standard? Coverage.
• How many records are actively out of line? Records Drifting.
• How broad is my governance? Fields Governed.

A high Coverage number paired with a low Records Governed number means the data you're evaluating is in good shape, but most of your database isn't being evaluated yet. The strongest position is both numbers high — broad governance, high conformance.

Below the metrics, two charts show how your data integrity has changed over time, broken out by object type — each line represents one object (Contacts, Companies, and so on), with the same color for the same object on both charts.

• Coverage Trend — the coverage percentage over time. A steady or rising line means your Blueprints and your data are staying in step. A drop usually means new data arrived that your Blueprints don't yet recognize.
• Drift Trend — the number of drifting records over time. Falling drift means corrections are landing; rising drift means records are moving away from your standards faster than they're being corrected.

A point at zero on the Drift Trend is a good sign — it means the object had no drifting records that day, not that data is missing.

The charts cover roughly the last three months. On an account whose first ingestion cycle is recent, they start from that first cycle, so you may see only a few points at first — the trend fills in as cycles accumulate.

The Overview populates after your first ingestion cycle completes and your observable templates have been evaluated. Until then, the page has nothing to summarize. Once a cycle finishes, the metrics and charts appear automatically — no configuration is needed beyond having observable Data Logic templates. Insycle provides some observable templates by default, and you can add your own templates by turning on the Observability toggle (the shield icon) in the Data Logic module.