A partire dalla versione 21.0.0 dell'SDK Google Mobile Ads (GMA), puoi attivare
l'inizializzazione ottimizzata dell'SDK e il caricamento degli annunci per migliorare la
reattività complessiva degli annunci e contribuire a evitare gli errori "L'applicazione non risponde"
(ANR) nella tua app.
Questa guida descrive le modifiche che devi apportare per attivare queste ottimizzazioni.
SDK Google Mobile Ads versione 21.0.0 o successive.
Aggiornare il file manifest
Sono disponibili due flag di ottimizzazione: OPTIMIZE_INITIALIZATION e
OPTIMIZE_AD_LOADING. Una volta attivate, le attività di inizializzazione e caricamento degli annunci che richiedono tempi di elaborazione prolungati vengono scaricate nei thread in background.
Segui le istruzioni riportate di seguito per aggiungere i tag <meta-data> corrispondenti nel file AndroidManifest.xml della tua app e attivare i flag. Tieni presente che puoi
attivare una o entrambe le opzioni nella stessa app.
Ottimizzare l'inizializzazione dell'SDK Google Mobile Ads
Il modo migliore per ottimizzare l'inizializzazione è chiamare
MobileAds.initialize()
su un thread in background, come descritto nella
Guida introduttiva.
Se lo fai già, non devi attivare questo flag.
Se devi chiamare il metodo sul thread principale, l'attivazione del flag riportato di seguito
sposterà alcune delle attività di inizializzazione sul thread in background.
[null,null,["Ultimo aggiornamento 2025-09-02 UTC."],[[["\u003cp\u003eStarting with Google Mobile Ads SDK version 21.0.0, you can optimize SDK initialization and ad loading to enhance ad responsiveness and mitigate ANR errors.\u003c/p\u003e\n"],["\u003cp\u003eTo enable these optimizations, you need to add specific \u003ccode\u003e<meta-data>\u003c/code\u003e tags to your app's \u003ccode\u003eAndroidManifest.xml\u003c/code\u003e file, controlling initialization and ad loading separately.\u003c/p\u003e\n"],["\u003cp\u003eBy default, both optimization flags (\u003ccode\u003eOPTIMIZE_INITIALIZATION\u003c/code\u003e and \u003ccode\u003eOPTIMIZE_AD_LOADING\u003c/code\u003e) are set to \u003ccode\u003efalse\u003c/code\u003e and require manual activation.\u003c/p\u003e\n"],["\u003cp\u003eOptimizing initialization is best achieved by calling \u003ccode\u003eMobileAds.initialize()\u003c/code\u003e on a background thread; if this is not feasible, enabling the \u003ccode\u003eOPTIMIZE_INITIALIZATION\u003c/code\u003e flag helps by offloading some tasks to a background thread.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eOPTIMIZE_AD_LOADING\u003c/code\u003e flag enhances ad load calls for all ad formats, improving overall ad loading performance.\u003c/p\u003e\n"]]],[],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/optimize-initialization \"View this page for the Android platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/optimize-initialization \"View this page for the Unity platform docs.\")\n\n\u003cbr /\u003e\n\nStarting from Google Mobile Ads (GMA) SDK version 21.0.0, you can enable\noptimized SDK initialization and ad loading to improve the overall\nresponsiveness of ads and help prevent [\"Application Not Responding\"\n(ANR)](//developer.android.com/topic/performance/vitals/anr) errors on your app.\nThis guide outlines the changes you need to make to enable these optimizations.\n\nRequirements\n\n- Complete the [Get Started guide](/ad-manager/mobile-ads-sdk/android/quick-start).\n\n\u003c!-- --\u003e\n\n- Google Mobile Ads SDK version 21.0.0 or higher.\n\nUpdate your manifest file\n\nThere are two optimization flags available: `OPTIMIZE_INITIALIZATION` and\n`OPTIMIZE_AD_LOADING`. Once they're turned on, the initialization and ad\nloading tasks that require extended processing time are offloaded to\nbackground threads.\n\nFollow the instructions below to add the corresponding `\u003cmeta-data\u003e` tags in\nyour app's `AndroidManifest.xml` file and turn on the flags. Note that you can\nturn on one or both options in the same app.\n| **Important:** Starting with Google Mobile Ads SDK version 24.0.0, the `OPTIMIZE_INITIALIZATION` and `OPTIMIZE_AD_LOADING` flags are set to `true` by default. In versions prior to 24.0.0, these flags are set to `false` by default.\n\nOptimize Google Mobile Ads SDK initialization\n\n: The best way to optimize initialization is to call\n [`MobileAds.initialize()`](/ad-manager/mobile-ads-sdk/android/reference/com/google/android/gms/ads/MobileAds#initialize(android.content.Context,com.google.android.gms.ads.initialization.OnInitializationCompleteListener))\n on a background thread, as described in the\n [Get Started guide](/ad-manager/mobile-ads-sdk/android/quick-start#initialize_the_mobile_ads_sdk).\n If you are already doing so, you don't need to enable this flag.\n\n If you must call the method on the main thread, enabling the flag below will\n move some of the initialization tasks to the background thread. \n\n ```scdoc\n \u003cmanifest\u003e\n ...\n \u003capplication\u003e\n ...\n \u003cmeta-data\n android:name=\"com.google.android.gms.ads.flag.OPTIMIZE_INITIALIZATION\"\n android:value=\"true\"/\u003e\n \u003c/application\u003e\n \u003c/manifest\u003e\n ```\n\nOptimize ad loading\n\n: The flag below optimizes ad load calls for all ad formats:\n\n ```scdoc\n \u003cmanifest\u003e\n ...\n \u003capplication\u003e\n ...\n \u003cmeta-data\n android:name=\"com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING\"\n android:value=\"true\"/\u003e\n \u003c/application\u003e\n \u003c/manifest\u003e\n ```"]]
