Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Las siguientes funciones globales pueden usarse para controlar cierta información
que recopila el SDK de anuncios para dispositivos móviles.
ID propio del publicador, antes conocido como clave para la misma aplicación
El SDK de C++ de anuncios de Google para dispositivos móviles usa un ID propio del publicador para ayudarte
publicar anuncios más relevantes y personalizados mediante el uso de datos recopilados desde la aplicación
usa el usuario.
El ID propio del publicador está habilitado de forma predeterminada, pero puedes inhabilitarlo con el
siguiente código antes de la inicialización:
El SDK de C++ de anuncios de Google para dispositivos móviles inspecciona las excepciones que ocurren en una app para iOS y
y registrarlas si son causadas por el SDK. Estas excepciones se recopilan, por lo que
para prevenirlos en versiones futuras del SDK.
El informe de fallas está habilitado de forma predeterminada. Si no quieres excepciones relacionadas con el SDK
para que se grabe, puedes inhabilitar esta función llamando al
función DisableSDKCrashReporting(). El mejor momento para llamar a este método es cuando
se inicia la aplicación:
El informe de fallas no es compatible con dispositivos Android.
Consentimiento para cookies
Si tu app tiene requisitos especiales en Android, puedes configurar la configuración
SharedPreferencesgad_has_consent_for_cookies Consulta la
Consentimiento para cookies
de la guía de Configuración global de Android para obtener más información.
[null,null,["Última actualización: 2025-08-21 (UTC)"],[[["\u003cp\u003eThe Google Mobile Ads C++ SDK is deprecated as of June 17, 2024 and will reach End-of-Maintenance on June 17, 2025, with no further updates or bug fixes after that date.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should consider using the iOS and Android SDKs from AdMob instead of the Google Mobile Ads C++ SDK.\u003c/p\u003e\n"],["\u003cp\u003eThe SDK includes features like Publisher first-party ID (enabled by default) for personalized ads and crash reporting (iOS only, enabled by default).\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can control these features, including disabling Publisher first-party ID and crash reporting, using provided code snippets.\u003c/p\u003e\n"],["\u003cp\u003eFor Android, specific consent requirements related to cookies can be addressed using SharedPreferences.\u003c/p\u003e\n"]]],["The Google Mobile Ads C++ SDK is deprecated as of June 17, 2024, and will reach End-of-Maintenance on June 17, 2025. Consider using the AdMob iOS and Android SDKs instead. Publisher first-party ID, enabled by default, can be disabled via `SetIsSameAppKeyEnabled(false)`. For iOS, crash reporting is on by default but can be disabled using `DisableSDKCrashReporting()`. Android consent for cookies can be set using `SharedPreferences` with `gad_has_consent_for_cookies`.\n"],null,["# Global Settings\n\n| **DEPRECATED:** The Google Mobile Ads C++ SDK is *deprecated* as of June 17, 2024 and should not be adopted in projects that don't already use it. It will enter *End-of-Maintenance (EoM)* on June 17, 2025. Note that versions of the SDK released before the EoM date will continue to function, but no further bug fixes or changes will be released after the EoM date.\n|\n| Instead of the Google Mobile Ads C++ SDK, consider using the\n| [iOS](/admob/ios/quick-start) and\n| [Android](/admob/android/quick-start) SDKs from AdMob.\n| For support, reach out to the\n| [Google Mobile Ads SDK Technical Forum](https://groups.google.com/g/google-admob-ads-sdk).\n\n\u003cbr /\u003e\n\nThe following global functions may be used to control certain information\ncollected by the Mobile Ads SDK.\n\nPublisher first-party ID, formerly known as same app key\n--------------------------------------------------------\n\nThe Google Mobile Ads C++ SDK uses Publisher first-party ID to help you\ndeliver more relevant and personalized ads by using data collected from the app\nthe user is using.\n\nPublisher first-party ID is enabled by default, but you can disable it with the\nfollowing code prior to initialization: \n\n #include \"firebase/gma.h\"\n\n firebase::gma::SetIsSameAppKeyEnabled(/*is_enabled=*/false);\n\nCrash reporting (iOS Only)\n--------------------------\n\nThe Google Mobile Ads C++ SDK inspects exceptions that occur in an iOS app and\nrecords them if they are caused by the SDK. These exceptions are collected so we\ncan prevent them in future SDK versions.\n\nCrash reporting is enabled by default. If you don't want SDK-related exceptions\nto be recorded, you can disable this feature by calling the\n`DisableSDKCrashReporting()` function. The best time to call this method is when\nthe app launches: \n\n #include \"firebase/gma.h\"\n\n firebase::gma::DisableSDKCrashReporting();\n\nCrash reporting is not supported on Android devices.\n\nConsent for cookies\n-------------------\n\nIf your app has special requirements on Android, you can set the optional\n[`SharedPreferences`](//developer.android.com/reference/android/content/SharedPreferences)\n`gad_has_consent_for_cookies`. See the\n[Consent for cookies](/admob/android/global-settings#consent_for_cookies)\nsection of the Android Global Settings guide for more information."]]
