Deduptio

How to find duplicate people in Attio by LinkedIn URL

The short answer

Attio does not look for duplicates on LinkedIn. It stores the LinkedIn value as plain text and only prompts you about people who share an email address. To find people who share a profile, reduce every stored URL to its handle, the part after /in/, lowercase it, and group records on that. Then open a sample of the groups and merge the pairs one at a time.

LinkedIn is worth this work because it survives a job change and email does not. When Jane moves from jane@oldco.com to jane.doe@newco.com, her two records share no email, but both can carry the same profile link. The wider rule for people, with email, phone and name, is in finding duplicate people in Attio. This page covers the LinkedIn value alone.

What Attio does with a LinkedIn URL

Four facts from Attio's documentation set the size of the job.

The standard People attributes are not editable, so you cannot switch uniqueness on for LinkedIn itself. The prevention route, a custom attribute of your own, is at the end of this page.

Per Attio's People object, manage standard objects, create and manage attributes and merge and delete records pages, and LinkedIn's manage your public profile URL article, checked November 21, 2026.

One profile, many strings

A text attribute compares values as typed. The same profile reaches Attio in several shapes, and each shape is a different string.

Stored valueWhat differsHandle
https://www.linkedin.com/in/jane-doe/Nothing; the full form with a trailing slashjane-doe
http://linkedin.com/in/jane-doeScheme, no www, no slashjane-doe
linkedin.com/in/Jane-DoeNo scheme, capital lettersjane-doe
https://www.linkedin.com/in/jane-doe?trk=profileA tracking query copied from the browserjane-doe
jane-doeHandle only, typed by handjane-doe

Capital letters do not change the profile. LinkedIn's help centre says the custom part of the URL is case-insensitive: “JohnSmith, johnsmith, or johnSmith will all point to the same profile”. So the handle, lowercased, is the value to compare. Everything before /in/ and everything after the next /, ? or # is noise.

Reduce every URL to a handle

Work in an export, not in the live workspace. You keep the original value and add the handle in a new column.

  1. Export People. Export the People object to CSV with Record ID, Name, Email addresses and LinkedIn.
  2. Extract the handle. In Google Sheets, with LinkedIn in column D: =IFERROR(LOWER(REGEXEXTRACT(D2,"/in/([^/?#]+)")),LOWER(TRIM(D2))). The first part takes whatever follows /in/. The fallback keeps a value that was entered as a bare handle.
  3. Flag values that are not profiles. Mark every row whose LinkedIn contains /company/ or /school/, and placeholders such as n/a. The formula falls back to the whole value for these, and they must not join a group.
  4. Count each handle. In a new column: =COUNTIF(E:E,E2). Filter to rows where the count is 2 or more and the handle is not empty.
  5. Sort by handle. Records with the same handle now sit next to each other. Each run of rows is one candidate group.

The spreadsheet finds the groups but merges nothing, and the export is out of date the moment someone edits a record. The limits of this route are in CSV export and a spreadsheet.

Write the clean value back

Normalizing the stored values makes every later check exact, including Attio's own filters and any tool you run next. Pick one canonical form, such as https://www.linkedin.com/in/jane-doe, and build it from the handle.

  1. Add a column: ="https://www.linkedin.com/in/"&E2, and leave the flagged non-profile rows empty.
  2. Import the file into People with Record ID mapped and the new column mapped to LinkedIn. Attio's import guide says a row whose ID matches an existing record updates it, and a row whose ID matches nothing is skipped.
  3. Test on ten records first and open them afterwards. Empty cells are skipped and do not overwrite existing data, so the flagged rows keep their old value until you fix them by hand.

Find shared URLs through the API

The records query endpoint answers “who else holds this profile” for one handle at a time. Text attributes accept the $eq, $in, $contains, $starts_with and $ends_with operators. Before the values are clean, $contains on /in/jane-doe finds the URL shapes; a value stored as a bare handle needs a second, $eqcheck. Attio's text attribute page does not say whether $contains ignores case, so search for the handle both lowercased and as it appears on the profile.

POST /v2/objects/people/records/query
{ "filter": { "linkedin": { "$contains": "/in/jane-doe" } } }

Finding every shared handle in the workspace is a different job. You read all People records, compute the handle for each and group them yourself. The paging, rate limits and merge calls are covered in duplicate detection with the API.

A shared URL that is not a duplicate

A matching handle is the strongest signal a person record has after email. It still produces wrong merges in four cases.

The opposite failure happens too. A person who changed their custom URL appears under two handles, and LinkedIn says the old one may show a Profile Not Found page. Those pairs share no value; only a name and a second signal will find them.

Merge the confirmed pairs

Attio merges people natively, two records at a time. Open one record, click the ⋮ icon in the top right, select Merge records, click + and choose the duplicate. The record on the right is prioritized: its values win where the two records conflict. LinkedIn holds one value, so put the record with the correct URL on the right.

Attio combines list entries, notes, files, tasks, comments, call recordings, meetings and emails from both records. The result is a new record with a new record ID and URL, so a link saved to either original stops pointing at it. Attio's merge page documents no undo. The full steps are in how to merge records in Attio.

Matching on LinkedIn in Deduptio

Deduptio can key a match rule on the LinkedIn attribute. It reads it as a text attribute: the value is lowercased and every punctuation mark and symbol becomes a space. Nothing is written back to Attio; only the comparison value changes. That has a consequence worth stating before you rely on it.

Scans are read-only, and you decide per group before anything merges. Merges run through Attio's native merge, and Deduptio keeps a snapshot for 24 hours so a wrong merge can be rolled back. Notes, tasks, emails and list memberships are not restored by a rollback. Details are in match rules, rollback and plans.

Find the people who share a LinkedIn profile

Connect your Attio workspace, write one match rule, and run a scan. Scans are read-only — you see every group and the reason it matched before anything is merged.

Start a free Attio duplicate scan

Stop new duplicates from arriving

Attio lets you create your own unique attributes on People. A custom attribute holding the lowercased handle, marked unique, refuses a second record with the same profile. Two details decide whether it works.

The other sources of new people, from email sync to form submissions, are covered in how to prevent duplicates in Attio.

Checklist

  1. Export People with Record ID, Name, Email addresses and LinkedIn.
  2. Extract and lowercase the handle after /in/; flag company pages and placeholders.
  3. Group by handle and read every group where the names disagree.
  4. Write a canonical URL back by import with Record ID mapped, testing on ten records.
  5. Merge confirmed pairs with the correct LinkedIn record on the right.
  6. Hold the handle in a unique custom attribute so the next duplicate is refused.

Related