Troubleshoot AdMob bidding

AI-generated Key Takeaways

• Fewer ad requests or a missing a3p parameter after the first request can indicate improper bidding partner SDK integration.

• A correct setup involves confirming partner integration in AdMob UI, verifying ad unit mappings, and updating app code with matching app IDs and ad unit IDs.

• It's crucial to initialize the Google Mobile Ads SDK, ensure the adapter status is READY, and use the latest adapter and SDK versions for proper integration.

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.