Does ClientRadar use an exported cookie or token for X?

No. ClientRadar reads X through the session already logged in to your Chrome browser — the same requests you make by scrolling. There is no exported cookie driving your account from a server, which is the pattern platforms detect and restrict.

Do I hand over my X password?

No. You stay logged in to X in your own browser and ClientRadar reads through that session. No X password is entered into ClientRadar and no credentials are stored.

Which plan includes X?

X is one of the four platforms; access depends on your plan. See the pricing page for which platforms each tier covers, and the free tier and caps guide for the free-tier limits.

Setup

Connect X (Twitter) to ClientRadar

ClientRadar reads X through your own logged-in session — no exported cookie, no server bot. Here's how to connect X, set your searches, and confirm the radar is running safely.

ClientRadar finds leads on X by reading your timeline and searches through your own logged-in browser session — not through an exported cookie and not through a server-side bot. That distinction matters: cookie-injection and cloud automation are exactly the patterns platforms detect and restrict. ClientRadar reads like you scrolling. If you are signed in to X in Chrome, it can read; if you log out, it stops.

Before you connect

You’re logged in to X in the same Chrome profile as ClientRadar. Open x.com and confirm you are signed in. ClientRadar borrows this session — no exported cookie, no password handover.
You know what to watch. On X, buying intent shows up in searches and keywords more than in a single feed. Decide which terms surface people looking for what you offer.

Connect X in four steps

Sign in to X in Chrome. In the same Chrome profile ClientRadar runs in, open x.com and make sure you are logged in.
Decide what to watch. Pick the keywords and searches buyers actually use when they need your service.
Connect X in ClientRadar. Open the Networks view, find X, and connect it. ClientRadar confirms access using your existing X session — there is no exported cookie and no separate login.
Save your keywords and let it run. Add your keywords and searches to your radar settings, save, and let scanning run across the day.

If X drops or pauses

X sessions can end on their own or if you sign out elsewhere; when that happens ClientRadar shows needs reconnect for X and pauses scanning there. Sign back in and return to the ClientRadar tab — see Fix: a platform needs reconnecting. If X pauses with a resume time instead, that is the safety layer protecting your account after a warning sign — see Fix: a platform is in a protective cooldown. If X is connected but quiet, check your keywords in Scanning isn’t finding any leads.

Get started