Argus for advertising agencies

Cookie sets

Five people, one Instagram login, no password in the group chat

A client's account in Argus is a browser profile, and the login lives in the profile — not with a person. Sign in once, save the session as a cookie set, and assign it to the profile. From then on the cookies are seeded into the session at launch, so whoever opens the profile — the buyer running the campaign, the designer swapping a creative, the account manager pulling a report — lands already signed in.

Nobody pastes a password into the group chat. Nobody texts the one colleague whose phone gets the login codes. And when a client arrives with sessions from a previous setup, you import the cookie files — one at a time or a whole folder — into a shared library and swap sets between profiles without ever re-uploading them.

Fingerprints · Isolation

The platform sees one steady device, not your whole office

Ad platforms flag accounts when the device behind them keeps changing — and an account opened from four laptops, two operating systems and one phone keeps changing. An Argus profile presents the same coherent hardware identity on every launch, from every seat: platform, CPU, memory, screen, timezone and languages generated together so nothing contradicts anything else. To the platform, the account lives on one believable machine that never changes, no matter who on the team opened it today.

Just as important is what the profiles don't share. Each one starts from its own directory — separate storage, cache and cookie jar — so two clients' accounts never touch, even side by side on the same machine. If one account hits a checkpoint, it is that account's problem, not a thread that unravels your whole roster.

Proxies

Run the ads from where the audience lives

The client sells in São Paulo; your team sits in Lisbon. Assign each of that client's profiles a Brazilian proxy from the shared library and every session — the ads manager, the organic posting, the page you open to check how a campaign actually renders — arrives from the geography where the audience lives. Different client in a different market? Different proxy, same launcher, side by side.

The part that saves accounts is the checking. Argus health-checks every proxy and reports the egress IP, its country, and the latency — and a proxy that fails its check blocks the launch entirely, instead of quietly falling back and stamping your Lisbon office IP onto an account that has only ever lived in Brazil. Authenticated SOCKS5 — the variant plain Chromium cannot speak at all — is handled inside the browser, and WebRTC is sealed so a page cannot read your real address around the proxy.

The whole path, from the library to the egress IP, is written up on its own page: how proxies work in Argus.

Cloud sync · Teams

Handover without the handover meeting

A buyer leaves, a new one starts Monday. In most shops that is a week of "which accounts did she run, where are the logins, why is this one asking for a code sent to her phone". In Argus the new hire signs into the workspace with an email and password, and the roster is simply there: a folder per client, every account a row with its status label and notes, every row launchable. Nothing lived on the old buyer's laptop, so nothing left with it.

The whole team shares one pool of profiles, proxies and cookie sets — seats on one workspace, not licence keys emailed around — and two people working the same list at once cannot overwrite each other. Client offboarding is the same picture in reverse: their folder, their profiles, their proxies, handed off or retired in one place.

Extensions · Automation

The tooling is set up once, and the routine runs itself

The utilities a media team actually uses — a cookie manager, a proxy helper, an SMS verification tool — are installed once for the whole organization and materialize on every machine that needs them. Four ship built in; your own come from a Chrome Web Store link or a folder.

The morning routine — open each client's ads manager, check the campaigns are delivering, note anything flagged — can run as an automation: workflows pinned to every profile's start page, or driven from your own scripts through the local API. The checks happen in the right profile, behind the right proxy, without a human clicking through forty tabs.

Schedule · Datasets

The warm-up runs at seven every weekday, and the results are in one table by nine

A new client account needs hours on it before it can be trusted with a budget, and those hours have to be spread out rather than crammed into one afternoon. In Argus that is a calendar entry: pick the automation that does the browsing, name every profile it should run on, and set it to repeat on the weekdays you choose — with a start and end day when the warm-up is only meant to last a fortnight. The entry works through its profiles one at a time, each behind its own proxy, cookies and fingerprint, and the day cell afterwards says whether it finished, partly failed or was missed.

Where the results land matters as much as the run. The last step writes what it found into a dataset — a table your workspace owns, with columns you named — so this morning's account status, yesterday's flagged campaign and last week's follower count sit in one place the whole team opens, instead of in a run log one person happens to read. Tomorrow's automation loads rows back out of that same table to decide what to work on.

Two caveats, both worth knowing before you build the week around it. Entries fire only while the launcher is open — a slot it was closed for is marked missed and skipped, never caught up — so the machine holding the overnight calendar has to stay awake; Keep awake stops it idling, though a closed lid still sleeps. And when two people are signed into the same workspace, a slot cannot double-run: the first machine to reach it claims it and the other steps aside.