Para analizar nuestros productos y proporcionar comentarios sobre ellos, únete al canal oficial de Ad Manager en Discord, en el servidor Google Advertising and Measurement Community.
Cómo solucionar problemas relacionados con las ofertas de Ad Manager
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Cuando se integra un socio de licitación que requiere su SDK, los siguientes síntomas indican una integración incorrecta:
El informe de Ad Manager muestra muchas menos solicitudes de anuncios a ese socio de lo que esperas.
Falta el parámetro a3p en cualquier solicitud posterior a la primera solicitud de anuncio.
Sigue esta lista de tareas para asegurarte de que tu configuración sea correcta:
En la IU de Ad Manager, haz lo siguiente:
Confirma que seguiste la guía de integración del socio específico para configurar la demanda de licitación externa.
Confirma que tienes una asignación de unidad de anuncios para cada formato de creatividad.
Por ejemplo, si configuras anuncios nativos y de banner, necesitas una asignación de unidades de anuncios para los anuncios nativos y otra para los anuncios de banner.
[null,null,["Última actualización: 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."]]