Per le offerte:
SDK Google Mobile Ads 7.53.1
o versioni successive.
Inizializza l'SDK Google Mobile Ads
La guida rapida mostra come inizializzare l'SDK Google Mobile Ads.
Durante la chiamata di inizializzazione, vengono inizializzati anche gli adattatori di mediazione. È importante attendere il completamento dell'inizializzazione prima di caricare gli annunci per verificare la piena partecipazione di ogni ad network alla prima richiesta di annuncio.
Il seguente esempio di codice mostra come controllare lo stato di inizializzazione di ogni adattatore
prima di effettuare una richiesta di annuncio.
Ogni classe di formato dell'annuncio ha una proprietà GADResponseInfo che contiene
adNetworkClassName che restituisce il nome della classe della rete pubblicitaria per l'annuncio
corrente. adNetworkClassName ha un valore solo dopo che un annuncio è stato caricato
correttamente. Il seguente codice mostra come ottenere queste informazioni per gli annunci banner.
Swift
funcadViewDidReceiveAd(_bannerView:AdManagerBannerView){print("Banner adapter class name: \(bannerView.responseInfo.adNetworkClassName)")}
Objective-C
-(void)adViewDidReceiveAd:(GAMBannerView*)bannerView{NSLog(@"Banner adapter class name: %@",bannerView.responseInfo.adNetworkClassName);}
Assicurati di disattivare l'aggiornamento in tutte le UI delle origini annuncio di terze parti per le unità pubblicitarie banner utilizzate nella mediazione. In questo modo si evita un
doppio aggiornamento, poiché Ad Manager attiva anche un aggiornamento
in base alla frequenza di aggiornamento dell'unità pubblicitaria banner.
Utilizzare gli annunci nativi con la mediazione
Di seguito sono riportate alcune best practice da tenere in considerazione quando implementi la mediazione
nativa.
Norme sulla presentazione degli annunci nativi
Ogni rete pubblicitaria ha le proprie norme. Quando utilizzi la mediazione, è importante
ricordare che la tua app deve comunque rispettare le norme della rete
di mediazione che ha fornito l'annuncio.
Evita di utilizzare la classe GADMultipleAdsAdLoaderOptions quando effettui richieste
Le richieste di più annunci nativi pubblicano solo annunci Google. La funzionalità relativa a più annunci nativi
non supporta la mediazione.
Leggi statali sulla privacy degli Stati Uniti e GDPR
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Mancano le informazioni di cui ho bisogno","missingTheInformationINeed","thumb-down"],["Troppo complicato/troppi passaggi","tooComplicatedTooManySteps","thumb-down"],["Obsoleti","outOfDate","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Problema relativo a esempi/codice","samplesCodeIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-06 UTC."],[[["\u003cp\u003eThis guide explains how to integrate a mediation adapter with your iOS app to maximize ad revenue by utilizing multiple ad networks.\u003c/p\u003e\n"],["\u003cp\u003eBefore integrating mediation, ensure you've integrated the desired ad formats (banner, interstitial, native, rewarded, rewarded interstitial) into your app.\u003c/p\u003e\n"],["\u003cp\u003eInitialize the Mobile Ads SDK to enable mediation adapters and check each adapter's initialization status before loading ads for optimal performance.\u003c/p\u003e\n"],["\u003cp\u003eIdentify the ad network serving the ad by accessing the \u003ccode\u003eadNetworkClassName\u003c/code\u003e property within the \u003ccode\u003eGADResponseInfo\u003c/code\u003e of the ad format class.\u003c/p\u003e\n"],["\u003cp\u003eFor banner ads used in mediation, disable refresh in third-party ad source UIs to avoid double refreshing, and consider native ad presentation policies and privacy laws when implementing native mediation.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\nThis guide shows you how to integrate a mediation adapter with your\niOS app.\n\nPrerequisites\n\nBefore you can integrate mediation for an ad format, you need to integrate that\nad format into your app:\n\n- [Banner Ads](/ad-manager/mobile-ads-sdk/ios/banner)\n- [Interstitial Ads](/ad-manager/mobile-ads-sdk/ios/interstitial)\n- [Native Ads](/ad-manager/mobile-ads-sdk/ios/native)\n- [Rewarded Ads](/ad-manager/mobile-ads-sdk/ios/rewarded)\n- [Rewarded Interstitial\n Ads](/ad-manager/mobile-ads-sdk/ios/rewarded-interstitial)\n\nNew to mediation? Read\n\n[Introduction to mediation](//support.google.com/admanager/answer/6272813).\n\nFor bidding:\n\nGoogle Mobile Ads SDK 7.53.1\nor higher.\n\nInitialize Google Mobile Ads SDK\n\nThe quick start guide shows you how to [initialize the Google Mobile Ads SDK](/ad-manager/mobile-ads-sdk/ios/quick-start#initialize_the_mobile_ads_sdk).\nDuring that initialization call, mediation adapters also\nget initialized. It is important to wait for initialization to complete before\nyou load ads in order to verify full participation from every ad network on the\nfirst ad request.\n| **Important:** Bidding adapters require you to explicitly initialize Google Mobile Ads SDK.\n\nThe following sample code shows how you can check each adapter's initialization\nstatus prior to making an ad request. \n\nSwift \n\n import GoogleMobileAds\n\n @UIApplicationMain\n class AppDelegate: UIResponder, UIApplicationDelegate {\n\n func application(_ application: UIApplication,\n didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -\u003e Bool {\n\n MobileAds.shared.start { status in\n // Optional: Log each adapter's initialization latency.\n let adapterStatuses = status.adapterStatusesByClassName\n for adapter in adapterStatuses {\n let adapterStatus = adapter.value\n NSLog(\"Adapter Name: %@, Description: %@, Latency: %f\", adapter.key,\n adapterStatus.description, adapterStatus.latency)\n }\n // Start loading ads here...\n }\n\n return true\n }\n\n }\n\nObjective-C \n\n @import GoogleMobileAds;\n\n @implementation AppDelegate\n\n - (BOOL)application:(UIApplication *)application\n didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {\n\n GADMobileAds \\*ads = \\[GADMobileAds sharedInstance\\];\n \\[ads startWithCompletionHandler:\\^(GADInitializationStatus \\*status) {\n // Optional: Log each adapter's initialization latency.\n NSDictionary \\*adapterStatuses = \\[status adapterStatusesByClassName\\];\n for (NSString \\*adapter in adapterStatuses) {\n GADAdapterStatus \\*adapterStatus = adapterStatuses\\[adapter\\];\n NSLog(@\"Adapter Name: %@, Description: %@, Latency: %f\", adapter,\n adapterStatus.description, adapterStatus.latency);\n }\n // Start loading ads here...\n }\\];\n return YES;\n }\n\n @end\n\nKnow which ad network wins\n\nEach ad format class has a `GADResponseInfo` property that contains\n`adNetworkClassName` which returns the class name of the ad network for the\ncurrent ad. `adNetworkClassName` only has a value once an ad successfully\nloads. The following code shows you how to get that information for banner ads. \n\nSwift \n\n func adViewDidReceiveAd(_ bannerView: AdManagerBannerView) {\n print(\"Banner adapter class name: \\(bannerView.responseInfo.adNetworkClassName)\")\n }\n\nObjective-C \n\n - (void)adViewDidReceiveAd:(GAMBannerView *)bannerView {\n NSLog(@\"Banner adapter class name: %@\", bannerView.responseInfo.adNetworkClassName);\n }\n\nRefer to [Retrieving Information about the Ad Response](/ad-manager/mobile-ads-sdk/ios/response-info)\nfor details.\n\n\u003cbr /\u003e\n\nUse banner ads with mediation\n\nMake sure to disable refresh in all third-party ad source UIs for banner ad\nunits used in mediation. This prevents a\ndouble refresh since Ad Manager also triggers a refresh\nbased on your banner ad unit's refresh rate.\n\nUse native ads with mediation\n\nThe following are some best practices to consider when implementing native\nmediation.\n\nNative ad presentation policy\n: Each ad network has its own policies. When using mediation, it's important to\n remember that your app still needs to abide by the policies of the mediated\n network that provided the ad.\n\nAvoid using the `GADMultipleAdsAdLoaderOptions` class when making requests\n: Requests for multiple native ads only serve Google ads. The multiple native\n ads feature does not support mediation.\n\nUS states privacy laws and GDPR\n\nIf you need to comply with the [U.S. states privacy\nlaws](//support.google.com/admanager/answer/9561023) or [General Data Protection\nRegulation (GDPR)](//support.google.com/admanager/answer/7666366), follow the\nsteps in [US state regulations\nsettings](//support.google.com/admanager/answer/10115735) or [GDPR\nsettings](//support.google.com/admanager/answer/10113006#adding_ad_partners_to_published_gdpr_messages) to add your\nmediation partners in Ad Manager Privacy \\& messaging's\nUS states or GDPR ad partners list. Failure to do so can lead to partners\nfailing to serve ads on your app.\n\nLearn more about enabling [restricted data processing\n(RDP)](/ad-manager/mobile-ads-sdk/ios/privacy/us-states) and obtaining GDPR consent with the\n[Google User Messaging Platform (UMP) SDK](/ad-manager/mobile-ads-sdk/ios/privacy)."]]