Developer Console - Pre-Launch Report

[orangead...@gmail.com]

Hi,

For automated testing using the Pre-Launch Report on the Google Play Developer Console, do you actively filter out artificial impressions/clicks generated through this route?

As you can imagine, it isn't practical to run this test with ads disabled, and then re-upload an APK with ads enabled for distribution. Seeing as the Pre-Launch Report is a service provided by Google, it would make sense if these impressions/clicks are automatically filtered out.

Could you please confirm that this is the case?

Thanks!

[Joshua Lagonera (Mobile Ads SDK Team)]

Hi there,

Our team is not familiar with your inquiry as we mainly handle SDK issues. You can reach out to our support team about this for further assistance

However, you can use the test Ad Unit IDs located in our example projects while your app is in testing on the Google Play Developer Console. Once your app is ready to be published, you can use Firebase's Remote Config to replace the test Ad Unit ID with your live one.

Regards,

Joshua Lagonera

Mobile Ads SDK Team

[Fung LAM]

No, they didn't block/filter the AdRequest.

They disabled my account.

[Fung LAM]

That means we need to have one config for each release? 

I think there should be a better way for doing this.

[zarsky]

Yeah, just happened to me as well :(

I've found this here on ubuverse.com, you can use it to hide ads for those test devices or whatever - seems to be working, but use at your own risk.

private boolean isTestDevice() {
 return Boolean.valueOf(Settings.System.getString(getContentResolver(), "firebase.test.lab"));
}