Built to keep your clients' LinkedIn accounts alive.
You run outreach on accounts that are not yours. One restriction and a client is gone.
So every number on this page is a real limit in the system, not a promise: connection requests at 3% of the account's connections (15 to 50 a day, under a weekly cap of 100 to 200), a warm-up that starts at 10% and grows 4 points per active day, and a review queue in front of every send.
Every account shows what ran, what is waiting, and why.
Every action type has its own independent budget.
Connections, messages, likes, and enrichments are all tracked independently. Budgets adjust per account tier (Free, Premium, Sales Nav, Recruiter) and are recalculated daily at midnight.
New actions start slow and ramp up with usage.
Each action type starts at 10% of its base limit. Active days add +4 percentage points. One idle day gets a grace period. After that, limits decay at 18% per idle day. Three weeks of consistent usage reaches 100%.
Activity that looks like a real person at work.
Actions are distributed across business hours in the account's local timezone, following a weighted curve that matches real human work patterns. Weekends are quieter, mornings busier.
Daily start varies by up to 30 minutes so the account never clocks in at the exact same time. Each action is staggered 45 to 120 seconds apart with random jitter.
Four checks before every single action.
No action reaches LinkedIn unless it passes every gate. If any check fails, the action waits. It doesn't fail, it doesn't retry blindly. It waits until the gate opens.
Every LinkedIn action must pass all four checks before dispatch. If any check fails, the action stays in WAITING. Never failed, never lost.
Safety is more than limits. It's how the system runs.
From dedicated IPs to orphaned job cleanup, the infrastructure is designed to make every action look like it came from a human sitting at their desk.
Questions about account safety
What does LinkedIn's automation warning mean, and what triggers it?
LinkedIn shows a notice saying it has detected a browser extension or third-party tool that goes against its User Agreement, and asks you to remove it. That notice is the first rung. The next is a temporary restriction, and if the pattern continues, a permanent one. What trips it is usually an extension injecting itself into LinkedIn pages inside your own browser. Volume does the rest: request rates a person could not produce, or one account showing up from a datacenter IP or from several devices in a day. CampaignStack sends nothing from your browser. Every action comes from one encrypted cloud browser profile per account, behind one residential IP, inside the daily budgets on this page.
Is LinkedIn automation illegal?
No. No law forbids automating your own account. It breaks LinkedIn's User Agreement, which bans bots and other automated ways of using the site, so the penalty is contractual: a warning, then a restriction on the account. The risk is to the account, which is why every number on this page is a limit the system enforces rather than a promise. What you do with the data you collect about other people is a separate question, covered by data-protection law.
How does LinkedIn detect automation tools?
By watching. Known browser extensions leave traces in the page, which is why extension-based tools draw the warning first. Request patterns give away the rest: the same action every 30 seconds, hundreds of profile views in an hour, a full day's invitations sent at 9:00, activity at 3 AM in the account's own timezone. The network too: a datacenter IP, or one account appearing from three countries in a day. This page answers each of those. Cloud profiles instead of extensions, jittered pacing inside business hours, one residential IP per account.
Will CampaignStack get my client's LinkedIn account restricted?
Automation carries risk on LinkedIn and no vendor can remove it. What the system does is hold every account under the observed platform limits: a daily budget per action type, a warm-up ramp for new accounts, business-hours pacing, one dedicated residential IP per account, and an automatic pause the moment LinkedIn pushes back. Those measures reduce the risk. They do not eliminate it.
How many LinkedIn connection requests a day is safe?
The daily allowance is 3% of that account's own network, never below 15 and never above 50, then clamped against a rolling 7-day cap running from 100 on a free account to 200 on Recruiter. A brand new account starts at 1 to 2 requests a day, not 15, and earns its way up.
How long does warming up a new LinkedIn account take?
Every account starts at 10% of its computed daily limit and earns roughly 4 points back per active day, per action type. Warming up messages does not warm up likes: each action type ramps on its own usage. From the account's page you can advance the ramp by 15% at a time, or skip to full capacity.
What happens when LinkedIn rate-limits an account?
A 429 or throttle signal caps that action type to the usage already spent, so nothing more of that type goes out that day. Three rate limits in 24 hours, or a single security check, pause that action family for 24 hours. Replies to people who wrote to you keep going, because answering someone is not the action that drew the limit.
Does CampaignStack send at night or at weekends?
No. Actions run 8 AM to 6 PM local on weekdays and 9 AM to 2 PM at weekends, and the daily start time shifts randomly so an account never begins at the same minute. Weekend sends drop 70%. Anything scheduled outside the window is deferred to the next morning, never dropped.
What happens to an account with fewer than 300 connections?
It sends no outreach and reads at half budget until it crosses 300. Job applications still go out, up to 5 a day, because an application answers a posting the employer published. A new account is protected until it has a natural connection base to send from.
Does every message need my approval?
Review mode is the default: every AI draft waits for a person to approve, edit or reject it. Auto-send is a choice you make per workflow, never a setting flipped for you.
Do you store the LinkedIn session cookie?
No. The cookie is used once, to open an encrypted Chrome profile on our server, and is never written to the database. Every later job runs as a tab inside that one profile, so LinkedIn sees one consistent device.
See the limits on your own accounts.
Connect one account free, with no card. The full safety system runs on every plan, the free one included, in review mode by default.