Please direct integration issues or Beta related bugs to email@example.com. Beta SDKs will not be supported upon beta testing completion. We recommend you update to the latest SDK version, once Beta testing is completed.
Use this guide to add Vungle iOS SDK into your app, using AdMob as your main advertising mediation layer.
AdMob iOS adapter v18.104.22.168 is compatible with Vungle iOS SDK v6.4.1 and is tested with Google SDK v7.44.0
Download AdMob iOS Adapter v22.214.171.124 and include Vungle SDK, adapter(libVungleAdapter.a) and related files(VungleAdapter.h, VungleAdNetworkExtras.h, VungleRouterConfiguration.h VungleRouterConsent.h) in your project manually.
Vungle iOS Beta SDK is also available through cocoaPods. Add the following line in your project's pod file followed by a quick pod install run to update the project with the Beta version of Vungle iOS SDK.
pod "VungleSDK-iOS", "6.4.1"
- Ad units set up on AdMob dashboard.
- Vungle App ID and Placement IDs created on Vungle dashboard and placement IDs are linked to ad units on AdMob dashboard.
- Set up the application with the right XCode and iOS SDK version as detailed in the Vungle iOS integration document
Refer AdMob's integration document for detailed steps to setup Ad units and link Vungle's Placement IDs to ad units on AdMob dashboard.
Before you begin to test the new adapter-
- Integrate the application with the latest adapter files(v126.96.36.199) and Vungle SDK(v6.4.1).
- Update the Google Mobile Ads SDK to the latest version in the project.
Verify that the integration contains the updated SDK and adapter (Vungle/6.4.1 and AdMob/188.8.131.52) by using a network monitor tool such as Charles. Initialize the app and check the User-Agent in the Request Headers of /config call from Vungle to confirm the SDK version.
v 6.4.1 supports AdMob’s banner ads.
To display banner ad in the application, create an MREC placement on Vungle dashboard and link this placement to a Banner Ad unit on AdMob dashboard.
Presently, Vungle supports banner size 300*250 and should be specified as kGADAdSizeMediumRectangle as ad constant size in the implementation.
//Create a Banner view of type kGADAdSizeMediumRectangle GADBannerView *bannerView = [[GADBannerView alloc] initWithAdSize:kGADAdSizeMediumRectangle]; [self addBannerViewToView:self.bannerView];
Loading, playing and closing the banner ad is detailed in the AdMob integration guide.
For SDK version 6.4.1 onwards, publishers can now restrict from passing IDFV from the device to the SDK.
//Set the bool value YES to pass the IDFV from device to SDK [VungleRouterConfiguration setPublishIDFV:YES]; //Set the bool value NO to disable the IDFV collection from device to SDK [VungleRouterConfiguration setPublishIDFV:NO];
Starting from v6.4.1, you can prevent the SDK from requesting ads or even initializing if the storage of your iPhone falls below a predefined threshold.
//Integer value sets the required minimum available free storage space to be able to initialize the SDK [VungleRouterConfiguration setMinSpaceForInit:]; //Integer value sets the required minimum available free storage space to be able to request an Ad [VungleRouterConfiguration setMinSpaceForAdLoad:];
As documented by AdMob, starting from version 7.42.2 or higher, AdMob’s Rewarded Ads (New APIs), let’s you cache multiple ads at the same time for a single ad unit.
Since Vungle does not support this feature, the Ad request for the second “Load ad” will not be filled by Vungle, rather it will be passed to the next ad network in the waterfall.