Este guia explica como ativar anúncios de teste na sua integração de anúncios. Recomendamos
que você ative os anúncios de teste durante o desenvolvimento para testar
o comportamento da taxa de cliques sem afetar as estatísticas das suas campanhas de reserva nem
gerar cobranças para os anunciantes no Ad Exchange.
O modo mais rápido de fazer testes é usando blocos de anúncios de demonstração do Google.
Eles não ficam associados à sua conta do Ad Manager, então não há risco de gerar tráfego inválido ao
usar os blocos.
Confira alguns blocos de anúncios de demonstração que levam a criativos de teste específicos para cada formato:
Importante: os blocos de anúncios de demonstração são configurados para veicular anúncios de venda direta no Ad
Manager, mas esses anúncios não retornam as Opções de Anúncios.
Ativar dispositivos de teste
Se quiser fazer testes mais rigorosos com anúncios idênticos aos de produção, agora é possível
configurar seu aparelho como um dispositivo de teste e usar os IDs de bloco de anúncios que
você criou na interface do Ad Manager.
Siga as etapas abaixo para adicionar seu aparelho como um dispositivo de teste.
Adicionar o dispositivo de teste de forma programática
Para registrar seu dispositivo de teste, siga estas etapas:
Carregue o app integrado aos anúncios e faça uma solicitação de anúncio.
Procure uma mensagem semelhante a esta na saída do Logcat. Ela mostra o ID do dispositivo e como adicioná-lo como um dispositivo de teste:
I/Ads: Use RequestConfiguration.Builder.setTestDeviceIds(Arrays.asList("33BE2250B43518CCDA7DE426D04EE231"))
to get test ads on this device."
Copie o ID do dispositivo de teste para a área de transferência.
Substitua TEST_DEVICE_ID pelo ID do seu dispositivo de teste.
Você pode verificar isTestDevice() para confirmar se o aparelho foi adicionado corretamente como um dispositivo de teste.
Execute o app novamente. Se o anúncio for do Google, você vai ver um rótulo Anúncio de teste centralizado na parte de cima dele (banner, intersticial ou vídeo premiado):
Para anúncios nativos avançados, o recurso de título é precedido pela string Anúncio de teste.
Você pode clicar com segurança nos anúncios com o rótulo Anúncio de teste. Solicitações, impressões e cliques em anúncios de teste não aparecem nos relatórios da sua conta.
Testar com mediação
Os blocos de anúncios de amostra do Google só mostram anúncios do Google. Para testar sua
configuração de mediação,
use a abordagem de ativação de dispositivos de teste.
Os anúncios mediados NÃO renderizam um rótulo "Anúncio de teste". Você é responsável por
garantir que os anúncios de teste estejam ativados em cada uma das suas redes de mediação para que elas
não sinalizem sua conta por atividade inválida. Consulte o guia de mediação de cada rede para mais informações.
Se você não tiver certeza se o adaptador de uma rede de mediação aceita anúncios de teste, o mais seguro é evitar clicar em anúncios dessa rede durante o desenvolvimento. Você pode usar o método getMediationAdapterClassName() em qualquer um dos formatos de anúncio para descobrir qual rede veiculou o anúncio atual.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Não contém as informações de que eu preciso","missingTheInformationINeed","thumb-down"],["Muito complicado / etapas demais","tooComplicatedTooManySteps","thumb-down"],["Desatualizado","outOfDate","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Problema com as amostras / o código","samplesCodeIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-05 UTC."],[[["\u003cp\u003eThis guide helps you enable test ads in your app during development to avoid impacting campaign stats and accidental charges.\u003c/p\u003e\n"],["\u003cp\u003eYou can use Google-provided demo ad units or configure your own device as a test device for more realistic testing scenarios.\u003c/p\u003e\n"],["\u003cp\u003eWhen using your own ad units, register your device programmatically for testing and remember to remove this configuration before releasing your app.\u003c/p\u003e\n"],["\u003cp\u003eTest ads are clearly labeled, ensuring clicks won't affect your reports; however, mediated ads might not have this label, requiring extra caution.\u003c/p\u003e\n"],["\u003cp\u003eFor mediation testing, enable test ads for each network individually and refer to their respective guides to ensure accurate results and prevent invalid activity flags.\u003c/p\u003e\n"]]],["To enable test ads, use Google-provided demo ad units during development, replacing them with your own before publishing. For more rigorous testing, configure devices as test devices. Programmatically, add devices by retrieving the device ID from logcat, then use `RequestConfiguration.Builder.setTestDeviceIds()` to register it. Test ads will have a \"Test Ad\" label. For mediation, use test devices, as mediated ads lack the label; consult each network's guide and use `getMediationAdapterClassName()` to identify the serving network.\n"],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/test-ads \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/test-ads \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/test-ads \"View this page for the Unity platform docs.\") [Flutter](/ad-manager/mobile-ads-sdk/flutter/test-ads \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\nThis guide explains how to enable test ads for your ads integration. It's\nrecommended that you enable test ads during development so you can test\nclick-through behavior without affecting your reservation campaigns' stats or\ncharging advertisers on Ad Exchange.\n\n\u003cbr /\u003e\n\nPrerequisite\n\n- Complete [Get Started](/ad-manager/mobile-ads-sdk/android/quick-start).\n\nDemo ad units\n\nThe quickest way to enable testing is to use Google-provided demo ad units.\nThese ad units are not associated with your Ad Manager\naccount, so there's no risk of your account generating invalid traffic when\nusing these ad units.\n| **Key Point:** Make sure you replace these IDs with your own ad unit ID before publishing your app.\n\nHere are demo ad units that point to specific test creatives for each format:\n\n| Ad format | Demo ad unit ID |\n|-----------------------------------------------------------------------------------|----------------------------------------------|\n| [App Open](/ad-manager/mobile-ads-sdk/android/app-open) | `/21775744923/example/app-open` |\n| [Adaptive Banner](/ad-manager/mobile-ads-sdk/android/banner) | `/21775744923/example/adaptive-banner` |\n| [Fixed Size Banner](/ad-manager/mobile-ads-sdk/android/banner/fixed-size) | `/21775744923/example/fixed-size-banner` |\n| [Interstitial](/ad-manager/mobile-ads-sdk/android/interstitial) | `/21775744923/example/interstitial` |\n| [Rewarded Ads](/ad-manager/mobile-ads-sdk/android/rewarded) | `/21775744923/example/rewarded` |\n| [Rewarded Interstitial](/ad-manager/mobile-ads-sdk/android/rewarded-interstitial) | `/21775744923/example/rewarded-interstitial` |\n| [Native](/ad-manager/mobile-ads-sdk/android/native) | `/21775744923/example/native` |\n| [Native Video](/ad-manager/mobile-ads-sdk/android/native/video-ads) | `/21775744923/example/native-video` |\n\nKey Point: These demo ad units are configured to serve direct-sold ads in Ad Manager, and direct-sold ads do not return AdChoices.\n\nEnable test devices\n\nIf you want to do more rigorous testing with production-looking ads, you can\nnow configure your device as a test device and use your own ad unit IDs that\nyou've created in the Ad Manager UI.\n\n\nFollow the steps below to add your device as a test device.\n| **Key Point:** Android emulators are automatically configured as test devices.\n\nAdd your test device programmatically\n\nTo register your test device, complete the following steps:\n\n1. Load your ads-integrated app and make an ad request.\n2. Check the logcat output for a message similar to the following, which shows you your device ID and how to add it as a test device: \n\n ```text\n I/Ads: Use RequestConfiguration.Builder.setTestDeviceIds(Arrays.asList(\"33BE2250B43518CCDA7DE426D04EE231\"))\n to get test ads on this device.\"\n ```\n Copy your test device ID to your clipboard.\n3. Modify your code to call\n\n [`RequestConfiguration.Builder.setTestDeviceIds()`](/ad-manager/mobile-ads-sdk/android/reference/com/google/android/gms/ads/RequestConfiguration.Builder#setTestDeviceIds(java.util.List%3Cjava.lang.String%3E))\n\n and pass in a list of your test device IDs.\n\n Java \n\n List\u003cString\u003e testDeviceIds = Arrays.asList(\"\u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e\");\n RequestConfiguration configuration =\n new RequestConfiguration.Builder().setTestDeviceIds(testDeviceIds).build();\n MobileAds.setRequestConfiguration(configuration); \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/java/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/RequestConfigurationSnippets.java#L15-L18\n\n Kotlin \n\n val testDeviceIds = listOf(\"\u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e\")\n val configuration = RequestConfiguration.Builder().setTestDeviceIds(testDeviceIds).build()\n MobileAds.setRequestConfiguration(configuration) \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/kotlin/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/RequestConfigurationSnippets.kt#L27-L29\n\n Replace \u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e with your test device ID.\n\n You can optionally check\n\n [`isTestDevice()`](/ad-manager/mobile-ads-sdk/android/reference/com/google/android/gms/ads/AdRequest#isTestDevice(android.content.Context))\n\n to confirm that your device was properly added as a test device.\n | **Caution:** Be sure to remove the code that sets these test device IDs before you release your app.\n4. Re-run your app. If the ad is a Google ad, you'll see a **Test Ad** label\n centered at the top of the ad (banner, interstitial, or rewarded video):\n\n | **Note:** To see the **Test Ad** label, you need to be using an SDK version of 11.6.0 or higher.\n\n For native advanced ads, the headline asset is prepended with the string **Test Ad**.\n\nAds with this **Test Ad** label are safe to click. Requests, impressions, and\nclicks on test ads won't show up in your account's reports.\n| **Note:** Mediated ads do *NOT* render a **Test Ad** label. See the following section for details.\n\nTesting with mediation\n\nGoogle's sample ad units only show Google Ads. To test your\n\nmediation configuration,\nyou must use the [enable test devices](#enable_test_devices)\napproach.\n\nMediated ads do *NOT* render a Test Ad label. You are responsible for\nensuring that test ads are enabled for each of your mediation networks so these\nnetworks don't flag your account for invalid activity. See each network's\nrespective [mediation guide](/ad-manager/mobile-ads-sdk/android/mediation)\nfor more information.\n\nIf you aren't sure whether a mediation ad network adapter supports test ads, it\nis safest to avoid clicking on ads from that network during development. You\ncan use the\n\n[`getMediationAdapterClassName()`](/ad-manager/mobile-ads-sdk/android/reference/com/google/android/gms/ads/ResponseInfo#getMediationAdapterClassName())\n\nmethod on any of the ad formats to figure out which ad network served the\ncurrent ad."]]
