Argus for affiliate marketing

Isolation · Fingerprints

A ban should cost you one account, not the shelf it sat on

The expensive failure in this business is never the first ban. It is the hour afterwards, when accounts that had nothing to do with it start going down too — because they were all opened from the same browser, on the same machine, from the same address, and the platform had already worked out they were one operation.

In Argus each account is a profile, and each profile starts from its own directory — its own storage, cache and cookie jar, with session restore off so a previous run cannot resurface inside a new one. On top of that sits a coherent hardware identity: platform, CPU cores, memory, screen, timezone and languages generated together, so nothing about the device contradicts anything else about it. Two of your profiles have no more in common than two strangers do.

Worth saying plainly, because this category is full of people who will not say it: that is separation, not immunity. Argus makes it hard for a platform to join two accounts by what the browser reveals. It cannot make a campaign compliant, and it does not promise an account survives what you do with it.

Proxies

Run the geo you are buying, and know the exit is what it claims

An offer that pays in Brazil is reviewed by people in Brazil, priced against Brazilian inventory, and looks wrong the moment its account signs in from Frankfurt. Argus keeps a shared proxy library rather than a text field per profile: assign the Brazilian exit to the Brazilian assets, the German one to the German assets, and change either without touching the profiles that use it.

The part that protects the account is the checking. Every proxy is health-checked for its egress IP, the country it lands in and its latency, and one that fails its check blocks the launch instead of quietly falling back to your own connection and stamping your home address onto an account that has only ever lived somewhere else. The check also flags an exit sitting on a datacenter network and names the provider behind it — which is the most ordinary reason a fresh account gets asked for documents on day one. Authenticated SOCKS5 works, which plain Chromium cannot do at all, and WebRTC is sealed as browser policy so a page cannot read your real address around the proxy.

Proxies also expire, usually at the worst moment. Record when a term ends and Argus warns you a week out, then asks you to confirm before launching anything behind one that has already lapsed.

Profiles · Folders

Two hundred accounts is a list problem before it is an account problem

At three accounts you remember everything. At two hundred you are hunting for the one that was warming for a vertical you paused in March, and the tool either handles that or it is furniture. Argus sorts profiles into folders with tags, custom status labels and per-profile notes, and the list searches, filters and pages rather than scrolling forever.

Everything that would be tedious one at a time is a bulk operation: launch a selection, edit a selection, delete a selection. Accounts arrive by CSV import and leave by CSV export, so a list you already keep in a spreadsheet does not have to be retyped. Delete is soft — a profile goes to Trash and comes back — which matters on the day the selection you just acted on was the wrong one.

Cookie sets

The session belongs to the account, not to whoever signed in

Sign in once, save the session as a cookie set, and assign it to the profile. The cookies are seeded into the session at launch, so the profile opens already signed in — no password in a group chat, and no waiting on the one person whose phone receives the codes.

The library is shared, so a set moves between profiles without being re-uploaded, and sessions inherited from a previous setup import from a file or a whole folder at once. When a buyer joins or leaves, the accounts stay where they are: nothing lived on their laptop, so nothing leaves with it.

Automation · Schedule · Datasets

Warm-up and the morning check are jobs, not afternoons

A new account needs hours on it before it can be trusted with budget, and those hours have to be spread out rather than crammed into one sitting. That is a calendar entry: pick the automation that does the browsing, name every profile it runs on, and repeat it 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.

The morning pass over live campaigns is the same machinery pointed at a different question, and the answers land somewhere you can use. The last step writes what it found into a dataset — a table your workspace owns, with columns you named — so today's account statuses and yesterday's flags sit in one place instead of in a run log one person happens to read. Tomorrow's run loads rows back out of that same table to decide what to work on.

Two limits 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 an overnight calendar has to stay awake; Keep awake stops it idling, though a closed lid still sleeps. And two machines signed into one workspace cannot double-run a slot: the first to reach it claims it and the other steps aside.