Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Ad Manager resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat mengintegrasikan partner bidding yang memerlukan SDK mereka, gejala berikut menunjukkan integrasi yang tidak benar:
Laporan Ad Manager
menunjukkan permintaan iklan ke partner tersebut jauh lebih sedikit dari yang Anda harapkan.
Parameter a3p dalam permintaan apa pun setelah permintaan iklan pertama tidak ada.
Ikuti checklist ini untuk memastikan konfigurasi Anda sudah benar:
Di UI Ad Manager:
Konfirmasi bahwa Anda telah mengikuti
panduan integrasi
partner tertentu untuk mengonfigurasi permintaan bidding pihak ketiga.
Pastikan Anda memiliki pemetaan unit iklan untuk setiap format materi iklan.
Misalnya, jika Anda menyiapkan iklan native dan banner, Anda memerlukan pemetaan unit iklan untuk native dan satu lagi untuk banner.
[null,null,["Terakhir diperbarui pada 2025-08-27 UTC."],[[["\u003cp\u003eLow ad requests in Ad Manager reports and a missing \u003ccode\u003ea3p\u003c/code\u003e parameter after the first request signal improper SDK integration for bidding partners.\u003c/p\u003e\n"],["\u003cp\u003eEnsure proper Ad Manager configuration by following the partner's integration guide and setting up ad unit mappings for all creative formats.\u003c/p\u003e\n"],["\u003cp\u003eVerify your app code by updating the \u003ccode\u003eInfo.plist\u003c/code\u003e file, matching ad unit IDs, initializing the Mobile Ads SDK, and using the latest adapter and SDK versions.\u003c/p\u003e\n"]]],["Improper bidding partner SDK integration is indicated by fewer ad requests than expected or a missing `a3p` parameter after the initial request. To fix this, confirm the partner's integration guide was followed and that ad unit mappings exist for each creative format. In the app code, ensure the `Info.plist` app ID matches the ad unit mapping, ad unit IDs match exactly, the Google Mobile Ads SDK is initialized with a `READY` status, and the latest adapter/SDK versions are used.\n"],null,["# Troubleshoot Ad Manager bidding\n\nWhen integrating a bidding partner that requires their SDK, the following\nsymptoms indicate an improper integration:\n\n- The [Ad Manager report](//support.google.com/admanager/answer/2671992) shows significantly fewer ad requests to that partner than you expect.\n- The `a3p` parameter in any request after the first ad request is missing.\n\n| **Key Point:** The first ad request may contain the `a3p` parameter even if you did not configure bidding.\n\nFollow this checklist to make sure your setup is correct:\n\n- In the Ad Manager UI:\n\n - Confirm that you have followed the specific partner's\n [integration guide](/ad-manager/mobile-ads-sdk/ios/choose-networks)\n to configure third-party bidding demand.\n\n - Confirm that you have an ad unit mapping for each creative format.\n\n For example, if you're setting up both native and banner, you need an ad\n unit mapping for native and another for banner.\n\n- In your app code:\n\n - [Update your `Info.plist`\n file](/ad-manager/mobile-ads-sdk/ios/quick-start#update_your_infoplist) with the same app ID that your ad unit mapping targets.\n\n - Make sure your ad unit IDs match those in the\n Ad Manager UI as they must match exactly.\n\n - [Initialize the Google Mobile Ads\n SDK](/ad-manager/mobile-ads-sdk/ios/quick-start#initialize_the_mobile_ads_sdk)\n and verify that the adapter status is `READY` prior to loading an ad.\n\n - Use the latest version of the adapter and SDK binaries for the ad source\n you're trying to integrate with."]]
