Native Ads Advanced (Unified) with UnifiedNativeAd in production App not clickable

[Sharad Upadhyay]

We integrated Native Advance Ads in production App and started rolling it out. However, the roll out was halted as we discovered that Native Ads are not clickable. 

We have followed Native Ads Advanced to implement Native Ads. We got production native ad unit id through Admob account similar to banner and interstitial. App for which roll out was halted is Hindu Calendar.

During development, we were using test id with additional addTestDevice() for all development devices. During development also we were not able to click on Native Ads but we assumed it might be due to test ad or addTestDevice(). Native Ads load successfully and displayed (after putting individual Ad components) without any issues but clicking on them doesn't do anything. 

Any quick help would be appreciated.  Only way to move ahead it to build new release without Native Ads. But we have put so much efforts to insert native ads in recyclable view that we want to get some clarification on this issue. Have we missed handling of click event in the code?

[mobileadssdk-a...@google.com]

Hi Sharad,

Thank you for reaching out to us.

Please note that as long as you were able to populate and register the corresponding asset views as well as register the Native Ad object, then the Native Ads should display successfully and should be clickable, regardless if it is a test or a production ad.

That said, could you confirm if you encounter the same behavior if you test with our NativeAdvancedExample app?

For us to have a closer look on the behavior you've encountered on your end, could you provide to us privately (using Reply privately to author option) a copy of your project (or at least a test project) where issue is reproducible?

Regards,

Ivan Bautista

Mobile Ads SDK Team

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/c2c72056-3139-426f-a699-f83d4221244b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sharad Upadhyay]

Hi,

We followed official developer page on Native Ad which says "When you are done showing your native ad, you should destroy it so that the ad is properly garbage collected". Hence we called UnifiedNativeAd.destroy(). However  NativeAdvanceExample doesn't call destroy() on UnifiedNativeAd and it works. Hence we also commented calling destroy on UnifiedNativeAd and after that clicking on Native Ad started working. 

Please clarify so that either we create new release without calling destroy() or wait for some fix from Admob which would make Native Ads clickable without we going through new release.

Thanks, Sharad

[mobileadssdk-a...@google.com]

Hi Sharad,

Apologies if I missed out on testing your app. I downloaded it but I kept on seeing Banner Ads instead of Native Ads. Also, upon checking the device logs, I saw that a lot of Error Code 3 or No fill errors are being thrown which I assume corresponds to the failed attempts to load Native Ads in your app. I also tested your Native Ad Unit Id with our NativeAdvancedExample app and I also kept on getting Error Code 3 or No fill error which just means that there are no available ads at the moment. Thus, we tried loading test Native Ads instead, using our sample Native Ad Unit Id (ca-app-pub-3940256099942544/2247696110), but we can't reproduce the behavior you described. 

However, it seems that the Native Ads are now clickable on your end based from your recent response. That said, please note that there is no existing known issue that affects the clickability of the Native Ads so it should have worked as expected with the latest release (15.0.0 as of this writing). On the other hand, it is indeed recommended to destroy the ad once you are done showing and using it but you don't need to call the destroy() method for the Native Ad asset views to be clickable.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/c2c72056-3139-426f-a699-f83d4221244b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/42ff784f-994b-405e-9254-bc6ca7ffe263%40googlegroups.com.

[Sharad Upadhyay]

Hi Ivan,

Thanks again for your prompt response. 

You might have missed it but I mentioned it in "reply privately to author" message that we have set eCPM for Native Ad unit to $1000 (as app is live and we don't want those ads eating real estate in app). Hence if you use our native ad id either in our app or in your sample app you would only get Error code 3 (which is expected as who would bid $1000 for one click?). We also mix banner and Native Ads so you would see only banner as we have not set any eCPM for banner.

Also the probable bug is visible "if we call destroy". If we don't call destroy then issue is not visible. You please call destroy() in your sample ad and you would find that Native Ad becomes non-clickable after calling destroy. Hence in our opinion it is wrong to suggest developers calling destroy() on UnifiedNativeAd().

Hope I have made myself clear.

Thanks, Sharad

[Sharad Upadhyay]

Hi Ivan,

Also if we call destroy() on UnifiedNativeAd() which makes Native Ad non-clickable and later when Native Ad is clicked...

Logcat shows...

07-30 17:00:29.095 24530-24530/com.drikp.core W/Ads: Your account need to be whitelisted to use this feature. Contact your account manager for more information.

07-30 17:00:29.229 24530-24530/com.drikp.core W/Ads: #004 The webview is destroyed. Ignoring action.

However if destroy() is NOT called...Native ad is clickable and pops up Ad and Logcat shows...

07-30 17:20:27.069 28501-28501/com.drikp.core W/Ads: Your account need to be whitelisted to use this feature. Contact your account manager for more information.

07-30 17:20:27.195 28501-28501/com.drikp.core I/Ads: Ad clicked.

Not sure if it would be helpful to you to investigate further. But for us it opens another questions - whom should be called to whitelist this feature? If we still need to be whitelisted why our Admob account let us create production ID for Advance Native Ads.

Thanks, Sharad

[mobileadssdk-a...@google.com]

Hi Sharad,

Thank you for getting back to us with more details.

Apologies if I misunderstood your explanation about the destroy method. It is expected that any interactions with the Native Ad will not work if the Native Ad object has been destroyed. That said, please note that the destroy() method is only recommended to be called when you are done using the Native Ad. One scenario you could put this in is if the user is leaving the screen where the Native Ad is loaded, thus, you could probably call the destroy() method inside the onDestroy method. However, don't call the destroy() method if the user will still have a chance to interact with the Native Ad.

As for the warning message "Your account need to be whitelisted to use this feature. Contact your account manager for more information.", it's best to confirm further information regarding your whitelisting to your designated Account Manager who processed your whitelisted access to Native Advanced Ads. It is indeed a logical assumption that since you were able to create a production Native Advanced Ad Unit Id, then it is a confirmation that you are whitelisted for Native Advanced Ads. However, I still suggest that you double check with your designated Account Manager so that they could add more insights on this.

Regards,

Ivan Bautista

Mobile Ads SDK Team

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/42ff784f-994b-405e-9254-bc6ca7ffe263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/732699a3-7e3a-485e-8d78-f3e6eb5045de%40googlegroups.com.

[Peeyu Squad]

Complete tutorial to implement Google AdMob Native Ads Advanced Unified