LUONG VAN VIET
Newbie
- Feb 13, 2020
- 16
- 11
Hey,
Running Google Ads at scale means managing accounts the way most people don't talk about publicly. Here's our actual setup — no theory, just what we're running right now.
---
The scale
Two anti-detect tools running simultaneously:
- GoLogin: 281/300 profiles (Business plan, $594/month)
- OmniLogin: 465/600 profiles (Pro, $123.9/month, 12 team members)
Total: ~750 active browser profiles. Team of 5, I'm the only admin.
Screenshots of both billing pages attached below.
---
MCC structure — this is the part most people get wrong
The biggest mistake I see: dumping 50-100 accounts into one MCC and using your main Google account as the manager.
When that MCC gets flagged — and eventually it will — everything dies together.
Our rule: max 20-30 accounts per MCC. Each MCC managed by a dedicated Gmail that exists solely as a manager account, never used to run ads directly. Your personal Gmail should never touch an MCC that has live ad accounts in it.
Why? Because Google's enforcement often cascades upward. If accounts inside the MCC get flagged for policy issues, the manager account gets reviewed too. If your personal account is that manager, you've just connected your identity to the whole operation.
Separate manager emails. Separate from everything personal. This alone saved us from several full wipes.
The MCC overview screenshot is attached — you can see €2.35M total spend, 1.81M clicks across one MCC. The campaign spend screenshots show current active numbers, not lifetime totals.
---
Why two tools?
GoLogin handles long-running, higher-value accounts better. More stable fingerprinting, less friction on aged profiles.
OmniLogin wins on team management — you can assign specific profiles to specific team members, track who opened what and when, and run automation flows directly inside the app. At 12 members across the team, that visibility matters.
We use GoLogin for accounts we want to run long-term. OmniLogin for volume operations where we're cycling through profiles faster.
---
Proxy setup
Datacenter proxies — one per profile, never shared. We tested residential extensively. At our scale the cost difference didn't justify the marginal improvement in ban rate. Datacenter works if warm-up is done right.
One proxy = one profile. Non-negotiable.
---
Warm-up process
New profile → 3-7 days manual browsing (Google search, YouTube, Gmail activity) → OmniLogin auto-care Gmail feature for inbox activity → then connect Google Ads account → 48h before launching any campaign.
Skipping any of these steps spikes your ban rate immediately. The 48h wait after connecting Ads before running campaigns is something a lot of people skip. Don't.
---
Payment method
One virtual card per account. Never reuse across profiles. Shared billing is one of Google's clearest cross-account signals — if two accounts share a payment method, Google already knows they're related.
---
Team structure
I'm MCC admin only — I don't touch individual accounts day to day. One team leader distributes accounts across folders by market and campaign type. Three operators run campaigns. One person monitors account health and manages replacements.
---
Ban rate
15% monthly. At 750 profiles that's ~110 replacements per month. We build this into operations — replacement is a workflow, not a crisis. When an account dies, there's already a warmed-up profile ready to swap in.
What kills accounts fastest:
- Shared proxies between profiles
- Reused payment methods
- No warm-up before running ads
- Launching campaigns within 24h of account creation
- Personal Gmail as MCC manager
---
Happy to answer questions on MCC structure, tool comparison, proxy setup, or anything else specific. Drop them below.
Running Google Ads at scale means managing accounts the way most people don't talk about publicly. Here's our actual setup — no theory, just what we're running right now.
---
The scale
Two anti-detect tools running simultaneously:
- GoLogin: 281/300 profiles (Business plan, $594/month)
- OmniLogin: 465/600 profiles (Pro, $123.9/month, 12 team members)
Total: ~750 active browser profiles. Team of 5, I'm the only admin.
Screenshots of both billing pages attached below.
---
MCC structure — this is the part most people get wrong
The biggest mistake I see: dumping 50-100 accounts into one MCC and using your main Google account as the manager.
When that MCC gets flagged — and eventually it will — everything dies together.
Our rule: max 20-30 accounts per MCC. Each MCC managed by a dedicated Gmail that exists solely as a manager account, never used to run ads directly. Your personal Gmail should never touch an MCC that has live ad accounts in it.
Why? Because Google's enforcement often cascades upward. If accounts inside the MCC get flagged for policy issues, the manager account gets reviewed too. If your personal account is that manager, you've just connected your identity to the whole operation.
Separate manager emails. Separate from everything personal. This alone saved us from several full wipes.
The MCC overview screenshot is attached — you can see €2.35M total spend, 1.81M clicks across one MCC. The campaign spend screenshots show current active numbers, not lifetime totals.
---
Why two tools?
GoLogin handles long-running, higher-value accounts better. More stable fingerprinting, less friction on aged profiles.
OmniLogin wins on team management — you can assign specific profiles to specific team members, track who opened what and when, and run automation flows directly inside the app. At 12 members across the team, that visibility matters.
We use GoLogin for accounts we want to run long-term. OmniLogin for volume operations where we're cycling through profiles faster.
---
Proxy setup
Datacenter proxies — one per profile, never shared. We tested residential extensively. At our scale the cost difference didn't justify the marginal improvement in ban rate. Datacenter works if warm-up is done right.
One proxy = one profile. Non-negotiable.
---
Warm-up process
New profile → 3-7 days manual browsing (Google search, YouTube, Gmail activity) → OmniLogin auto-care Gmail feature for inbox activity → then connect Google Ads account → 48h before launching any campaign.
Skipping any of these steps spikes your ban rate immediately. The 48h wait after connecting Ads before running campaigns is something a lot of people skip. Don't.
---
Payment method
One virtual card per account. Never reuse across profiles. Shared billing is one of Google's clearest cross-account signals — if two accounts share a payment method, Google already knows they're related.
---
Team structure
I'm MCC admin only — I don't touch individual accounts day to day. One team leader distributes accounts across folders by market and campaign type. Three operators run campaigns. One person monitors account health and manages replacements.
---
Ban rate
15% monthly. At 750 profiles that's ~110 replacements per month. We build this into operations — replacement is a workflow, not a crisis. When an account dies, there's already a warmed-up profile ready to swap in.
What kills accounts fastest:
- Shared proxies between profiles
- Reused payment methods
- No warm-up before running ads
- Launching campaigns within 24h of account creation
- Personal Gmail as MCC manager
---
Happy to answer questions on MCC structure, tool comparison, proxy setup, or anything else specific. Drop them below.
Attachments
-
3.png -
2.png -
gen-n-z7955195535172_30dd41c1f0a21770e361d12572999990.jpg -
gen-n-z7955183588431_70e4b655163cdbb789b0cfb339d87148.jpg -
gen-n-z7955183600464_867d38116f61371a682a6296cf33a1a2.jpg -
gen-n-z7955183595757_48f23314fbfad4490afb3318168cf079.jpg -
gen-n-z7955183583492_7cf3fc8d19ca1ca4489102d7f79cd7f6.jpg -
4.png -
1.png
