Error message: "video-enabled native ad, but did not register"

[Sean]

Hello,

Has someone experienced this error message before:

You have received a video-enabled native ad, but did not register ' +

‘a media view. In order to improve user experience and to maximize ’ +

‘revenue, we recommend rendering a media view of size 300x150 or ’ +

’larger. See https://goo.gl/13Cx1M for more details.

Native ad view size has been detected to be 0x0. This size seems to be too small, and might indicate a problem with your SDK implementation. Note that ad slots that have a width or height smaller than 32 will be demonetized in the future. Please make sure the ad view has sufficiently large area.

Here is our situation:  We have a working iOS native template implementation with a non-zero (full-screen width, 16:11) size MediaView with video that is throwing this error in the console. We would either like to know if the error is incorrect and can be ignored or if it cannot be ignored, how do we resolve the error to not impact our advertising. The video works properly, renders correctly, and clicks work correctly. Everything is working correctly except for the error in the console.  The sizing message seems to be a red herring and may flow from the original registration issue.  We know the ad is sized correctly as we can see it.

Our developers also discovered another detail about this issue today.  When downloading Google’s sample code for custom format native video, it exhibits the same error we’re seeing (screenshot attached).  So it appears to be a Google issue and not our implementation.  The source is here: https://github.com/googleads/googleads-mobile-ios-examples/releases  [googleads_mobile_ios_swift_admanager_custom_rendering_example]

And a link to the specific zip file is here: https://github.com/googleads/googleads-mobile-ios-examples/releases/download/7.22/googleads_mobile_ios_swift_admanager_custom_rendering_example.zip

And one last piece for additional context:   We’re using a Custom Format. (https://developers.google.com/ad-manager/mobile-ads-sdk/ios/native/custom-formats)

We’re adding the mediaView to our hierarchy, nearly identically to the sample code here: https://developers.google.com/ad-manager/mobile-ads-sdk/ios/native/custom-formats#native_video_for_custom_native_ad_formats

Given the documentation here https://developers.google.com/ad-manager/mobile-ads-sdk/ios/native/custom-formats#displaying_custom_native_ad_formats that says "Because there is no dedicated ad view class, you do not need to register any of the views you use to display the ad's assets.”, I’m wondering if this error is legitimate. I’m not sure I know of a way to register the view when using Custom Formats.

Video looks great. As a test, I delayed our call to recordImpression until the ad was loaded and playing and I see the same error in the console.

Please let us know if you have experienced this error and how you resolved it!

Thank you,

Sean

[Mobile Ads SDK Forum Advisor Prod]

Hi Sean,

Thank you for bringing this issue to our attention. While I have not seen all of those messages, especially relating the demonetization. I have seen the one about the ad showing as 0x0. With that in mind, I have given the information and screenshot that you provided to my team to look into what is causing this. As this appears to be more of an issue with our system just not recognizing the dimensions of the ad. But also appears to be more of a display issue than a real issue. As you have stated, the ads appear to be displaying correctly and everything else appears to be ok.

But as also the other part of this dealing with policy and the effects this can have on your account, revenue and things related to that. I am unable to answer as we do not have access to those types of things. That is beyond what we do here. We are more here to help you with the technical aspect which we will. For the policy part, I would suggest contacting our Product Support Team, as they handle those types of issues.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2CSZwU:ref

[Sean O'Keeffe]

Hi William

Thank you for your response.  Please do let us know if you find out what is causing this.  I will contact your product support team as well to understand any possible policy or revenue effects.

Thanks,

Sean O'Keeffe

Ad Operations Manager

sean.o...@teamsnap.com

website | facebook | twitter | youtube

[Mobile Ads SDK Forum Advisor]

Hi Sean,

I just want to circle back on this. If you still encounter the issue, please let us know.

Regards,

Teejay Wennie Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2CSZwU:ref