AdMob cash practice, 15 days to successfully remove invalid traffic restrictions

Since 2020, AdMob has gone through several major changes, using its powerful technology to combat all kinds of violations. Starting with the closure of Cheetah Mobile in February, AdMob has focused on a number of violations.

I recently experienced a wave of policy limiting. I launched my APP in early June, and it started rolling out in mid-June. Then I saw AD revenue on AdMob. On June 24, when the AD fill rate dropped and the mail came in, AdMob restricted the AD display because they suspected we had a fake traffic problem.

Seeing the restrictions on advertising display, I wondered if I was stepping into a giant pit again. At the time, the only AD alliance the APP had picked up was AdMob. It was frustrated and didn’t know what to do about it. Then I read some introductions on the Internet, but I was restricted by the policy. The reason given in the email was invalid traffic.

Then I read AdMob’s invalid traffic policy, which reads as follows:

We carefully reviewed the entire process of our APP, from development to release. None of us clicked on the official ads, and the testing process used test ads all the time. I don’t know why the flow is restricted.

Then we took a closer look at AdMob’s report and found some clues. On 18th, there were less than 200 AD requests and only 60 displays, and the eCPM for 1,000 displays was $8.03. APP users are mainly from Indonesia. Developers who are familiar with the region should know that the price of 1,000 displays in Indonesia should be less than 3 DOLLARS, and most of them are only about 0.8 dollars.

However, it was the abnormal data on this day that triggered the policy traffic limiting measures and was judged to be invalid. According to AdMob’s prompt, the limit is up to 30 days, during which time the program is automatically reviewed.

At this time, we can’t do anything, nor can we stop harvesting. If we want to wait for 30 days, it’s a waste of traffic. When traffic was restricted, the AD display match rate went from 99 percent to less than 4 percent.

We also started to look for other advertising platforms, and later connected with The Audience Network of Facebook. The version was updated on July 1. Then, on July 3, AdMob’s AD traffic was back to normal, but a look at the AdMob background showed that the policy alert was still there.

In the following days, I checked the background of AdMob every day to see whether the policy restriction prompt message was still in place. After July 3, the display data of ads I saw had returned to normal, but the policy restriction prompt still existed. It wasn’t until July 9 that the notification of the policy disappeared from AdMob’s background that I checked my email and didn’t get an email reminding me to lift the restrictions.

Back to normal, our AdMob has had no other exceptions since then. The next step is to wait for the income to break $100, and then complete the first collection. AdMob’s AD monetization process is complete.

After this, we understand that AdMob monitors all AD accounts, and if it finds something unusual, it limits traffic. Especially just apply for the account, must pay attention to. If you are blocked, keep your AD requests normal and check your traffic channels. The author of this APP acquisition is Google Ads. I believe there is no problem with the flow. At the beginning, we were not sure how long it would take to lift the restriction. Fortunately, the actual consumption was much less than we expected, and the time of restricting the flow lasted for 8 days.

Finally, I hope every developer can realize excess cash. I just got involved in overseas APP development, and there were a lot of pitfalls. Some of them passed, and some of them didn’t. This time, AdMob’s troubles are over. May you all go to sea and make a fortune!