Test Ads have stopped receiving after Google imposed ad serving limit

[Oblica Studio]

Due to reasons which I dont know, an Ad serving limit has been imposed on my AdMob account. I would like to know if this impact test ads as well because since this limit has been imposed, I am not getting test ads as well.

When I logcat my game and saw the log entries when Ads requests were sent, I saw - 

Ad failed to load : 3.

I have already successfully implemented live and test ads. My game is live on play store. Issues have started occurring after Google has imposed this limit. As a matter of fact just before the day ads thing was working fine. I have already reinstalled the SDK. I have also tried both approaches for test ads, adding test device on AdMob and programmatically. But nothing is working.

Any help is really appriciated.

[Mobile Ads SDK Forum Advisor]

Hi Oblica,

Thank you for reaching out to us with your concern. There can be many reasons for why an ad limit could be placed on your account. We suggest reading this article as it talks more about this. Also if this is a new app or you are testing ads with real Ids this can also trigger this. Which is why we always suggest to use the Test Ids. As for impact on test ads? It should not, you should be able to test still with our Ids. What we would also say is to check your account and make sure there are no violations.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2QFI7R:ref

[Oblica Studio]

Thanks for your reply. Unfortunately issue still persists and I don't see any exceptions in the Logcat entries (e.g. some kind of Java exceptions). It would be really helpful if you can tell me some of the reasons for this message, which I am seeing in Logcat output -  Ad failed to load : 3

Also when I send Ad requests it uses this test device ID - 73DF96442EF35525D9******************. While the test device which is registered using Google Advertising ID is completely different which is like 5b5bb915-e8c2-4******-*******. Why this is happening. I don't know the internal working of Mobile Ads SDK for Unity. So any help could point me towards resolving the issue.

[Mobile Ads SDK Forum Advisor]

Hi Oblica,

Thank you for responding to us. This is the first time we have heard that the device ID has been changed. There is nothing in the SDK that should be doing this. These numbers are coming from the device themselves and the SDK is just pulling that off your device. It could be possible that something within Unity is doing something that could change the number.

[Oblica Studio]

Ohh, does that mean that device ID in the Logcat entries (RequestConfiguration.Builder().setTestDeviceIds(Arrays.asList("")) and advertising ID for the test device must be same? If this is the case then it might be the reason for AdMob imposing limit on my account. I think somehow wrong device ID has been passed to Google (as it was not the advertising ID) and live ads might be served on my supposedly testing device. This was really unfortunately. Do you think this could be the case? Any suggestions how to avoid it in the future?

I have also tried removing my testing device from AdMob settings and passing test device ID which has been visible in Logcat, but I still did not get any ads.

Though when I have used AdMob sample IDs for Ad Units, I got sample ads served on my device. 

[Mobile Ads SDK Forum Advisor]

HI Oblica,

Thank you for reaching out to us again. Yes, you can read more about that here .  If these are not correct it is possible for ads to not be served to you. Also depending on the device this can also cause some of these limits or restrictions. in general though this should also be used automatically on newer devices, but again on some devices there might be restrictions.