Troubleshoot Ad Manager bidding

AI-generated Key Takeaways

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

• Ensure your Ad Manager UI is configured correctly, including following the partner's integration guide and having ad unit mappings for each creative format.

• Verify your app code has the correct app ID in AndroidManifest.xml, matching ad unit IDs, a ready Mobile Ads SDK, and the latest adapter and SDK versions.

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

• The Ad Manager 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 Ad Manager 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. For example, if you're setting up both native and banner, you need an ad unit mapping for native and another for banner.

• 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 Ad Manager 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.