|
||||||
|
||||||
Hello,
The confirmed click behavior is a good find, and could explain the drop. "Near 0", something like 0.0x% CTR still seems a bit low to me, but I would defer to product support there.
As for particular creatives showing ads in the non-safe area, creatives by default are limited to the safe area. However, advertisers can opt-out of having their creatives being limited to the safe area, to allow for a nicer full screen experience. Unfortunately, some creatives (and usually it's the 3rd party creatives coming from an Ad exchange) opt out of that safe area limitation, but then their html doesn't take that unsafe area into account, leading to screenshots you see on https://github.com/FirebaseExtended/flutterfire/issues/3090, even when not using the Flutter plugin.
I can't confirm whether the interstitial behavior of the Firebase plugin further contributes to this problem as well. I suggest refiling the issue at https://github.com/googleads/googleads-mobile-flutter for confirmation. I did however try our test interstitial on a vanilla iOS application running iPhone X, and saw the ad being limited to safe area as expected (screenshot attached). So if that same test ad consistently has that close button behavior on Flutter integrations (as reported in https://github.com/FirebaseExtended/flutterfire/issues/3090), perhaps the Flutter plugin does have a bug.
Thanks,
Eric, Mobile Ads SDK Tam
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/53deb6bc-e513-45d0-bac0-ed419af622bcn%40googlegroups.com.
Hello Martin,
Thank you for your response.
I'm sorry to hear that you're having troubles in contacting our Product Support Team. But, please do 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/ CTR of your app. That said, we would recommend raising this again to our Product Support team instead. The product specialist there should be able to assist you further on this, and wait for them to respond to you. We hope that you get a positive response from them the soonest time possible.
Regards,
|
||||||
|
||||||
Hello Ettore,
Thank you for reaching out to us.
Can you confirm if you already reach out to the Product Support Team? If not yet, I would recommend reaching out to them as this is more related to the clicks that are being reported into your account. 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/ CTR of your app. We hope that you get a positive response from them the soonest time possible.
Regards,
|
||||||
Hi Peter,
Thank you for reaching out to us.
Can you confirm if you already reach out to the Product Support Team? If not yet, I would recommend reaching out to us, as they have more tools on checking the recording of clicks. We hope that you get a positive response from them the soonest time possible.
Hi Nadhir,
Thank you for your response.
Can you confirm if you already reach out to the Product Support Team? If not yet, I would recommend reaching out to them as they can help you with regard to your previous concern. Then for your message for native ads, can you confirm what you mean by this?
Hi Peter,
Thank you for your response.
Can you confirm if you already reach out to the Product Support Team? If not yet, I would recommend reaching out to them as they can help you with regard to your previous concern.
Regards,
Hello Everyone,
Thank you for getting back to us.
As previously mentioned by my colleague(Princess), we suggest that you reach out to the Product Support Team for your click-related concerns.
We hope that you receive their response the soonest time possible.
Regards,
|
||||||
Hi Peter,
Thank you for your response.
As one of our team members mentioned previously, this issue looks to be unrelated to SDK implementation, and must be diagnosed by product support at https://support.google.com/admob/community.
Regards,
|
||||||