Issue Integrating Meta Adapter

[Jake van der Vliet]

Hello, I have followed this page (https://developers.google.com/admob/ios/mediation/meta) to integrate the meta adapter, but it doesn't appear at all when iterating "adapterStatusesByClassName", and doesn't show up in the ad inspector either. 

I am not sure what I am missing here for it to not appear at all. The steps I've taken are:
 - setup the meta placement

 - setup admob ad units and meta mapping

 - added pod 'GoogleMobileAdsMediationFacebook' and re-run pod install

 - updated the library and runpath search paths

 - set the meta AdvertiserTrackingEnabled flag

What's strange to me is that the adapter doesn't seem to appear at all, no logging, or errors at all to indicate the admob has been able to detect it. 

Any help here would be greatly appreciated.

- Jake

[Mobile Ads SDK Forum Advisor]

Hi Jake,

Thank you for contacting the Mobile Ads SDK support team.

It seems like you've already followed the necessary steps to integrate the Meta adapter for AdMob mediation. The issue might be related to integration. Could you please share your sample project along with the app ID and ad unit ID with us.

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. Kindly follow using the steps below:

1. Navigate to https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=IMA+SDK&entry.460850823=5004Q00002vGwTDQA0&entry.80707362=00284849

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

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

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

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

 

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

I'm deleting the previous thread from the forum as it consists of PII information.

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).

I checked the sample project with the provided IDs and am able to reproduce the issue when a single ad source test of the ad inspector is enabled for Meta Audience Network (Bidding).

As per our observations ads are not returning from third party resources (Meta Audience Network).

This happens due to below reasons:

• No ad returned: The ad sources may have decided to not bid for the ad request or they may not be eligible to bid for it. There are several possible reasons for this issue. Here are some examples:
  • The ad source may only bid under certain conditions, such as specific geographic areas. 
  • The ad source may not have an ad for the bid request. 
  • There was an unexpected system error or timeout on the ad source’s end.

Kindly refer to your third-party ad source to understand why the ad source may not be bidding. 

Also refer to this link for more information related to troubleshooting the bidding issue.

Please reach out to us, if you need any further assistance.

Find below your previous response with redacted information.

I actually managed to get the meta adapter showing in the list (I had missed adding it to the bidding sources in the mediation group. The issue I am running into now is that meta seems like it's not bidding at all. When testing with "Single ad source test" in the ad inspector I get "No ad to show". Is there anything logs or anything on googles side of things that would help me determine why that is? There really isn't much to go off of on my side.

Sending the entire project I don't think is possible, it's a production project that would be too big to share. I can send the relevant code where we interact with GAD.

App ID: ca-app-pub-22xxxxxxxx8~23xxxxxx3

Ad Unit: ca-app-pub-225xxxxxx568/828xxxxxx5 

[Jake van der Vliet]

Thank you, we'll contact Meta to try and resolve this.