Choose the field that identifies one of your records

Most workspaces already carry an identifier of their own: a number from the system they moved off, a Danish P-nummer, a customer number the finance team uses. Naming that field tells DealJourney it *is* the record, so an import matching on it links a row to the customer that already carries the value, ahead of organisation number, email and phone number.

Name the field

1. 1Open Admin from the sidebar.
2. 2Go to Arbejdsområdeindstillinger.
3. 3Choose Hvad identificerer en post.
4. 4Pick the field from the list.
5. 5Read what the panel underneath says about the records you already have, then add it.

Only fields your workspace already has appear in the list. If yours is not there, create it first: see Add a custom field.

You can name more than one. They are checked in the order shown, so put the one you trust most at the top.

How values are compared

Each field has a comparison rule, and picking the right one matters more than it sounds.

• Compare digits only ignores spaces, dots and letters. A reference written "DK 10 12 83 80 81" in an export and stored as "1012838081" here is one value, not two. Right for org numbers, P-numbers and customer numbers.
• Compare as written matches the text exactly. Right for a reference that genuinely contains letters that matter.
• Compare as an email address ignores capitalisation the way an email address should.

Two rules that keep it safe

Both are deliberate, and neither can be switched off.

• A blank is never a match. Two records that both leave the field empty are not the same company. A row with nothing in that field falls back to ordinary matching.
• A value several records already use will never link automatically. If three of your customers carry the same number, nothing can tell which one an incoming row means, so the row goes to review with those records listed rather than being merged into a guess.

See what it would mean before you save

Pick a field and DealJourney counts your existing customers on the spot, before anything is saved. It tells you three things:

• how many of your customers have a value in that field at all,
• how many different values there are, and
• how many of those values are already carried by more than one customer, and how many customers that covers.

That last number is the one to read. Those records will never link automatically, so the cost of a messy identifier is review work, not a wrong merge. A field where every value is unique says so plainly.

The panel also lists the values shared by the most records. That is usually enough to spot a placeholder somebody imported years ago, which you can clear out before you start relying on the field.

A field nobody has filled in yet is not an error either. It simply will not match anything until the values are there, and the panel says exactly that.

What changes in an import

Once a field is named, mapping a column to it is a linking strategy on its own. A file with only that column and nothing else the importer recognises will still match, where before it reported that it had no way to link and created a new record for every row. See Avoid creating duplicates.

Removing a field from this list changes nothing that has already been imported. It only stops future imports matching on it.