No fill for meta mediation.

[Dzmitry]

Hi, I integrated meta sdk into my app, followed all steps listed here 

https://developers.google.com/admob/android/mediation/meta

But all I am getting right now is "No fill".

The integration is so complicated, that I've probably missed something.

Please help.

[Mobile Ads SDK Forum Advisor]

Hi,

No Fill error means an ad serving issue which indicates there are no ads available at request time. Kindly share below details via reply to author option to verify your account and run our Google sample project.

    •    app ID
    •    ad unit ID
    •    Platform being used
    •    Mobile Ads SDK Version
    •    Meta Audience Network Version
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02s09zC:ref" (ADR-00228319)

Thanks,
 

Mobile Ads SDK Team

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Upon reviewing your AdMob account with the provided information, I found the below issues which must be fixed.

It was discovered that your app status is in "Requires review" state. This indicates that your app has not yet been subject to the review process. To have it reviewed, it is necessary to establish a link between your app and the supported app store. You can link a supported store to your app within the All Apps or App settings pages and subsequently submit it for review. For more information, you can visit  Requires review. 

The app-ads.txt file has not been configured yet. Although the app-ads.txt file is not absolutely necessary for ads to be displayed, it's still recommended to Set up an app-ads.txt file for your app. You need to make sure that your apps are crawlable by AdMob in order to properly set up your app-ads.txt. Kindly refer to crawled. 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.

I presumed that you have adhered to the AdMob Policies and restrictions and Implementation Guidelines to avoid any issues.

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

[권나영]

Hello,

I wanted to clarify whether this issue is related to Meta's mediation, as ads are currently being displayed correctly through other networks like IronSource, Liftoff, and AdMob.

You mentioned setting up the app-ads.txt file for my app. I have already configured the marketing URL, and the app-ads.txt file is accessible from that URL. (I just double-checked, and the file is visible without any issues, including Meta’s network ID.) 

