For PhantomBuster users
PhantomBuster runs from the cloud on your LinkedIn session cookie and a proxy you supply. Get an account where the li_at cookie, the IP, and the profile geo already match — so your Phantoms run instead of stalling on a security checkpoint.
Trusted by lead-gen agencies · 0.01% ban rate · 24h replacement SLA
PhantomBuster never logs into LinkedIn with a password — it acts on the li_at session cookie you paste in, executing each Phantom from PhantomBuster’s cloud through the proxy you attach. That architecture creates three predictable failure points: a proxy IP that doesn’t match where the account normally signs in, too many Phantoms firing in parallel on one cookie, and a cookie that silently expires mid-run. We provision against all three before the account reaches you.
When you load a li_at cookie into PhantomBuster from one country and the proxy resolves to another, LinkedIn sees a session that teleported. We pair the cookie with a static ISP residential proxy on an IP in the account’s passport country, so the login context is consistent from the first Phantom onward.
PhantomBuster lets you queue many Phantoms, and it is tempting to run Auto Connect, Message Sender, and Profile Scraper at once on one account. Concurrent cloud actions on a single cookie look nothing like a human. Our runbook caps safe simultaneous slots per account age and spaces launches.
A li_at cookie lasts until LinkedIn rotates it or you sign out elsewhere. When it dies, every Phantom on that account fails until you refresh it. We document how to pull a fresh cookie without tripping a re-verification and how to keep one stable session for PhantomBuster.
If an account restricts mid-campaign, your scheduled Phantoms are dead weight. Our 24h SLA either recovers the original via NFC passport or ships a like-aged replacement, with steps to repoint the same Phantoms at the new cookie.
Concrete outcomes when the cookie, proxy, and account age are aligned before you launch a Phantom.
Network Booster, Auto Connect, and Message Sender finish their runs instead of halting on a security checkpoint or 999 page.
PhantomBuster does not ship a proxy. Yours arrives already attached to the account, so you skip vetting datacenter pools that LinkedIn flags on sight.
Aged accounts hold up under Profile Scraper and Auto Connect volume that would throttle a fresh login within days.
A static ISP IP means the cookie loads from the same place every Phantom run — no impossible-travel flags between executions.
When a Phantom triggers an ID challenge, the NFC-verified human owner clears it, rather than the account being lost.
One line item covers the account and its proxy; you add only your PhantomBuster seat on top.
The specific configuration choices that matter for cookie-and-cloud automation.
You receive a working session cookie alongside the account, so you can drop it straight into a Phantom’s LinkedIn session-cookie field and launch.
The proxy is the type PhantomBuster recommends for LinkedIn — a fixed residential IP in the account’s country, not a rotating pool and not datacenter.
PhantomBuster-bound rentals come from profiles aged multiple years with real connection graphs, so Phantom-driven actions blend into existing behaviour.
A doc that maps account age to safe daily caps and to how many Phantoms can share one account without tripping LinkedIn.
Every account is backed by a passport-verified owner who can pass an ID upload or video check if a Phantom’s volume triggers one.
If the account restricts, you get a like-aged replacement within a day, plus the steps to swap the new cookie into your existing Phantoms.
How accounts driving PhantomBuster Phantoms perform across our customer base.
Composite use cases drawn from accounts running Phantoms in production.
“We kept getting checkpointed because our own proxy resolved to a different country than the profile. The account from 500accs arrived with the cookie and IP already matched, and our Auto Connect Phantom has run clean ever since.”
“The slot runbook was the part I didn’t know I needed. We were stacking Profile Scraper and Message Sender on one account in parallel and wondering why it kept dying. Spacing them per their guide fixed it.”
“Our li_at cookie expired over a weekend and every Phantom went dark. Their refresh steps got us a fresh session without a re-verify in about ten minutes. No lost pipeline.”
Composite use cases drawn from agency and in-house customers. Names and identifying details omitted to protect customer confidentiality.
Yes. PhantomBuster is a separate cloud SaaS. We supply the LinkedIn account, the matched proxy, and a working li_at cookie; you connect them inside your own PhantomBuster workspace.
PhantomBuster authenticates by LinkedIn session cookie. You paste the li_at cookie we provide into the Phantom’s LinkedIn session-cookie field and add the proxy we supply. No password is entered into PhantomBuster.
When LinkedIn rotates the cookie or you sign out elsewhere, the Phantom stops authenticating. You pull a fresh li_at from the browser on the account’s proxy and paste it back in. Our runbook walks through doing this without triggering a re-verification.
Sparingly. Many concurrent Phantoms on one cookie is the single most common ban cause we see. Our runbook gives safe simultaneous-slot counts by account age and tells you which Phantoms — like Auto Connect and Message Sender — should not fire in parallel.
No. PhantomBuster does not include a proxy and recommends a stable residential one for LinkedIn. The account ships pre-paired with a static ISP residential proxy in the matching country, so you skip sourcing one yourself.
The LinkedIn suite — Network Booster, Auto Connect, Message Sender, Profile Scraper, Search Export, and Activity Extractor. Aged accounts absorb the action and scrape volume that throttles fresh logins.
PhantomBuster executes from the cloud through your proxy, so to LinkedIn the session appears to originate at that IP. If the IP country differs from where the profile normally signs in, LinkedIn reads it as impossible travel and checkpoints the account.
No. PhantomBuster only sees a valid li_at cookie and the proxy you attach — the same inputs any LinkedIn user would provide. There is no rental signal exposed to the platform.
Stay inside LinkedIn’s own ceilings: roughly 20–25 connection requests and 40–60 profile views or messages a day on an aged account, lower for the first weeks. The runbook maps caps to each account’s age so you don’t over-drive a Phantom.
Pause the affected Phantoms and report it. We diagnose the cause and either recover the original through NFC passport verification or send a like-aged replacement within 24 hours, with steps to repoint your existing Phantoms at the new session cookie.
Aged account, working li_at cookie, and a static ISP residential proxy — paired and ready to paste into your first Phantom.