This guide shows which metrics to watch while your campaigns run, how to keep pending requests under control, and what to do if LinkedIn warns or restricts your account.
LinkedIn restricts accounts that look spammy or go over its activity limits.
Track your account health
Run a weekly health check
Keep pending requests under control
Avoid the common causes of restrictions
What to do after a LinkedIn warning
What to do if your account is restricted
Swap out an account that needs a break
Common mistakes when monitoring accounts
Track your account health
Check these signals for every account at least once a week. Compare each account with its own usual numbers, not only with general benchmarks: a steady decline is an early warning even when the numbers still look fine. Acceptance rate is on the LinkedIn Reports dashboard, and SSI score and limits are in your LinkedIn account settings.
| Signal | Healthy | Monitor | Replace account |
|---|---|---|---|
| Acceptance rate | Above 40% | 25% to 40%: keep connection requests at 20 to 30 per day or fewer. | Below 25%: do not raise limits, improve your targeting and connection notes first. |
| Acceptance trend | Stable or growing compared with the account's usual rate. | Falling a little for two weeks in a row: review the list and connection notes before the next week. | A sharp drop within one week: lower the daily limits for this account and pause new connection requests until you find the cause. |
| Pending requests | Well under the auto-withdrawal threshold you set. | Growing week after week: withdraw the oldest requests in small batches. | Close to 300 or more (set a lower bar for accounts younger than 6 months): stop new connection requests and withdraw requests older than 14 days. |
| SSI score | Stable or growing | A small drop: keep your current limits for now. | A noticeable drop: lower your daily limits to match the new score. |
| Daily volume | Within your safety limits, with room to spare. | At the maximum limit every day. | Rising while acceptance falls: lower the limits back to the last stable level. |
| LinkedIn warnings | None | Any warning: pause outreach for 2 to 3 days, then resume at your last stable limit. |
See the recommended limits for each SSI score in this guide, and what each campaign metric means in this guide.
Run a weekly health check
Pick one day a week, for example Monday, and spend 15 to 30 minutes on it. If you run several accounts, the LinkedIn Reports page shows the metrics of every account side by side, and the LinkedIn accounts page shows each account's SSI score and limits.
- Review each account. Open LinkedIn Reports and check acceptance rate, pending requests, daily volume and reply rate for every account. Then check the SSI score of each account on the LinkedIn accounts page.
- Compare with last week. Look at the direction, not just the number. An account that went from 45% to 32% acceptance needs attention sooner than one that has stayed at 30%.
- Mark each account. Use the table above to mark it as healthy, monitor or replace account.
- Fix the cause. For accounts to monitor, check the list and connection notes. For accounts to replace, lower limits or swap the account out of the campaign.
- Check the workload. Make sure one account is not doing most of the work in every campaign.
If several people run outreach, agree on who checks each account, so warning signs are not left for someone else to notice.
Keep pending requests under control
Many unanswered connection requests tell LinkedIn that you contact people who do not expect you. This lowers your account rating and can lead to restrictions.
Turn on automatic mode on the Connection requests page, and Snov.io withdraws old requests for you once they reach the threshold you set. To withdraw them manually or adjust the settings, see this guide.
If you withdraw requests manually, spread them over several days instead of removing hundreds at once.
Avoid the common causes of restrictions
Running automation and manual outreach at the same time
Automated actions count toward the same LinkedIn limits as your manual ones. If you also send requests and messages yourself, lower your daily automation limits, or pause manual outreach while a campaign runs.
Sending too many connection requests or messages
Connection requests and messages have the strictest LinkedIn limits. Around 20 to 30 per day is a safe zone for most profiles. To reach more prospects, use InMail, which has fixed monthly limits, or add email steps to your sequence.
Browsing in robotic patterns
LinkedIn does not publish its limits, and even manual activity can trigger a warning. Avoid patterns such as opening profiles from search results one by one at high speed.
Low acceptance and response rates
When many people ignore your requests or click "I don't know this person", your SSI drops. Personalize your connection notes and send requests only to prospects relevant to your profile.
Using more than one automation tool
Never run the same LinkedIn account in two automation tools at once. It doubles your activity even if each tool uses safe limits, and overlapping schedules almost always lead to a restriction.
Low SSI score
A low SSI combined with high activity is a common reason for restrictions. See how to raise your score in the scaling guide.
What to do after a LinkedIn warning
A warning about suspicious activity is most often triggered by going over the limits or by a sudden increase in activity. It does not mean that LinkedIn detected Snov.io.
- Pause outreach for 2 to 3 days. Pause the campaigns that use this account.
- Resume at your last stable limit. Check that your limits match your current SSI score.
- Keep manual activity low. Focus on posting and commenting, which helps your SSI.
- Grow volume again with warm-up. Turn on warm-up mode before you raise your limits.
What to do if your account is restricted
Restrictions are often temporary and lifted after a few days. While your LinkedIn account is unavailable, keep your outreach going by email: prospects from Snov.io Finder tools come with both an email address and a LinkedIn URL.
- Switch senders. Pause the campaigns that use the restricted account, or add backup profiles with LinkedIn rotation so the campaign keeps running. To move its prospects to another account, follow the swap-out steps.
- Reconnect the account. When the restriction ends, check the connection status in your LinkedIn account settings. If you see an error, click the Edit icon, choose Reconnect and follow the instructions.
- Resume with low limits. In Safety limits, set 10 to 20 actions per day and keep them for a week.
- Increase gradually. Add 1 to 2 actions per action type each week while your SSI grows.
Swap out an account that needs a break
When an account is restricted, gets a warning or lands in the replace account column, move its outreach to a healthy account and let it rest.
- Pause the campaign that uses the account.
- Replace the sender. Remove the account from the campaign's LinkedIn senders and add a healthy one. See how to rotate multiple LinkedIn senders.
- Reassign its recipients. Recipients who already got a step from the removed account are paused. In the campaign's recipient list, choose which account continues their sequence and set their status back to Active. See how to manage paused and unassigned recipients.
- Resume the campaign.
- Let the account rest for about a week, withdraw its oldest pending requests, then bring it back at 10 to 20 actions per day.
Common mistakes when monitoring accounts
- Waiting for a restriction. Warning signs usually show up days earlier as falling acceptance and growing pending requests. Act when an account moves to monitor.
- Relying on one top account. If one profile does most of the work, it reaches its limits first and puts the whole campaign at risk.
- Letting pending requests pile up. Keep automatic withdrawal on for every account.
- Raising volume before fixing targeting. More requests to the wrong people lowers acceptance even faster.
- Ignoring the first message after a connection. If acceptance is healthy but replies are low, change the first message, not the limits.
- Sharing one location across accounts. Give each account its own proxy that matches where its owner usually logs in.
Sorry about that 😢
How can we improve it?