Home → Use cases → Agencies

Client accounts, one browser each

An agency's problem is not one person with many accounts — it is many people touching many clients' accounts, on machines the agency does not fully control, with staff who join and leave.

What goes wrong without isolation

• Cross-contamination. Two clients' accounts opened in one browser share a fingerprint and an IP. To the platform they are related — which is a problem for the client, not just for you.
• Passwords in a spreadsheet. The usual handover mechanism, and the one that survives an employee leaving.
• Work trapped on a laptop. The person who set the accounts up is on holiday and nobody else can get in.
• Silent logouts. Someone opens a client account from home, the platform sees a new device and location, and the session dies mid-campaign.

The shape that works

A profile per client account, never per client

If a client has three ad accounts, that is three profiles. The moment two accounts share a profile they are permanently linked, and no amount of care afterwards separates them.

Groups that match how you bill

Name profiles so the client is the first thing you read, and group by client. Bulk actions then apply to exactly the set you mean — assigning a proxy to eleven profiles individually is where the mistakes happen.

A stable address per profile

Client accounts are long-lived, so they want a steady address rather than a rotating one — see residential vs datacenter. Match it to the client's actual market: a Manchester shop should not appear from Singapore.

Handover without passwords

Cloud sync means a colleague signs in and gets the profile definitions — names, groups, proxy bindings, fingerprints. Session cookies are exported deliberately when you want to hand over a live login, rather than being sprayed across a shared document.

Onboarding a new client

1. Create a group named for the client.
2. One profile per account they own, named Client — platform — account.
3. Buy or assign a proxy that exits where the client actually operates, and test it.
4. Sign into each account once, in its own profile, and let it settle before doing real work.
5. If routine checks are part of the retainer, build the process once and schedule it across the group — automation covers the shape.

Offboarding

When a client leaves, delete their group's profiles. Storage, cookies and fingerprints go with them, and there is no residue in a shared browser to leak into the next client's work. When a person leaves, they lose access by losing the account — not by you trusting them to forget a spreadsheet.

That is what team members are for: each person on the account gets their own login and access to only the client groups they work on, so removing one of them is deleting a login rather than changing every password you own.