Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
As seguintes funções globais podem ser usadas para controlar determinadas informações
coletados pelo SDK dos anúncios para dispositivos móveis.
ID próprio do editor, antes conhecido como mesma chave de app
O SDK dos anúncios para dispositivos móveis do Google para C++ usa o ID próprio do editor para ajudar você
veicular anúncios mais relevantes e personalizados usando dados coletados no app
que o usuário está usando.
O ID próprio do editor é ativado por padrão, mas é possível desativá-lo com a opção
código a seguir antes da inicialização:
O SDK dos anúncios para dispositivos móveis do Google para C++ inspeciona exceções que ocorrem em um app iOS e
os registra se forem causados pelo SDK. Essas exceções são coletadas para que
poderão ser impedidos em versões futuras do SDK.
O Crash reporting está ativado por padrão. Se você não quiser exceções relacionadas a SDKs
sejam gravadas, é possível desativar esse recurso chamando o
função DisableSDKCrashReporting(). O melhor momento para chamar esse método é
o app é iniciado:
Não é possível gerar relatórios de erros em dispositivos Android.
Consentimento para cookies
Caso seu app tenha requisitos especiais no Android, defina o
SharedPreferencesgad_has_consent_for_cookies. Consulte a
Consentimento para o uso de cookies
do guia de configurações globais do Android para saber mais.
[null,null,["Última atualização 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."]]
