hello and sorry for my bad english i'am native french speaker, i have a problem with admob, the OnAdPaid event is never called when i use real ads, but works perfectly with test ads.
I would like to give a reward to a player when the advert passes the reward mark i.e. 15-30 seconds.
I would have put a timer of 30 sec but the reward cap on adMob scale between 15 and 30 sec
Related
I use the strategy of preloading interstitials and rewarded videos at application startup, and this means that the user doesn't have to wait for an ad to load when it's time to display it. However, this also causes many ads that were requested to the admob network to not be displayed (because it was not the user's will or the time did not come), resulting in a low "show rate".
I've seen people saying that Admob can penalize profits if the "show rate" is low, but I haven't seen it anywhere making that clear
No you wont be penalized for low flow rate. However, i am on a 30 day suspension with admob for having to many ads displayed. It is called invalid clicking. So if you have your app show ads continuously without the user consent or point of interest you can get a suspension for displaying to many ads.
If they punished you for having to low of ads then no one would ever use them. Too many ads will get you in trouble.
We started to implement manual_screen_view for Android in June 2021. Faced problem about double screen_view events. It was fixed and released around the 12th of July. The last release before the problem appeared was on the 16th of August.
Everything was fine until the 26th of August. Since then our engagement times started to rise significantly and way out of proportion. As an example, we've highlighted a screen called "Logo intro". This is Splash screen and takes around 5 seconds before moving on to the next screen. Why is the average engagement time 1m 33s and then varies from 6mins to 40 sec.? There are way more examples, but this is a nice illustration.
graphic
table
We spoke with Firebase support and sent them screenshots from DebugView. Everything is perfectly fine with events and params. "Logo Intro" event is sent, then "Watch" event with previous "Logo Intro" and engagement_time_msec is around 6 second.
log intro event
watch event
watch event previous screen
watch event engagement_time_msec
We try to contact with Google Analytics support but haven't get any answer yet.
It is very important to understand this metric "Average engagement time". I have start to understand that metric when I was looking for how it is counted. In GA4 interface the note in question mark is very sad. This is from docs:
Average engagement time is the sum of user engagement durations divided by the number of active users. This metric shows the average engagement time per user. Google Analytics also shows the average engagement time per session, which is the sum of user engagement durations divided by the number of sessions. (https://support.google.com/analytics/answer/11109416)
In other words, the metric doesn't say what is average time spent in the mobile app for one session. It says how long on the average the users stays in your mobile app in the time period. E.g it says this "Between 1.9.2021 and 31.12.2021 users spend with your app 6 min on average. They dedicated 6mins of their life on average with your mobile app between the time period"
Rather than looking at implementation, which seems okay to me, ask some questions:
Have you released any new cool feature, that your users were looking forward to?
What about your average session duration, did it change overtime? If so, how and explore why.
How can i track timing of user watching my ads,
I want to give user point if user watch my ad for 5 seconds,
I don't use any code yet. How can i track the time user spend on my Ad
Any Hint Of Help will be useful for me.
I track the time, When user Click The Ad And when he closed the ad,
I'm about to integrate Admob in my app and I know this isn't a "coding error question" but I need some clarification on Admob from someone that use it.
I'd like to know how Impressions work and calculate it.
They just count 1 impression when the Ad appear? So If I keep that Ad only for some seconds or 60 seconds is the same thing? Sound strange to me.
More fair seem to me that Impressions are calculated with the seconds that they were shown...
Someone can explain to me How the thing work?
Impressions are a count of the number of times an ad is shown to a user, regardless of the duration it is displayed.
In my experience ad is rotated after some time - giving you more impressions
When talking about interstitial ad, an impression is counted every time the user see it regardless of the time it being presented
Banners are different, on the admob dashboard you can define refresh intervals when the default is 60 seconds, which mean that every 60 seconds a new banner will be called and when shown it is counted as impression
banner refresh
I've been uploading apps to the Google Play for a couple of months now. I've added Admob banner ads in all of my ~30apps. I'm getting my first payment this month, and I'll get a "big" one (+2000$) in January.
So, I've been doing my research. I've found AdMob closed LOTS of profitable accounts this year, so I'm a bit scared. I'm following their rules: no fraud clicks, banner always at the bottom of the app (shown in a fixed region, no matter if ad is served or not).
My only "but" is the refresh rate. Admob RECOMMENDS applying a 60 second refresh rate. I load an ad in every "onCreate" call of all my Activities. So, if an user enters my app in Activity A and Ad will be shown. If 5 seconds later, he navigates to Activity B, another Ad will be served.
I developed a while ago an static function, based on shared preferences, which doesn't allow the app to request an Ad faster than once in X seconds. That solves your problem! Nope.
Most of my aps have 4 or 5 Activities, one of them is shown 80-90% of time. I don't want the Ad to be server for an activity that is shown 2 or 3 seconds and then I wouldn't ask for another ad in the main activity because I still need to wait another 57 seconds.
I wonder how you guys solved this issue, I can't be the only want "fighting" against this.
The easiest solution (and a pretty good hueristic) is to just show ads in the activity that is shown 80-90% of the time. If the user is only in one of your activities for 2-3 seconds, chances are they aren't looking to click an ad in that activity. Do right by your users and don't annoy them with ads in the main menu or setting menu of your app.