Using the Recommendations View

Top Opportunities lists specific values in your records that no Blueprint row currently matches — the same coverage gaps that appear on each template's Observability report, but surfaced here across every template whose Observability toggle is turned on, ranked by how many records hold each value.

Each row shows:

• Template — The template whose matching came up empty. Click the template name to open it in the Data Logic module.
• Type — The object it applies to.
• Coverage Gaps — The unmatched CRM field value, shown per Blueprint input. Each chip pairs the Blueprint input with the CRM field value that didn't match it — for example, Job Title (Contains, Case Insensitive) → Marketing means records with "Marketing" in their job title didn't match any Blueprint row through that input. <Empty> means the CRM record's field held no value for that Blueprint input — the record didn't fail to match because of a wrong value, it failed because that field was blank entirely.
• Count — The number of records that hold this CRM field value.
• Review — Opens the template's report on the Observability page, so you can review the gap alongside the template's other findings.

For each opportunity, decide which of the three cases it is:

• The CRM field value is legitimately new or valid, and the Blueprint simply doesn't have a row for it yet. Add a row to the Blueprint.
• The CRM field value should have matched an existing Blueprint row, but didn't. Often, a Matching Criteria or Match Options issue (such as case sensitivity, extra whitespace, a Contains match that needed to be Exact, and so on). Adjust the existing row's matching rather than adding a duplicate.
• The CRM field value is invalid or malformed and doesn't belong in a Blueprint row at all. This may point to a data quality issue upstream, outside of Data Logic.

To view Top Opportunities:

1. In the left navigation, go to Data Integrity > Recommendations.
2. Find the Top Opportunities: Coverage gaps worth adding to the Blueprint section.
3. To fix a gap, click Review to open the template on the Observability page.
4. Scroll down to Coverage Gaps and click Export to download a CSV of the unmatched value combinations in the Blueprint's own column format.
5. Go to Data Integrity > Blueprints, download the current Blueprint version, and fill in the missing output values using the CRM field values from the export as a guide.
6. Upload the updated Blueprint CSV as a new version.

Once the new Blueprint version is uploaded, records that previously fell into this gap are re-evaluated against it — run the template in Data Logic to see the effect immediately, or let the next ingestion pick it up. The ranking makes fixing these efficient: a single Blueprint row that closes a 228-record gap moves your coverage more than a dozen one-record fixes would.

The image above shows the Top Opportunities table, with Template, Type, Coverage Gaps, Count, and Review columns.

Top Output Drift lists matched records whose CRM field values no longer hold what their Blueprint row assigned — the same drift that appears on each template's Observability report, but surfaced here across every template whose Observability toggle is turned on, ranked by how many records are mismatched.

Each row shows:

• Template and Type — Where the drift is happening. Click the template name to open it in the Data Logic module.
• Field Name — The CRM field that has drifted.
• Output Condition — When the template writes this field, such as Always or Field Non-Empty.
• % Consistent — of the records that matched, the percentage whose CRM field value still holds the Blueprint output it was assigned.
• # Mismatched — The number of records where it doesn't.
• Review — Opens the template's report on the Observability page, where the field's full Drift by Field breakdown sits alongside the template's other findings.

A low % Consistent paired with a high mismatch count is the clearest signal on the page: the Blueprint matched these records, and their CRM field values still don't reflect it.

To view and correct Top Output Drift:

1. In the left navigation, go to Data Integrity > Recommendations.
2. Find the Top Output Drift: Fields drifted from the Blueprint output they were assigned section.
3. Click Review to open the template on the Observability page.
4. In the template's detail report, scroll down to Drift by Field.
5. To open the template in the Data Logic module for analysis, click Analyze.
6. In the Data Logic module, under Run, click Review, and run the template in Preview mode now.

Reviewing the preview shows the exact before-and-after CRM field values for every affected record without changing any data. Once you're ready, run the template in update mode — this applies the Blueprint's output to every mismatched record whose Output Condition allows the write — or configure the template to run automatically so corrections land every cycle. If drift stays high after running, check the Output Condition first: under Field Non-Empty (or similar conditions that protect existing values), a CRM field that already holds a value is reported as drift but deliberately left unchanged, so a run won't move the number. If the condition is Always and drift still persists, something else is likely rewriting the CRM field after Insycle corrects it — an integration, a Workflow, or manual edits are the usual culprits.

The image above shows the Top Output Drift table, with Template, Type, Field Name, Output Condition, % Consistent, and # Mismatched columns, and a Review button on each row.

Top Blueprint Inconsistencies lists structural cases where a Blueprint field is used as both an input and an output, and the Blueprint is missing a row that would let a record already holding the correct value be recognized as such — for example, "The field 'Country/Region' is used as both an Input and an Output, but the Blueprint is missing a row with an Input value that matches 'united states.'" These are the same inconsistencies that appear in each template's Observability report, but they surface here across every template whose Observability toggle is turned on.

Each row shows:

• Template and Type — Where the inconsistency is happening. Click the template name to open it in the Data Logic module.
• Description — Names the Blueprint field, and the specific CRM field value it's missing an input row for.
• Count — The number of records affected.
• Review — Click to open the template's report on the Observability page, where the full Blueprint Inconsistencies list sits alongside the template's other findings.

When there are none, the section shows "No review items to show" — that's the state to aim for.

To view and correct Top Blueprint Inconsistencies:

1. In the left navigation, go to Data Integrity > Recommendations.
2. Find the Top Blueprint Inconsistencies: Blueprint rows with contradictory logic section.
3. Click Review to open the template on the Observability page.
4. In the template's detail report, scroll down to Blueprint Inconsistencies.
5. Click Export to download the missing Blueprint values as a CSV in the Blueprint's own column format. For each row in the CSV, the self-mapped Blueprint field is filled in on both sides — the missing value appears in both its matching input column and its output column. For Blueprints with more than one input/output pair, every column outside the self-mapped pair is left blank.
6. Go to Data Integrity > Blueprints and download the current Blueprint version, append the rows from the export CSV, and upload the result as a new version.

These should be fixed in the Blueprint itself, not the data. Once the new version is uploaded, the flagged records for that CRM field value clear — run the template to see the effect immediately, or let the next ingestion pick it up. Because each entry names one missing value, one added row typically clears every record flagged for it, so the counts are a useful way to prioritize which gaps to close first.

The image above shows the Top Blueprint Inconsistencies table, with Template, Type, Description, Count, and Review columns, listing two State/Region self-mapping gaps for Broken State Normalization.

An ingestion cycle runs each time your CRM data flows into Insycle — on every sync and whenever an update operation runs. A full ingestion cycle, which evaluates every record, runs once daily; intra-day and ad hoc ingestions, such as a template run, re-evaluate only the records they touch.

Recommendations reflects the most recent ingestion — including operations run through Insycle, such as a template run — so when you fix something, the count for it drops the same day, without waiting for the next full cycle. The account-wide numbers in the Overview and the tiles and template list in Observability are based on the full ingestion cycle, which runs once daily, so they catch up more slowly at the next full cycle. An emptying Recommendations page is the product working, even before the Overview reflects it.

The Recommendations view populates once your first ingestion cycle completes and draws only on templates whose Observability toggle is on — a template that isn't observable doesn't contribute any items here, regardless of how much data it has.

If every section shows "No review items to show" on an account whose templates have already been evaluated, that's not an error — it means your observable templates currently have nothing that needs review.