Troubleshoot AdMob bidding

AI-generated Key Takeaways

• Low ad requests in the Ads Activity report and a missing a3p parameter after the first request signal improper SDK integration for bidding partners.

• Ensure proper integration by verifying ad unit mappings, updating the AndroidManifest.xml file, matching ad unit IDs, initializing the Google Mobile Ads SDK, and using the latest adapter and SDK versions.

Select platform: Android iOS Unity

When integrating a bidding partner that requires their SDK, the following symptoms indicate an improper integration:

• The Ads Activity report shows significantly fewer ad requests to that partner than you expect.
• The a3p parameter in any request after the first ad request is missing.

Key Point: The first ad request may contain the a3p parameter even if you did not configure bidding.

Follow this checklist to make sure your setup is correct:

• In the AdMob UI:

  • Confirm that you have followed the specific partner's integration guide to configure third-party bidding demand.

  • Confirm that you have an ad unit mapping for each creative format.

• In your app code:

  • Update your AndroidManifest.xml file with the same app ID that your ad unit mapping targets.

  • Make sure your ad unit IDs match those in the AdMob UI as they must match exactly.

  • Initialize the Google Mobile Ads SDK and verify that the adapter status is READY prior to loading an ad.

  • Use the latest version of the adapter and SDK binaries for the ad source you're trying to integrate with.