- Joined
- Jul 5, 2023
- Messages
- 7
Collected the top problems from chats and added working solutions. Short, practical, straight in arbitrage slang.
1.
What’s the issue:
Google may request a selfie either when logging into the account or when trying to launch ads. This often happens if:
How it looks:
A pop-up appears asking for “Selfie verification” or “Confirm your identity via photo.”
How people solve it:
If the face doesn’t exist in the docs → don’t try, system compares photos.
What doesn’t work:
1.
Selfie Verification in Google Ads
What’s the issue:
Google may request a selfie either when logging into the account or when trying to launch ads. This often happens if:
- You just logged into a fresh account and went straight into Google Ads.
- You suddenly switch countries, IPs, devices, names, or payment methods.
- The Policy Risk Engine flags the profile.
- After a failed verification or suspicion of multi-accounting.
How it looks:
A pop-up appears asking for “Selfie verification” or “Confirm your identity via photo.”
How people solve it:
- Do the selfie via Google Ads interface.
Works in ~90% of cases if:- Face matches the document photo.
- Neutral background (no posters, people, filters).
- No masks, retouching, etc.

- If it fails — don’t waste time.
Easier to launch with a new account than to trick facial recognition. - Manual verification through third-party services.
Some teams solve this with document packs or dedicated verification workflows.
What doesn’t work:
- AI-generated