Google Ads - account is suspended for Circumventing systems policy

Hi,

I have a situation that seems weird to me. I created an Ads account to advertise a legitimate, regulated business in the UK. I created a few ads that ran ok for about 2 weeks. On week 3 my account got suspended for Circumventing systems policy. I filled the appeal form and it got reactivated in 2 days. A few hours later it got suspended again. This time I disabled all the ads, filled in the appeal again and the next day it got reactivated. I did NOT start any campaigns this time, wanted to make sure that all is ok. The account got suspended a third time after less than 24 hours passed. NO ads or campaigns were running.

I got sent a business operations verification which I filled in, I removed all the ads and campaigns from my account to make sure nothing was wrong, I paid the outstanding balance of around £70 for the ads, I filled another appeal to get my account reactivated and got refused this time by the message that my account was and still is violating the Circumventing systems policy and that the decision is final and I should not try to open another account with google.

Completely lost at this point. What can I do now? I only was trying to advertise my legitimate business and as far as I am aware was not trying to circumvent anything. Google never sent me any explanation about what was wrong.

I did get disabled by Facebook last week for Circumventing systems too, I -think- it was because of my URL cloaking but not entirely sure.

A friend of mine thinks it is because my account as well as my page was cold (never used it).

This means Facebook thinks my account was sold to someone that sells black products/ads because there is a market for buying and selling "clean" Facebook profiles.

I deleted my campaigns and they stopped blocking me...

But yeah, it seems to be dangerous to start a new account and already do a "big" ad campaign in it.

Are you using tracking software like voluum, hasoffers, or similar? If you remove any redirects before your destination URL it should resolve the issue.