1. Key Points for Avoiding LinkedIn Restrictions with Edges
When implementing Edges for LinkedIn automation, it’s crucial to inform your users about a few key actions to prevent account restrictions. Key steps to follow:Step | Action |
---|---|
1. Avoid Multiple Automation Tools | Advise against using multiple automation tools simultaneously to prevent LinkedIn from flagging the account for suspicious activity. |
2. Match Timezone Settings | Ensure the timezone selected in Edges matches the user’s actual location or VPN country. |
Avoid Using Multiple Automation Tools Simultaneously
Using multiple automation tools at once with Edges can cause issues.- Why? Many automation tools don’t manage IP addresses properly, which could trigger flags on LinkedIn. When using multiple tools, LinkedIn may detect activity from different sources, increasing the likelihood of restrictions.
- The result: LinkedIn might flag the account for suspicious activity, potentially resulting in restrictions.
Ensure Timezone Settings Match
Thetimezone
selected in Edges must match the country where you’re logging into LinkedIn.
- Why it matters: The timezone field provisions a proxy IP matching that timezone/country. If the timezone in your Edges identity doesn’t align with your LinkedIn login location, LinkedIn may restrict your account.
- What to do: Always check that the timezone in your Edges identity matches the country where you’re logging into LinkedIn to avoid being flagged.
VPN Use: Match Locations Carefully
Using a VPN can be helpful but needs careful management.- Best practice: The country in your VPN should match the timezone set in Edges. If there’s a mismatch, LinkedIn might flag your activity as suspicious.
- Tip: Double-check that the timezone in Edges matches your VPN’s location, or disconnect the VPN when accessing LinkedIn to avoid issues.
What to Do if Your Client Gets a LinkedIn Restriction?
- Don’t worry! Restrictions are usually temporary. ⏳
- Steps to follow:
- Are other automation tools running alongside Edges?
- Does the timezone setting in Edges match the user’s actual location?
- If using a VPN, does the VPN location match Edges’s timezone setting?
2. Edges Smart Limits
Edges applies a set of limits to prevent accounts from getting banned. Edges protects your clients’ LinkedIn accounts with our unique Smart Limits system. By using Edges exclusively, clients can run a high volume of actions without issues. These limits help stay within LinkedIn’s daily action caps, preventing account restrictions.Smart Limits operate on a 24-hour sliding window.
What happens when the limit is reached? In real-time mode, requests will fail with a rate limit error. In async or schedule modes, tasks will be postponed for 24 hours and automatically resume once the limit is freed up.
- If the limit is hit (e.g., 1000/1000 actions), no new tasks are launched in async/schedule modes, or requests fail immediately in real-time mode.
- We periodically check to see if the limit is cleared, e.g., at 3 PM, there might be 100 actions freed up.
- The available actions may vary depending on when the limit was last checked.
Edges only tracks actions performed within the platform, not manual
actions on LinkedIn or using other automation tools.
3. Best Practices
- Scale your efforts: Use multiple identities and the identity_mode=auto feature to manage higher action volumes while staying within LinkedIn’s limits.
- Avoid overloading: Space out actions over time to improve efficiency and avoid triggering restrictions.
- Monitor activity: Regularly track identity usage to prevent exceeding limits unexpectedly.
- Choose the right execution mode: Use real-time mode for immediate results, async mode for large batches, and schedule mode for time-based automation.
4. LinkedIn Commercial Limits
All limits are based on a 24-hour sliding window, meaning they reset every 24
hours.
Limit Name (Per Day) | Value LinkedIn/Sales Navigator | Platform | Info | Action Link |
---|---|---|---|---|
Maximum connection requests | 25/30 | LinkedIn, Sales Navigator | Classic accounts can send up to 100 connection requests per week. | Connect LinkedIn Profile, Connect Sales Navigator Profile |
Maximum messages sent | 50/250 | LinkedIn, Sales Navigator | Message LinkedIn Profile | |
Maximum profile visits | 80/500 | LinkedIn, Sales Navigator | Remember that manual visits also count. For Sales Navigator, use the Visit Sales Navigator Profile Action to increase the limit. | Visit LinkedIn Profile, Visit Sales Navigator Profile |
Maximum contact info | 250 | LinkedIn, Sales Navigator | Extract LinkedIn Contact | |
Maximum search metrics | 1,000 | Sales Navigator | Search Sales Navigator Metrics | |
Maximum event invitations sent | 100 | Invite People to LinkedIn Event | ||
Maximum profile enrichments | 10,000 | Extract LinkedIn People Profile | ||
Maximum company enrichments | 10,000 | Extract LinkedIn Company Profile |
5. LinkedIn Usage Limits
Limit Name (Per Day) | Value LinkedIn/Sales Navigator | Platform | Info | Action Link |
---|---|---|---|---|
Maximum Search LinkedIn People | 300 searches/month | Classic Accounts | Users may encounter a restriction after 300 searches in a month. | Search LinkedIn People |
Maximum Search LinkedIn People | Unlimited | Sales Navigator Accounts | No search limit. | Search LinkedIn People |
Maximum Search Sales Navigator People | Varies based on account activity | Sales Navigator Accounts | 1 search page = 1 API call (each page contains 25 profiles, max 100 pages x 25). Example: 100 results = 4 pages = 4 API calls. | Search Sales Navigator People |
Maximum Search Sales Navigator Company Employees | 500 companies every 2 hours (w/ max 25 employees per company) | Sales Navigator Accounts | If max employee results are set to 250 → 2 companies every 2 hours. | Search Sales Navigator Company Employees |
Maximum Extract LinkedIn Connections | 30,000 connections per day | Classic Accounts, Sales Navigator Accounts | Extract all connections at once and set to repeat, ensuring only new, recent connections are captured. | Extract LinkedIn Connections |
Space out searches to avoid hitting your limits too quickly.
Use
identity_mode=auto
for automatic load distribution. If you hit rate
limits, take a 24-hour break, and/or add more identities, and/or use
identity_mode=managed
.