Give every ads client a persistent, owned login environment.

Before you start

• Google Ads manager account (MCC) and Meta Business Manager access per client
• AliasMode installed with one group per client
• One proxy per client profile, in or near the client's market
• A media-buyer rota: who opens which client on which days

Step-by-step

1. 1

   Structure access officially first

   Link client Google Ads accounts to your MCC and grant Meta Business Partner or partner-business access. The profile never replaces platform permissions; it stabilizes the environment you use them from.

2. 2

   One profile per client login

   Create a profile per login the agency operates: client·google-ads, client·meta-bm. Fixed fingerprint seed. A client with both platforms gets two profiles.

3. 3

   Proxy per client, matched to market

   Attach one residential proxy per client, in the client's country. Campaign accounts logging in from switching geographies draw security reviews at the worst time.

4. 4

   Log in once, persist the session

   Log into the MCC or Business Manager inside the profile once. Cookies persist, so buyers open a returning session instead of a new device every week.

5. 5

   Group by client, tag by platform

   One AliasMode group per client, tags for platform and role. Contractors get workspace access to their client's group only.

6. 6

   Pre-check sessions before spend

   Before a buyer starts, launch the profile and confirm the session is live. For scripted checks, use the Local API to start the profile and inspect it over CDP.

   Step 6

   const res = await fetch('http://127.0.0.1:50400/api/v1/browser/start?user_id=' + profileId);
   const { data } = await res.json();
   const browser = await chromium.connectOverCDP(data.ws.puppeteer);
   // ... work inside the logged-in session ...
   await browser.close();
   await fetch('http://127.0.0.1:50400/api/v1/browser/stop?user_id=' + profileId);

7. 7

   Keep the 2FA map

   Record where each client's 2FA codes land — an authenticator on your side or the client's phone. A buyer locked out mid-flight is an incident; a documented 2FA map is not.

8. 8

   Hand off between buyers

   Close and sync the profile at shift end. The next buyer opens the same session through Cloud sync, on their own machine, with no credential movement.

The AliasMode workflow

1. 1

   Preflight before spend

   Proxy preflight confirms the exit country before any buyer opens a spend-capable account.

2. 2

   Local API session checks

   Scripted start, connectOverCDP, and stop let your internal tools verify sessions before shifts.

3. 3

   Cloud handoffs

   Persistent sessions move between buyers through encrypted sync — never through shared passwords.

Verify it worked

• Each client profile restores its session on relaunch with no security checkpoint.
• Preflight reports the client's market for every profile before spend.
• MCC and Business Manager roles match the signed access list per client.
• The buyer rota log shows one open session per profile at a time.

Cautions

• Google and Meta restrict certain regulated ad categories regardless of login hygiene; isolation does not change ad policy.
• Do not run client ad accounts from personal logins outside the agency structure; it breaks access audits.
• Shared office IPs across many clients' accounts create linking patterns — one proxy per client profile avoids it.