Home → Use cases → Affiliate marketing
Networks, traffic sources, one profile each
An affiliate's login list grows sideways: four networks, a tracker, two or three traffic sources, a spy tool, the landing page host, and a payment dashboard. Holding all of those is normal and permitted. Running them through one browser is what turns a routine review of one account into a question about all of them.
What this page is about
Keeping accounts you legitimately hold from being wrongly associated, and not losing sessions every time you switch machines. It is not about holding several accounts where a network's terms permit one, or about returning after a ban. Isolation does not make a prohibited thing permitted, and the networks in this industry are better at detecting duplicate affiliates than the tooling sold to hide them.
What goes wrong without isolation
- Networks see one operator. Four network accounts from one fingerprint and one IP are, to a compliance team, one relationship. Fine until one of them asks a question.
- Traffic source accounts inherit each other's history. Ad platforms associate accounts by device and address, so a problem on one reaches the others without anyone deciding that it should.
- Sessions drop constantly. Laptop at home, desktop at the office, a VPS when travelling. Every switch looks like a new device, and the response is a logout and a verification challenge.
- Everything lives on one machine. The sessions, the saved logins and the two-factor state sit on whichever computer you set them up on, so working elsewhere means setting them up again.
The shape that works
One profile per account
Not per network, per vertical or per campaign: per account. Two accounts opened in one profile share a fingerprint and a cookie jar from that moment on, and nothing undoes it later. This is the decision that costs nothing on day one and cannot be fixed on day ninety.
A proxy per profile, and leave it alone
Rotating addresses is the instinct and it is the wrong one here. What you want is the opposite: each account always arriving from the same place, so it never generates a location-change signal at all. Match the proxy to the profile properly, because a timezone that contradicts the IP is a louder signal than a plain residential address with nothing to hide. For the difference between proxy types and where each belongs, see residential against datacenter.
Groups that match how you think
Group by network, by traffic source, or by vertical, whichever is how you actually navigate. The grouping matters more than it sounds once there are sixty profiles, and it is what makes handing a vertical to a media buyer a single action rather than an afternoon.
Sessions that follow you
A profile carries its cookies and its logged-in state, and cloud sync means opening it on another machine finds you already inside. That is the difference between a laptop you can work from and a laptop you have to re-authenticate on. If you work with a buyer or a VA, team members get their own logins and per-group access rather than your password.
Automating the dull half
Pulling yesterday's numbers out of four networks and a tracker every morning is mechanical, and no-code RPA will do it per profile, with the local API and an MCP server if you would rather script it. Worth stating plainly: that is for collecting data you already have access to. Automated clicks or manufactured conversions are detectable, are fraud against the advertiser, and no amount of fingerprint work makes them anything else.
What isolation does not separate
- Payment details. The same payout account or card across several network accounts is a direct link at the account level, far below anything a browser controls.
- Identity documents. Networks that verify affiliates keep what you sent them, and the same documents connect accounts permanently.
- Domains, pixels and creatives. Shared landing pages or tracking across accounts associate them regardless of which browser loaded them.
- Behaviour. Identical campaign structures appearing across accounts within minutes is a pattern, and behavioural detection runs independently of fingerprints.
Browser isolation closes one category of link. It is worth closing, and it is not the only one open.
Setting it up
- A group per network or traffic source.
- A profile per account, named so you know what it is six months later.
- A proxy bound per profile, verified once in the fingerprint test.
- Log in once inside the profile and let the session stay there.
- Record the reporting you do every morning as a process and run it across the group.
Three profiles are free, which is enough to move one network across and see whether it holds up before moving the rest.
Related: ad accounts, social media management, agencies, how accounts get linked.