Data and search
In short
Why did my LinkedIn search import fewer contacts than it found?
Start with the results file the search produces; it gives a reason for every person it did not add. The three usual answers are the 2,000-per-day allowance on your LinkedIn account, people who were already in your contacts, and the one that is genuinely invisible: a person whose LinkedIn address already belongs to more than one of your existing contacts is dropped with no reason recorded at all.
Quick fix
- Open the results file attached to the finished-search notification. It lists every person and why they were or were not added.
- Add up the "already exists" rows; those people are in your contacts already, and may still have been moved into the sequence.
- Check how many results you have already pulled today on that LinkedIn account. The allowance is 2,000 per account per day.
- If the file's totals still do not account for the gap, the missing people are most likely duplicates by LinkedIn address. See below.
- Re-run tomorrow, or from a different connected LinkedIn account, for anything the allowance cut short.
Didn't work? Contact Reply support; the team can check your account directly.
Symptom
You pasted a LinkedIn search and asked for a number of contacts. The run finished and you were notified, but the contact count in Reply is lower (sometimes much lower) than the search reported.
Read the results file first
Every finished LinkedIn search produces a downloadable file with one row per person and a reason for each. It is the fastest way to answer this question, and most of the reasons below appear in it by name:
| Reason in the file | What it means |
|---|---|
| Added | The contact is now in your account |
| Already exists | The person was already one of your contacts. They were not added again, but they may still have been moved into the sequence |
| Duplicate | Two rows in the same run resolved to the same person |
| Skipped | The row was excluded by your settings for contacts already in other sequences |
| Invalid | The row could not be read as a person |
| Limit exceeded | Your contact storage allowance was reached mid-run |
If the rows in the file add up to the number the search showed, your answer is in the table. If they do not add up, read the next section.
The five reasons people go missing
1. People who share a LinkedIn address are dropped silently
This is the one that is genuinely invisible, and it is the most common cause of a gap the results file cannot explain.
A LinkedIn search returns people without email addresses. When Reply tries to match such a person against your existing contacts and finds that two or more of them already carry that same LinkedIn address, it cannot decide which one to update, so it drops the row entirely. No error, no row in the file, no explanation.
Duplicate LinkedIn addresses are more common in long-running accounts than people expect; the same person can arrive through an import, a Findy save and a CRM sync, and each route can leave its own record.
How to recognize it: the results file's totals are lower than the number of people the search reported, and the gap has no row to explain it.
What to do: merge duplicate contacts, then re-run the search. The people who were dropped will import normally once each LinkedIn address belongs to one contact.
2. The daily allowance was reached
Each connected LinkedIn account can pull 2,000 results per day, counted per calendar day in UTC and shared with anything else that consumes that account's search activity. The count goes up by the number of people actually returned, not by the number you asked for.
How to recognize it: the run stopped part-way with a message about no searches being left, or you had already run large searches earlier the same day.
What to do: wait for the counter to reset, or run from a different connected LinkedIn account. The remaining allowance is shown next to the account.
3. The people were already your contacts
An existing contact is reported as "already exists" and not counted as added, even in the case where Reply did move them into your sequence. So the sequence can gain people that the added count does not show.
How to recognize it: the results file is full of "already exists" rows and the sequence's contact count went up anyway.
What to do: nothing. Check the sequence rather than the import total.
4. A person's email address already belongs to someone else
If a row would create a contact whose email address is already held by a different live contact, the row is skipped. This is rarer from a LinkedIn search than from a CSV, because LinkedIn rows usually arrive without an address at all.
How to recognize it: the file shows the row as not added, and searching your contacts for that address finds a different person.
What to do: merge or correct the existing contact, then re-run.
5. The contact imported, but never reached the sequence or list
Adding a contact, adding it to a list and moving it into a sequence are separate steps. If the first succeeds and a later one fails, the contact exists in your account but is not where you expected, and no error is shown.
How to recognize it: the contact is in People but not in the sequence you ran the search from.
What to do: add them to the sequence manually. If it happens across a whole run, contact support.
Why the search stopped early
If the run ended before it finished, the notification names the reason. In plain terms:
| What you are told | What it means |
|---|---|
| The Sales Navigator session dropped | Your Sales Navigator subscription or session is no longer valid |
| The account is disconnected | The connection to LinkedIn expired and needs reconnecting |
| No access to this search | LinkedIn refused the search – usually a private list, or a URL your account cannot open |
| Too many requests | LinkedIn rate-limited the account. Reply retries a few times before giving up |
| The provider is unavailable | A temporary failure reaching LinkedIn. Retried automatically |
A search that stopped early keeps the contacts it had already imported.
FAQ
Can I run two LinkedIn searches at once?
Not on the same LinkedIn account; one search runs at a time and a second returns a "busy" message. Different connected accounts can run in parallel.
Do I need Sales Navigator?
Yes. The feature requires a LinkedIn account with Sales Navigator; other LinkedIn plans are not supported. If a URL is refused, that is the first thing to check.
Does this use credits?
No. It runs through your own LinkedIn account and consumes that account's daily search activity, not Reply credits.
Still stuck? Contact Reply support
If these steps didn't solve the problem, the Reply support team can look at your account directly. Open the Reply Help Center and send the team a message.
To get an answer faster, include:
- how many contacts the search reported and how many were added
- the results file from the finished-search notification
- which connected LinkedIn account you used
- roughly when it ran, and your timezone
Don't send passwords, API keys, or access tokens. Don't send your LinkedIn credentials either.
Related
- Why was a contact duplicated? – merging contacts that share a LinkedIn address
- Why were contacts not imported? – the same reasons, for CSV imports
- Why do LinkedIn steps fail? – connection and account problems
Build with Reply
- REST API: Contacts – check which of a list of people already exist before importing