When integrating a bidding partner that requires their SDK, the following symptoms indicate an improper integration: - The [Ad Manager report](https://support.google.com/admanager/answer/2671992) shows significantly fewer ad requests to that partner than you expect. - The `a3p` parameter in any request after the first ad request is missing. > [!IMPORTANT] > **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](https://developers.google.com/ad-manager/mobile-ads-sdk/android/choose-networks.md.txt) 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](https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start#import_the_mobile_ads_sdk) 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 Google Mobile Ads SDK (Legacy)](https://developers.google.com/ad-manager/mobile-ads-sdk/android/mediation#initialize) and verify that the adapter status is `READY` before loading an ad. - Use the latest version of the adapter and SDK binaries for the ad source you're trying to integrate with.