LUONG VAN VIET
Newbie
- Feb 13, 2020
- 46
- 42
Hey guys,
Reposting this one. The original version had a section comparing the two anti-detect browsers we use, with their pricing, and that got flagged as advertising. Fair enough, my mistake. Everything else is the same, and I've added a bit more detail on the MCC side since that's what most people asked about last time.
Quick note before anything else: I'm not naming the tools this time. Honestly it matters way less than people think. The discipline around how you use them is what keeps accounts alive.
The scale
Around 750 active browser profiles split across two anti-detect platforms. Team of 5, I'm the only admin.
MCC structure
This is the part I see people get wrong the most.
The mistake is dumping 50-100 accounts into one MCC and using your main Google account as the manager. That MCC will get flagged eventually. And when it does everything inside it dies at the same time.
We run 20 to 50 accounts per MCC depending on what's in it.
MCCs holding aged high spend accounts stay closer to 20. Losing one of those hurts so we keep the blast radius small. MCCs with newer or low spend accounts go up to 50 because replacing them is cheap and splitting them up isn't worth the admin time.
Each MCC is managed by a dedicated Gmail that does nothing else. It never runs ads directly. It exists purely to be a manager account.
Your personal Gmail should never touch an MCC that has live ad accounts in it. Google's enforcement cascades upward. If accounts inside get flagged the manager gets reviewed too, and if that manager is your personal account you've just linked your identity to the whole operation.
We learned this the expensive way. Lost a chunk of accounts early on because one manager email was shared across too much. Just sharing what's working until it stops working
Screenshots attached. One MCC overview showing 2.35M total spend and 1.81M clicks, plus an accounts list from a different MCC so you can see the structure. Account names and IDs are blacked out for obvious reasons.
Running two platforms
We split across two anti-detect browsers instead of putting everything in one.
Redundancy is the main reason. If one has an outage or ships a bad update that starts tripping detection, half the operation keeps running while we figure out what happened.
They also have different strengths. One is more stable on aged profiles, fingerprinting holds up better when a profile has months of history on it. The other has better team management, you can assign profiles to specific operators and see who opened what and when. With 12 seats that visibility is worth more than raw profile quality.
If you're picking one, what actually matters:
Datacenter, one per profile, never shared.
We tested residential pretty extensively. At our volume the price difference didn't justify the small improvement in ban rate. Datacenter is fine if your warm-up is solid.
One proxy one profile. This is the rule we never break.
Warm-up
New profile, then 3 to 7 days of manual browsing. Google search, YouTube, some Gmail activity. Then automated inbox activity to keep the Gmail looking alive. Then connect the Ads account. Then wait 48 hours before launching anything.
Skip any of these and your ban rate jumps immediately.
The 48 hour wait after connecting Ads is the one people skip most. Don't. It's free to wait and expensive not to.
Payment
One virtual card per account, never reused.
Shared billing is probably the clearest cross account signal Google has. Two accounts on the same payment method and they already know those accounts are related. Doesn't matter how clean your fingerprints are.
Team
I'm MCC admin only, I don't touch individual accounts day to day.
One team leader distributes accounts into folders by market and campaign type. Three operators run campaigns. One person watches account health and handles replacements.
Ban rate
15% monthly. At 750 profiles that's roughly 110 replacements a month.
We built this into how we operate. Replacement is a workflow, not an emergency. When an account dies there's already a warmed up profile sitting ready to take over.
What kills accounts fastest, in order:
Happy to answer questions on MCC structure, proxy setup, warm-up timing, whatever. Drop them below.
Reposting this one. The original version had a section comparing the two anti-detect browsers we use, with their pricing, and that got flagged as advertising. Fair enough, my mistake. Everything else is the same, and I've added a bit more detail on the MCC side since that's what most people asked about last time.
Quick note before anything else: I'm not naming the tools this time. Honestly it matters way less than people think. The discipline around how you use them is what keeps accounts alive.
The scale
Around 750 active browser profiles split across two anti-detect platforms. Team of 5, I'm the only admin.
MCC structure
This is the part I see people get wrong the most.
The mistake is dumping 50-100 accounts into one MCC and using your main Google account as the manager. That MCC will get flagged eventually. And when it does everything inside it dies at the same time.
We run 20 to 50 accounts per MCC depending on what's in it.
MCCs holding aged high spend accounts stay closer to 20. Losing one of those hurts so we keep the blast radius small. MCCs with newer or low spend accounts go up to 50 because replacing them is cheap and splitting them up isn't worth the admin time.
Each MCC is managed by a dedicated Gmail that does nothing else. It never runs ads directly. It exists purely to be a manager account.
Your personal Gmail should never touch an MCC that has live ad accounts in it. Google's enforcement cascades upward. If accounts inside get flagged the manager gets reviewed too, and if that manager is your personal account you've just linked your identity to the whole operation.
We learned this the expensive way. Lost a chunk of accounts early on because one manager email was shared across too much. Just sharing what's working until it stops working
Screenshots attached. One MCC overview showing 2.35M total spend and 1.81M clicks, plus an accounts list from a different MCC so you can see the structure. Account names and IDs are blacked out for obvious reasons.
Running two platforms
We split across two anti-detect browsers instead of putting everything in one.
Redundancy is the main reason. If one has an outage or ships a bad update that starts tripping detection, half the operation keeps running while we figure out what happened.
They also have different strengths. One is more stable on aged profiles, fingerprinting holds up better when a profile has months of history on it. The other has better team management, you can assign profiles to specific operators and see who opened what and when. With 12 seats that visibility is worth more than raw profile quality.
If you're picking one, what actually matters:
- Fingerprint stability across sessions. Does the profile look the same every single launch
- Per profile proxy assignment that doesn't leak
- Team access controls and activity logs if you have staff
- Profile export so you're not locked in
Datacenter, one per profile, never shared.
We tested residential pretty extensively. At our volume the price difference didn't justify the small improvement in ban rate. Datacenter is fine if your warm-up is solid.
One proxy one profile. This is the rule we never break.
Warm-up
New profile, then 3 to 7 days of manual browsing. Google search, YouTube, some Gmail activity. Then automated inbox activity to keep the Gmail looking alive. Then connect the Ads account. Then wait 48 hours before launching anything.
Skip any of these and your ban rate jumps immediately.
The 48 hour wait after connecting Ads is the one people skip most. Don't. It's free to wait and expensive not to.
Payment
One virtual card per account, never reused.
Shared billing is probably the clearest cross account signal Google has. Two accounts on the same payment method and they already know those accounts are related. Doesn't matter how clean your fingerprints are.
Team
I'm MCC admin only, I don't touch individual accounts day to day.
One team leader distributes accounts into folders by market and campaign type. Three operators run campaigns. One person watches account health and handles replacements.
Ban rate
15% monthly. At 750 profiles that's roughly 110 replacements a month.
We built this into how we operate. Replacement is a workflow, not an emergency. When an account dies there's already a warmed up profile sitting ready to take over.
What kills accounts fastest, in order:
- Shared proxies between profiles
- Reused payment methods
- No warm-up before running ads
- Launching campaigns within 24h of creating the account
- Personal Gmail as MCC manager
Happy to answer questions on MCC structure, proxy setup, warm-up timing, whatever. Drop them below.