|
||||||
Hi Oblica,
Thank you for reaching out to us.
Some ad serving limit are cause by invalid traffic concerns in your AdMob account. To avoid this kind of policy error, we always recommend to use our ad unit ids, when testing your application and enable the test device so you can avoid being tag as invalid traffic.
Regards,
|
||||||
Hi Oblica,
I understand that there is an urgency in your concern. However, the product support team is the appropriate team who can help you around as this is more of an ad serving issue. Kindly note that the SDK just requests an ad to the ad server (E.g: AdMob), and I'm afraid that it doesn't have any control on fill rate / match rate and policy error of your app. The product support team is handling this and it is out of our scope. To answer your questions clearly, we would recommend raising this to the Product Support team instead. We hope that you get a positive response from them the soonest time possible.
Regards,
Hi Oblica,
I'm glad to know that you're able to reach out to the product support team regarding the ad serving issue. We hope that you get a positive response from them the soonest time possible. If you have any other concerns related to the implementation of Google Mobile Ads SDK, kindly provide us the details. We'll be happy to assist you.