I had previously reached out regarding this matter (https://groups.google.com/g/google-admob-ads-sdk/c/F2YFRemymvg), but it has now been three weeks, and AdMob still hasn’t crawled the app-ads.txt file.

Also you mentioned that "if your site doesn't make many ad requests, it may take up to a month." Could you please clarify what qualifies as “many” ad requests? Currently, my app is making 13.7k ad requests. Is this number not sufficient for the file to be crawled?

Or is this simply a matter of needing to wait a bit longer?

Thank you for your assistance.

2024년 8월 16일 금요일 오후 4시 15분 52초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:

[권나영]

Hello,

I wanted to clarify whether this issue is related to Meta's mediation, as ads are currently being displayed correctly through other networks like IronSource, Liftoff, and AdMob.

You mentioned setting up the app-ads.txt file for my app. I have already configured the marketing URL, and the app-ads.txt file is accessible from that URL. (I just double-checked, and the file is visible without any issues, including Meta’s network ID.) 

I had previously reached out regarding this matter (https://groups.google.com/g/google-admob-ads-sdk/c/F2YFRemymvg), but it has now been a month, and AdMob still hasn’t crawled the app-ads.txt file.

Also you mentioned that "if your site doesn't make many ad requests, it may take up to a month." Could you please clarify what qualifies as “many” ad requests? Currently, my app is making 13.7k ad requests. Is this number not sufficient for the file to be crawled?

Or is this simply a matter of needing to wait a bit longer?

Thank you for your assistance.

2024년 8월 16일 금요일 오후 4시 15분 52초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:

Hi,

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

You need to make sure that your apps are crawlable by AdMob in order to properly set up your app-ads.txt. Kindly refer to crawled. It may take a few days for app-ads.txt changes to be reflected in AdMob. 

Could you confirm whether you have followed all the steps to Integrate Meta Audience Network with bidding? 

I have executed our Google Sample project with the provided information and am able to load the ads successfully. Could you confirm whether the mentioned issue is reproducible in our Google Sample project by integrating the Meta Audience Network? If yes, kindly share the below information privately so we can review it and try to replicate the problem. After doing so, we will be better equipped to offer a solution. 

• Sample project reproducing the issue
• Screenshots or video recordings of the issue

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files via reply to author option or by performing the following steps:

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002s09zCQAQ&entry.80707362=00228319

2. Fill out all fields and attach your file(s).

3. Please reply on this thread when you have uploaded your file(s). Please do not share this link.

[권나영]

Hi,

Thank you for the update.

I have few questions.

1. Just to clarify, you are using Meta through AdMob mediation. right?

2. And is the Meta ad showing up in Ad Inspector?

3. If that's correct, could you please let me know which version of the Meta SDK you are using?

Thank you.

2024년 8월 19일 월요일 오후 12시 57분 20초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

In response to your inquiries, please adhere to the following responses:

1. Just to clarify, you are using Meta through AdMob mediation. Right?

Response: Yes, we are indeed using Meta through AdMob mediation.

2. And is the Meta ad showing up in Ad Inspector?

Response: Yes, the Meta ad is visible in the Ad Inspector. 

3. If that's correct, could you please let me know which version of the Meta SDK you are using?

Response: We utilized the Meta Audience Network Version 6.15.0.0 and the Mobile Ads SDK Version 11.5.0, as you have specified.

[Kwong]

I'm having the same issue as well in Unity. The review was done and the app status is in "Waiting for bid request" in Meta business website now, but it's still returning No Fill when "Single ad source test" is set to "Meta Audience Network (Bidding)" in Ad Inspector.  Testing Mode is enabled in Meta website adn Admob console and test devices were added accordingly too. Tested with installed Facebook app and logged in the Facebook account which is also under the Facebook developer account as tester role. Tried Applovin bidding and regular admob ads, and they worked fine without issue. It's easy to blame Meta seeing only Meta mediation does not work, but we also suspect the mediation adapter might be missing passing some important data, such as test mode value or test device ID to Meta SDK and Meta just simply returns no ads due to it's not a test ad request. For more info, here's the ReponseInfo:

ResponseInfo: {

  "Response ID": "xxxxxxxxxx",

  "Mediation Adapter Class Name": "",

  "Adapter Responses": [

    {

      "Adapter": "com.google.ads.mediation.facebook.FacebookMediationAdapter",

      "Latency": 610,

      "Ad Source Name": "Meta Audience Network (bidding)",

      "Ad Source ID": "xxxxxxxxxx",

      "Ad Source Instance Name": "Meta Audience Network (bidding) (Rewarded)",

      "Ad Source Instance ID": "xxxxxxxxxx",

      "Credentials": {

        "pubid": "xxxxxxxxxx",

        "placement_id": "xxxxxxxxxx"

      },

      "Ad Error": {

        "Code": 3,

        "Message": "No fill.",

        "Domain": "com.google.android.gms.ads",

        "Cause": {

          "Code": 1001,

          "Message": "No fill",

          "Domain": "com.facebook.ads",

          "Cause": "null"

        }

      }

    }

  ],

I replaced confidential credentials with "xxxxxxxxxx". Please ignore them.

This is tested using the samples in https://github.com/googleads/googleads-mobile-unity and configured using our own ads unit IDs. More info on versions:

- Google Mobile Ads Unity Plugin v9.2.0

- com.google.ads.mediation:facebook:6.17.0.0 (Android package)

- com.google.ads.mediation:applovin:12.6.1.0  (Android package)

- Unity 2022.3.39f1

[Mobile Ads SDK Forum Advisor]

Hi Kwong,

Thank you for contacting the Mobile Ads SDK Support team.

The “no fill” error means that the ad request was successful, but no ad was returned due to lack of ad inventory.

When testing, ensure that you have the Facebook app installed on the test device and be logged in with a valid Facebook login. See Meta's documentation for more details. Without this, it is expected that Facebook might not bid (though they still might get bid requests).

Could you confirm whether you have followed all the steps to Integrate Meta Audience Network with bidding?

Kindly provide the below information via the reply to author option, so that we will review your account and let you know why ads aren’t showing.

• app ID
• ad unit ID

Could you kindly share the export request and response file generated from the Ad Inspector to us for further investigation. For detailed info refer to this AdInspector document.

[Kwong]

I have replied using the "Reply to Author", but the message does not show either here or email. Wanna check if you have received the message. Let me know if you need more info.