Configuring Data Logic Input Mapping

1. Navigate to Data Integrity > Data Logic.
2. Complete 1. Pick Blueprint.
3. Click 2. Input Mapping to expand this step.

The image above shows the Data Integrity nav with Data Logic selected, and the Territory Assignment template's 2. Input Mapping step expanded.

Each row in Input Mapping binds one Blueprint column to one CRM field, and defines how the two are compared:

• Blueprint Column — the column whose values are being matched against.
• CRM Field — the record field being compared to that Blueprint column.
• Matching Criteria — how the two are compared (see Matching Criteria Reference below).
• Match Options — optional refinements that let legitimately equivalent values match despite formatting differences (see Match Options Reference below).

Add additional input columns with + Input. Once you've configured your mapping, use Test to check it against a real record before running the template — see Testing Data Logic with Test Matching and Near-Miss Detection.

The image above shows 2. Input Mapping of the Data Logic module with three Blueprint columns mapped to CRM fields — Lead Source (Contains) mapped to Lead Source with Contains matching criteria and Blank Cell Matches Any enabled, Lead Source Original (Exact) mapped to Lead Source Original with Exact matching criteria, and Referrer Domain (Ends With) mapped to Referrer Domain with Ends With matching criteria and Blank Cell Matches Any enabled (partially visible).

Matching Criteria determines how a Blueprint cell's value is compared to a record's CRM field value.

Criteria Usable on Any Field Type

Numeric Criteria

Date Criteria

Number Between and Date Between cells follow specific formatting conventions — see Numeric and Date Ranges in Designing a Blueprint CSV for the full rules on range syntax, open-ended ranges, and accepted date formats.

Match Options refine how comparisons are made — they never modify your CRM data or your Blueprint. Each input column can carry one or more, chosen from the Options dropdown beneath its Matching Criteria, and multiple options can be combined on the same column.

Case Insensitive — Comparison ignores letter casing, so United States matches united states. Applies to all text-based matching criteria: Exact, Contains, Contains Word, Starts With, Ends With, and Regex.

Trim Whitespace — Leading and trailing spaces are stripped from the CRM field value before comparing. Doesn't affect spaces in the middle of a value. Useful for data with leading or trailing spaces from imports, integrations, or manual entry — one of the most common causes of unexpected non-matches.

Normalize Whitespace — Trims leading and trailing spaces and also collapses internal runs of whitespace to a single space. Useful for data with inconsistent internal spacing from copy-pasting or rich text sources.

Ignore Whitespace — Removes all whitespace before comparing, so values match regardless of spacing entirely: NewYork matches New York, and ABC 123 matches ABC123. The strongest of the three whitespace options — use it when spacing carries no meaning at all, as with codes and identifiers that appear both spaced and unspaced.

Ignore Special Characters — Removes punctuation and symbols before comparing, preserving letters, digits, and spaces, so AT&T matches ATT and Inc. matches Inc. Hyphens and decimal points count as special characters — avoid this option on fields where they carry meaning, such as product codes or identifiers.

Blank Cell Matches Any — A blank Blueprint cell in this column becomes a wildcard, matching any CRM field value, including an empty one. Without this option, a blank cell under Exact matching matches only records where the CRM field is also empty, and a blank cell under any other matching criteria blocks the row from matching at all. This is the mechanism behind sparse Blueprint rows — see How Blank Cells Are Evaluated in Blueprint Input and Output Columns for the full explanation, including when this option should and shouldn't be enabled.

Combining options: The three whitespace options escalate — Trim is contained within Normalize, and Normalize within Ignore — so combining them is redundant; choose the strongest one the field actually needs. Case Insensitive and Trim Whitespace are commonly combined to handle both casing and stray-space issues in the same column: a CRM field value of " ACME CORP " would match a Blueprint cell of acme corp with both enabled.

The image above shows 2. Input Mapping of the Data Logic module with three Blueprint columns configured, and a teal arrow pointing to the Match Options column where the dropdown is expanded — displaying the six available options (Case Insensitive, Blank Cell Matches Any, Ignore Whitespace, Ignore Special Chars, Trim Whitespace, and Normalize Whitespace) — with Blank Cell Matches Any and Ignore Special Chars checked.

What Match Options Don't Affect

• Numeric and date matching criteria are never affected by any option — values are always compared exactly as they appear in the CRM field.
• Output columns — options apply only to input columns and have no effect on what gets written when a row matches.
• The Blueprint itself and your CRM data — options change comparison behavior only. Neither your Blueprint CSV nor your CRM field values are ever modified by enabling an option.

Quick Reference

Once you've mapped a CRM field as an input, it's worth knowing that the same field can also serve as an output in the same Blueprint. For example, a Job Title column can match records based on their current job title value and, in the same run, write a standardized job title back to that same CRM field—letting Data Logic identify and update a field in a single pass. 

See Configuring Data Logic Input Mapping and Configuring Data Logic Output Mapping for how Data Logic mapping works.