Android Question [SOLVED] Ad Fraud?? I need an Advice

mcqueccu

Well-Known Member
Licensed User
Google keeps Rejecting my App anytime I implement FirebaseAdmob2 in my App. They claim I am committing Ad Fraud?

ABOUT MY APP
It's a simple app with Formulas to calculate Employee Social Security and Income tax.

1624829511286.png


POSITION OF ADS (3 Ads)
1. A banner Ads at the bottom of the Main Activity,
2. An interstitial Ads when the user hits the calculate button for 5 times, the 6th time shows an interstitial Ads
3. An interstitial Ad when User closed is True after which iad_closed event has Activity.finish to close the App

The app has been in the play store since 2019 with FirebaseAdmob which works fine.
I later switched to FirebaseAdmobplus which was also accepted in the play store, Until Support ended.
I then switched to FirebaseAdmob2 after it was released, When I implemented it, they accepted that update briefly and later removed the app after few days because of Ad Fraud.

I quickly removed the FirebaseAdmob2 from the App, cleaned the project, and uploaded an update without Ads and the App was reinstated into the Store (Version Code 8)
I Made another update - Made a change in calculating one particular Tax (Accepted to Playstore - Version code 9)

Yesterday, I reimplemented the FirebaseAdmob2. Consent manager tested OK, funding choices OK, App-Ads.txt OK , and USING THE SAME ADS POSITION, and the app was rejected again. Reason - Ad Fraud (Version code 10)

At this point, I feel there is something am not doing right.

Have anyone encountered this before? And how did you solve it?

1624828716866.png
 

JohnC

Expert
Licensed User
I think the important part of Google's response is "contains code to facilitate ad fraud". Meaning, google's code scanner is somehow thinking some of your code has the "ability" to do ad fraud even if it actually isn't.

For example, one of your methods displays an ad "after 6 calculations" - so maybe google thinks that because the ad doesn't appear every single time the calc button is pressed, then all of the sudden it does display an ad, google might think you're trying to trick the user to accidently clicking the ad because the user may be use to a particular tap sequence when using your app, and to suddenly display something new might get the user to click on the ad by mistake because they meant to click on something that the ad is now covering up, especially since interstitial ads cover most/all of the screen so any accidental click is an ad click.

You mention three different instances where you show ads:

POSITION OF ADS (3 Ads)
1. A banner Ads at the bottom of the Main Activity,
2. An interstitial Ads when the user hits the calculate button for 5 times, the 6th time shows an interstitial Ads
3. An interstitial Ad when User closed is True after which iad_closed event has Activity.finish to close the App

You may need to do a few trial and error runs to narrow down which of these three ad display methods are causing the rejection.

My guess is that method #2 is causing the rejection, so I would start with just including ad methods 1 and 3 in the app and see if it gets rejected. If it does, then just try method #1.

This might help narrow down which ad method google's scanner doesn't like.

P.S. From what I have read for some other apps, you are lucky that google didn't detect any actual ad fraud, otherwise your account could be closed permanently.
 
Last edited:
Upvote 0

asales

Well-Known Member
Licensed User
3. An interstitial Ad when User closed is True after which iad_closed event has Activity.finish to close the App
You need to check this too:
Do not place interstitial ads on app load and when exiting apps
 
Upvote 0

mcqueccu

Well-Known Member
Licensed User
You need to check this too:
Do not place interstitial ads on app load and when exiting apps

Seen. Am guilty of this as well.

My app is basically one Activity (Main) with Tabstrip to navigate to other layouts.

I will try AppOpenAds to see the result.
 
Last edited:
Upvote 0

kisoft

Well-Known Member
Licensed User
It seems to me that FirebaseAdmob2 is not a problem here ... The problem is on your side, or actually the way you try to display ads ...
 
Upvote 0

mcqueccu

Well-Known Member
Licensed User
It seems to me that FirebaseAdmob2 is not a problem here ... The problem is on your side, or actually the way you try to display ads ...

Yes, I agree. I think they just recently started being strict on this.

I released an app recently (on May 21) DVLA Questions, and its using firebaseAdmob2. Simillar Ads placement(banner at bottom, appopenads after answering 5 questions, an interstitial on closing the app) and it was also accepted and still in store.
 
Last edited:
Upvote 0

asales

Well-Known Member
Licensed User
I will try AppOpenAds to see the result.
Don't forget to check this link below, because it has some requirements like "the app open ad should not be placed on top of content that includes a banner ad"...
 
Last edited:
Upvote 0

mcqueccu

Well-Known Member
Licensed User
Don't forget to check this link below, because it has some requirements like "the app open ad should not be placed on top of content that includes a banner ad"...

Thank you all. I have learnt a lot from this thread. Obviously, I have implemented ads the wrong way over the years and they allowed it. Now they are hitting hard on me.
I will have to quickly update other apps to conform to these recommended implementation guidelines before they block my account.
 
Upvote 0
Top