Receive Log message tells "media views slots that have a width or height smaller than 120x120 will be demonetized in the future"

[Yang Jiao]

Hi There

We had something related to native ads size to consult. There are Log message had been received : <Google: HTML> Full screen native media view size has been detected to be 144x81. This size seems to be too small and might indicate a problem with your SDk implementation. please make sure the full screen native media view has sufficiently large area Received Log message: <Google: HTML> Partial screen native media view size seems to be too small, and might indica e a problem with your SDk implementation. Note that media views slots that have a width or height smaller than 120x120 will be demonetized in the future. please make sure the full screen native media view has sufficiently Large area

May we know that for which format, 120x120 will be deprecated? will this influence all our native ads? What is categorized as full screen native?

Thanks for help

[Mobile Ads SDK Forum Advisor]

Hello Yang,

Thank you for reaching out to us.

Can you please provide us additional information on this before we can provide proper context with regard to your question? Also, what platform in our Google Mobile Ads SDK are you using that returned you this log message?

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2R93l8:ref

[Alexander VI]

Hi.

We have the same message:

"Partial screen native media view size seems to be too small, and might indicate a problem with your SDK implementation. Note that media views slots that have a width or height smaller than 120x120 will be demonetized in the future. Please make sure the full screen native media view has sufficiently large area."

This is despite the fact that the Media type of the Ad Unit configured to return only "Image" not a "Video".

Our application is a music player, we cannot use video ads, as users always listen to music in the application.

The image asset is displayed using a MediaView as described in Native advanced Guide.

Attempts not to use the MediaView, for example to use the standard ImageView instead, result in the following message:

"Please note that policies require the use of MediaView at all times for main image assets. Non-compliant implementations may not function properly and may incur warnings or other enforcement actions from the Google Policy team."

So please fix this:

Or remove the message with "media views smaller than 120x120 will be demonetized"

Or remove the message with "policies require the use of MediaView at all times for main image assets" and allow us to use ImageView instead of MediaView.

Or explain what to do (to use) to display main Image Asset in area smaller than 120x120.

Otherwise, it turns out that we are dealing with an absurd situation with two conflicting requirements.

понедельник, 15 ноября 2021 г. в 12:28:57 UTC+2, mobileadssdk:

[Mobile Ads SDK Forum Advisor]

Hi Alexander,

Thank you for reaching out to us and providing more information with regard to this. But for us to further investigate this, we would need a sample app where this is happening and steps to replicate it. We would like to ask also if this is reproducible in our Sample App Android or Sample App iOS? You can send it via Reply privately to author option or send it directly to mobileads...@gmail.com. Kindly inform us on this thread if you sent it directly to the email provided.

[Alexander VI]

Hi.

You can simply take the "AdMob Native Advanced Example" project from "Sample Android Apps" and change the MediaView height to 110dp in the "ad_unified.xml" file.

For me this simple app always returns an App Install Ad without video.

It might be something different for you, but you will see this "...smaller than 120x120 will be demonetized...'' message in the log, even for non-video ads.

[يوميات ام عمر سهله وبسيطه‎]

انا لم افهم شىء من هذا ممكن توضيح 

--

---
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/d82409c3-69a3-4d5a-8527-bb5dcd5a764dn%40googlegroups.com.

[Mobile Ads SDK Forum Advisor]

Hi Alexander,

Thank you for your response.

I've tried to use our AdMob Native Advanced Example, and change the height of the mediaView in the ad_unified.xml file and tried to build it in an emulator. But I wasn't able to get the message you mentioned. Can you confirm if you've tried different ways to get the message?

[Alexander VI]

Hi.

It might be because you are expecting an error or warning message, no, this is a normal debug message.

Here's a screenshot:

[Mobile Ads SDK Forum Advisor]

Hi Alexander,

Thank you for your response.

I've it again in our sample app, but still unable to get the same logs as the screenshot provided. Can you confirm if this is happening to a specific device? Can you also provide us with what device you have tested this on?

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2TlrMM:ref

[Alexander VI]

Hi.
This is happening to all Android emulators and all our physical devices (Samsung Galaxy s4, s5, s20) , API levels form 19 to 31.
This is probably due to geolocation - a server that receives ad requests. Some of your servers may have outdated software.
Try using Israel proxy. (I'm from Israel)

[Mobile Ads SDK Forum Advisor]

Hi Alexander,

Thank you for your response.

Have you tried using another proxy or setting the geolocation to another country while testing it? Kindly make sure that if you are testing your ad unit id, kindly enable the device you're using as a test device or use our ad unit ids to avoid any invalid traffic.

[Alexander]

Hi.

I used a US proxy and still get these messages in the log. It means that the case is not related to the client's IP address.

I have no more guesses why you don't see them, but we do.

[Mobile Ads SDK Forum Advisor]

Hi Alexander,

Thank you for your response.

I was able to get the same log message when checking our sample app. With that, let me bring this to the rest of the team to ask additional context to the message that is being returned. Rest assured that one of our team will reach out to you.

[Mobile Ads SDK Forum Advisor]

Hello Alexander,

Thanks for reaching out to us.

We are currently looking into the issue and will get back to you shortly.

In the meantime, please do not hesitate to let us know if you have any questions.


Regards,
Joshua

ref:_00D1U1174p._5004Q2TlrMM:ref