Best Practices for Using Banner Ads in RecyclerView

[Muhammed]

Hi everyone,

I’m working on implementing multiple banner ads inside a RecyclerView in my Android app using AdMob. However, I have concerns about optimizing ad requests and impressions.

Currently, if I load all ads when initializing the list, I end up making too many ad requests (e.g., 100+ requests for a long list), which could negatively affect my CTR and fill rate. On the other hand, if I delay ad loading, I might miss impressions.

Questions:

1. What is the best way to handle banner ads in RecyclerView efficiently?
2. Should I load only visible ads using onViewAttachedToWindow()?
3. Is there an official Google-recommended approach for handling this?

Any insights or best practices would be greatly appreciated. Thanks in advance!

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Please refer to the BannerRecyclerViewExample Google sample application for implementing Banner Ads in a RecyclerView. Use onViewAttachedToWindow() to load ads only when necessary. This helps reduce unnecessary ad requests, which can save resources and improve fill rates and CTR.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-02-26 02:19:07Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH3vE:ref" (ADR-00289808)

[Muhammed]

Hello, this is quite an old repo. Since it preloads ads, they cannot be fully displayed, resulting in a low load/view ratio.
Additionally, if there are more than 1,000 items and loading is done with lazy load or endless scroll, this method will not work.

26 Şubat 2025 Çarşamba tarihinde saat 05:20:02 UTC+3 itibarıyla Mobile Ads SDK Forum Advisor şunları yazdı:

[Mobile Ads SDK Forum Advisor]

Hi Muhammed,

This can be accomplished in the following ways:

1.Load Ads only when visible using onViewAttachedToWindow() and onViewDetachedFromWindow() to load and release ads dynamically.
2.User a viewType for Ads: Instead of treating ads like normal list items, create a separate viewType for ads and insert them at regular intervals (eg every 10 items)
3.Recycle and reuse AdViews: Instead of creating new ad views every time, reuse existing AdView instances in the RecyclerView.ViewHolder.
4.Pagination: If you have more than 1000 items for loading you will use pagination for that. This approach lets your app use both network bandwidth and system resources more efficiently.
5.Load specific ad container: Take the visible count of the items present on the screen using layoutManager.findLastVisibleItemPosition() - layoutManager.findFirstVisibleItemPosition() and load ad container present between those items runtime.
AdMob provides Implementation guidance
Recommended banner implementations, Discouraged banner implementations and Banner ad guidance
 

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-03-07 00:42:41Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH3vE:ref" (ADR-00289808)

[Mobile Ads SDK Forum Advisor]

Hi,

Kindly note that if the app status is in "Getting ready" state. This indicates that your app is under review. This usually takes a couple of days, but in some cases it may require more time to evaluate your app. 

Note: If you recently signed up for AdMob, your apps will remain in the "Getting Ready" status until your account is verified. Enter your payment details to have your account verified. 

For more information, you can visit  Getting Ready. 

The app-ads.txt file has not been configured yet. Kindly note that It may take a few days for app-ads.txt changes to be reflected in AdMob. If your site doesn't make many ad requests it may take up to a month. Please use the following help center article to Set up an app-ads.txt file for your app and Ensure your app-ads.txt files can be crawled.

I hope this helps! Let me know if you have any other questions.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-03-07 09:09:06Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH3vE:ref" (ADR-00289808)

[Gallet Nyambo]

Show me how to do it

--

---
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 visit https://groups.google.com/d/msgid/google-admob-ads-sdk/789Cu000000000000000000000000000000000000000000000SSQ9Z500-BbVXJ24QYGAEV0wNI0oTg%40sfdc.net.

[Zubaida Jannat]

Subject: Delay in AdMob App Verification – More than 3 Weeks

Dear AdMob Support Team,

I hope you are doing well. I have submitted my app for AdMob verification, but it has been more than three weeks, and my app is still not verified. Due to this delay, I am unable to monetize my app.

Here are the details of my AdMob account and app:
App Name: [ super fast browser,  wild animal quiz]

App Package Name  [com.zubaidajannat.wildanimalquiz2]
[com.securesuperfast27]
Submission Date: [more than 2 weeks]

Issue: My app has been under review for more than two weeks, and I have not received any update.

I do not have a sample project, but I am happy to provide any additional details if needed. Please let me know the current status of my app verification and if there is anything I need to do from my end.

Looking forward to your response.

Best regards,
[Tahira Naz]
[jannatzu...@gmail.com]

[Mobile Ads SDK Forum Advisor]

Hi,

To check the issues in AdMob follow the below steps:

• Open the AdMob 
• On the left side panel click on policy center

In this way you are able to check and please be informed that our support channel can only best assist you with regards to Mobile Ads SDK implementation and technical issues. As your concern is more related to the Account side issues rather than Google Mobile Ads SDK implementation. So I would recommend reaching out to the Product support team as they are better equipped to address your concern.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-03-10 13:48:36Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH3vE:ref" (ADR-00289808)