The confidence line
What the score means, where the line sits, and what happens to the fields that fall under it.
What the score means
The engine reads the source and scores every field: how confident it is that a field on their side means what it appears to mean. Not whether the types line up — whether the meaning does. cust_nm mapping to customer.name at 94% is the engine saying it is fairly sure those are the same idea.
A high score is not a promise. It is a statement about how much checking the engine thinks the mapping needs.
Where the line sits
Above the line, the engine maps the field and moves on. Below it, the mapping comes to a person as a question, with the engine’s best guess already filled in — so the common answer is yes rather than a blank form.
The line ships at a sensible default per connector. Moving it up means more questions and less taken on trust; moving it down means the reverse. Most partners never move it.
A connector, end to end
Fourteen fields, eleven mapped without anyone, three questions. The three took a few minutes between them, and two of the three answers were the engine’s own suggestion.
The figures above illustrate the shape of a run rather than reporting one — the pattern is what matters here: most fields settle well above the line, a few land under it, and those few are the only ones anyone is asked about.
| Their field | Confidence | What happened |
|---|---|---|
| work_email | 98% | Mapped by the engine |
| given_name | 96% | Mapped by the engine |
| employee_no | 91% | Mapped by the engine |
| dept | 88% | Mapped by the engine |
| — default line, 85% — | ||
| cost_ctr | 61% | Asked. Confirmed against their chart of accounts |
| mgr_ref | 44% | Asked. Redirected to a different destination field |
| loc_code_2 | 23% | Asked. Left unmapped — it duplicates loc_code |
The same line governs repair
When the far side changes, the engine re-scores what moved. Anything that clears your line is remapped without asking. Anything that does not comes back as the same kind of question it asked the first time.
That is why the line is worth understanding: it is not a one-time setup decision, it is the standing rule for how much the system does on its own.