Google ads - Cloaking - Proxy - Systems fraud

For some months now I have not been able to advertise well on google ads, I only serve black ads in brazil, government ads that can only be advertised and scaled with cloaker, on the google ads search network there is only one advertiser with an account that does not fall with government ads, I have studied the standards, a friend close to this same person informed me that he does not use a proxy, only 4g or starlink, the pointing of his domain to the vps does not use the cloudflare proxy (I found this curious, because the cloudflare proxy prevents attacks and he has suffered attacks recently and because of his knowledge he knows he can activate the cloudflare proxy), another pattern I noticed is that the vps he uses has nginx and does a forced redirection, I believe he is using a cloaker within the site itself with parameters and filters through nginx,In addition, he runs ads to the white page and after a few days without changing the budget, he installs a cloaker on the domain of the google ads campaign, gradually changing keywords, titles and descriptions and gradually increasing the budget, in addition, he waits for the account to fall due to fraud in the systems and returns to it, in this way the account comes back stronger.


I'm going to do the same test, I'm using 4g in some accounts, heating well done, after that upload a campaign to white page, install my cloaker in the same domain as the campaign and follow the same steps as them, I would like to see with you how much you think that using 4g instead of residential proxy, using a famous hosting instead of vps with pointing through proxy can influence the longevity of a google ads account? This is the method I'm testing.

1. Mobile Data
2. Using AdsPower
3. Renowned hosting companies such as hostinger
4. Wait days to add a cloaker to the campaign link, without changing the link
5. Wait days to increase budget
6. The account contains a warm-up campaign for a company registered with google ads billing and the company's details at the bottom of the white page.

What can I improve? How valid do you think this is in the logenicity of an account?

sounds like a solid plan


though sometimes ive found that using vanilla firefox works wonders without uising antidetect

it seems to work great

Interesting.

I've seen this thread here before, which is going on right now. Maybe ask it that's a good thing to test there

https://www.blackhatworld.com/seo/ask-me-about-gambling-blackhat-ads.1687691/page-14#post-19541170

neathticsmellswitchmeg said:

sounds like a solid plan


though sometimes ive found that using vanilla firefox works wonders without uising antidetect

it seems to work great

Click to expand...

I'm using firefox on the accounts I'm testing, I'm testing 3 accounts, 1 with any proxy, 1 home proxy and 1 mobile data, both using firefox and they will follow the same line of account heating, I will vary keywords, titles and descriptions of all.

Interesting approach, I’ve been testing something similar with mixed results. One thing that made a big difference for me was shifting from residential proxies to stable mobile IPs (like you're doing) and using a VPS with tighter server-level controls (nginx rules help a lot).

Also, cloaker timing matters. I saw better longevity when using a cloaker that filters pre-request instead of relying solely on redirects. I tested a few like Jci, Trafficshield, Adspect etc., but TrafficShield stood out for me because of how it handles pre-filtering. Might be worth looking into if you're embedding on-domain.
Curious how your tests go with Hostinger, keep us updated.

You're on the right path. Using 4G and waiting to install the cloaker is a smart move. I’d recommend switching from Hostinger to a clean VPS to reduce risk from shared setups. Make sure the white page content aligns with your ad during warm-up. Keep testing and adjusting. This method looks promising.

I've tested something very similar in BR gov niche—4G IPs + clean warm-up + delayed cloaker activation does help a lot. Using Hostinger is okay, but I'd be cautious—popular hosts = higher footprint. I’d go for a quieter VPS with raw DNS if longevity is the goal.
Also, if your NGINX cloaker is basic (IP/User-Agent), consider testing more advanced filtering. I’ve had better stability using TrafficShield lately—clean redirect timing, solid bot filtering. NoIPFraud’s decent too if you're self-hosting.
Let us know how your test plays out, sounds like you’re on the right track.