Troubleshoot AdMob bidding

AI-generated Key Takeaways

outlined_flag

• Significantly fewer ad requests to a bidding partner than expected and a missing a3p parameter in subsequent requests are symptoms of improper integration.

• Ensure you have followed the specific partner's integration guide and have an ad unit mapping for each creative format in the AdMob UI.

• Confirm your AndroidManifest.xml file has the correct app ID, your ad unit IDs match those in the AdMob UI, and the Google Mobile Ads SDK is initialized with a READY adapter status.

• Use the latest versions of the adapter and SDK binaries for the ad source you are integrating with.

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.

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.