This guide shows you how to use the Google Mobile Ads SDK to load and display ads from DT Exchange using AdMob Mediation, covering waterfall integrations. It covers how to add DT Exchange to an ad unit's mediation configuration and how to integrate the DT Exchange SDK and adapter into an iOS app.
Supported integrations and ad formats
The mediation adapter for DT Exchange has the following capabilities:
Integration | |
---|---|
Bidding | |
Waterfall | |
Formats | |
Banner | |
Interstitial | |
Rewarded | |
Native |
Requirements
- iOS deployment target of 12.0 or higher
Latest Google Mobile Ads SDK
Complete the mediation Get started guide
Step 1: Set up configurations in DT Exchange UI
Add new app and ad placement
Sign up or log in to DT Exchange Console.
Click on the Add App button to add your app.
Select your Platform, fill out the rest of the form, and click Add Placements.
Android
iOS
Enter a name for the new placement in the field labeled Name your Placement and select your desired Placement Type from the dropdown list. Finally, click Save Placement.
App ID and Placement ID
Open the left navigation bar by hovering your mouse over it. Then click Apps from the left menu.
On the App Management page, take note of the App ID next to your app.
Select your app, navigate to the Placements tab, and click on the copy icon next to Placement Name. Take note of the Placement ID.
Publisher ID, Consumer Key and Consumer Secret
Click on your username from the left menu and select User Profile.
Take note of the Publisher ID, Consumer Key, and Consumer Secret as these are needed in the next step.
Step 2: Set up DT Exchange demand in AdMob UI
광고 단위에 대한 미디에이션 설정 구성
DT Exchange 를 광고 단위의 미디에이션 구성에 추가해야 합니다.
먼저 AdMob 계정에 로그인합니다. 그런 다음 미디에이션 탭으로 이동합니다. 수정할 기존 미디에이션 그룹이 있는 경우 해당 미디에이션 그룹의 이름을 클릭하여 수정한 후 DT Exchange 광고 소스로 추가로 건너뜁니다.
새 미디에이션 그룹을 만들려면 미디에이션 그룹 만들기를 선택합니다.
광고 형식과 플랫폼을 입력하고 계속을 클릭합니다.
미디에이션 그룹에 이름을 지정하고 타겟팅할 위치를 선택합니다. 미디에이션 그룹 상태를 사용으로 설정한 다음 광고 단위 추가를 클릭합니다.
이 미디에이션 그룹을 하나 이상의 기존AdMob 광고 단위와 연결합니다. 그런 다음 완료를 클릭합니다.
이제 광고 단위 카드가 선택한 광고 단위로 채워진 것을 볼 수 있습니다.
광고 소스로 DT Exchange 추가
광고 소스 섹션의 폭포식 구조 카드에서 광고 소스 추가를 선택합니다. 그런 다음 DT Exchange을 선택합니다.
DT Exchange를 선택하고 최적화 스위치를 사용 설정합니다. 이전 섹션에서 가져온 Publisher ID, Consumer Secret and Consumer Key을 입력하여DT Exchange에 대해 광고 소스 최적화를 설정합니다. 그런 다음DT Exchange 에 eCPM 값을 입력하고 계속을 클릭합니다.이미 DT Exchange에 대한 매핑이 있는 경우 해당 매핑을 선택할 수 있습니다. 그렇지 않으면 매핑 추가를 클릭합니다.
그런 다음 이전 섹션에서 얻은 Application ID and Placement ID를 입력합니다. 그런 다음 완료를 클릭합니다.
Add Fyber to GDPR and US state regulations ad partners list
GDPR 설정 및 미국 주 규정 설정 Fyber 를 AdMob UI의 GDPR 및 미국 주 규정 광고 파트너 목록에 추가합니다.
Step 3: Import the DT Exchange SDK and adapter
Using CocoaPods (recommended)
Add the following line to your project's Podfile:
pod 'GoogleMobileAdsMediationFyber'
From the command line run:
pod install --repo-update
Manual integration
- Download the latest version of the
DT Exchange SDK for iOS
and link the following frameworks to your project:
IASDKCore.framework
IASDKMRAID.framework
IASDKVideo.framework
- Download the latest version of the DT Exchange adapter from the download
link in Changelog and link
FyberAdapter.framework
in your project. - Add the following frameworks to your project:
libxml2.2.tbd
Step 4: Implement privacy settings on DT Exchange SDK
EU consent and GDPR
Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.
DT Exchange contains an API that lets you forward user consent to their SDK. The following sample code shows how to pass consent information to the DT Exchange SDK manually. Should you choose to pass consent information to the DT Exchange SDK manually, it is recommended that this code is called prior to requesting ads through the Google Mobile Ads SDK.
Swift
import IASDKCore
// ...
IASDKCore.sharedInstance().gdprConsent = IAGDPRConsentType.given
IASDKCore.sharedInstance().gdprConsentString = "myGdprConsentString"
Objective-C
#import <IASDKCore/IASDKCore.h>
// ...
[IASDKCore.sharedInstance setGDPRConsent:YES];
[IASDKCore.sharedInstance setGDPRConsentString:@"myGdprConsentString"];
Visit DT Exchange's GDPR Resource Page and their GDPR implementation guide for more details and the values that may be provided in the method.
US states privacy laws
U.S. states privacy laws require giving users the right to opt out of the "sale" of their "personal information" (as the law defines those terms), with the opt-out offered via a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The U.S. states privacy laws compliance guide offers the ability to enable restricted data processing for Google ad serving, but Google is unable to apply this setting to each ad network in your mediation chain. Therefore, you must identify each ad network in your mediation chain that may participate in the sale of personal information and follow guidance from each of those networks to ensure compliance.
DT Exchange contains an API that lets you forward user consent to their SDK. The following sample code shows how to pass consent information to the DT Exchange SDK manually. Should you choose to pass consent information to the DT Exchange SDK manually, it is recommended that this code is called prior to requesting ads through the Google Mobile Ads SDK.
Swift
import IASDKCore
// ...
IASDKCore.sharedInstance().ccpaString = "myCCPAConsentString"
Objective-C
#import <IASDKCore/IASDKCore.h>
// ...
[IASDKCore.sharedInstance setCCPAString:@"myCCPAConsentString"];
Visit DT Exchange's CCPA Resource Page and their CCPA implementation guide for more details and the values that may be provided in the method.
Step 5: Add required code
SKAdNetwork integration
Follow DT Exchange's documentation
to add the SKAdNetwork identifiers to your project's Info.plist
file.
Step 6: Test your implementation
테스트 광고 사용 설정
AdMob
테스트 광고 확인
DT Exchange에서 테스트 광고를 수신하고 있는지 확인하려면 광고 검사기에서 DT Exchange (Waterfall) 광고 소스를 사용하여 단일 광고 소스 테스트를 사용 설정하세요.
Optional steps
Network-specific parameters
The DT Exchange adapter supports additional request parameters that can be
passed to the adapter using the GADMAdapterFyberExtras()
. The adapter looks
for the following keys in the bundle:
Request parameters and values | |
---|---|
setUserData The age, gender and zip code of the user. |
IAUserData |
setMuteAudio
|
Boolean. Mute or unmute video |
Here's a code example of how to set these ad request parameters:
Swift
let userData = IAUserData.build({ builder in
builder.age = 23
builder.gender = IAUserGenderType.male
builder.zipCode = "1234"
}];
let request = GADRequest()
let extras = GADMAdapterFyberExtras()
extras.userData = userData
extras.muteAudio = true
request.register(extras)
Objective-C
IAUserData *userData = [IAUserData build:^(id<IAUserDataBuilder> _Nonnull builder) {
builder.age = 23;
builder.gender = IAUserGenderTypeMale;
builder.zipCode = @"1234";
}];
GADRequest *request = [GADRequest request];
GADMAdapterFyberExtras *extras = [[GADMAdapterFyberExtras alloc] init];
extras.userData = userData;
extras.muteAudio = YES;
[request registerAdNetworkExtras:extras];
Consult the DT Exchange integration guide for more information.
Error codes
If the adapter fails to receive an ad from DT Exchange, you can check the
underlying error from the ad response using
GADResponseInfo.adNetworkInfoArray
under the following class:
GADMediationAdapterFyber
Here are the codes and accompanying messages thrown by the DT Exchange adapter when an ad fails to load:
Error code | Reason |
---|---|
0-10 | DT Exchange SDK returned an error. See documentation for more details. |
101 | DT Exchange server parameters configured in the AdMob UI are missing/invalid. |
102 | The requested ad size does not match a DT Exchange supported banner size. |
103 | Failed to show ad because ad object has already been used. |
104 | Failed to show DT Exchange ads due to ad not ready. |
105 | DT Exchange SDK returned an initialization error. |
DT Exchange iOS Mediation Adapter Changelog
Next Version
- Removed deprecated usage of keywords.
- Removed didFailToPresentWithError call from within videoInterruptedWithError callback. Fixes a bug which was causing the ad to disappear and a blank screen to be shown.
Version 8.3.2.0
- Verified compatibility with DT Exchange SDK version 8.3.2.
Built and tested with:
- Google Mobile Ads SDK version 11.8.0.
- DT Exchange SDK version 8.3.2.
Version 8.3.1.0
- Verified compatibility with DT Exchange SDK version 8.3.1.
Built and tested with:
- Google Mobile Ads SDK version 11.6.0.
- DT Exchange SDK version 8.3.1.
Version 8.3.0.0
- Verified compatibility with DT Exchange SDK version 8.3.0.
Built and tested with:
- Google Mobile Ads SDK version 11.5.0.
- DT Exchange SDK version 8.3.0.
Version 8.2.8.0
- Verified compatibility with DT Exchange SDK version 8.2.8.
Built and tested with:
- Google Mobile Ads SDK version 11.3.0.
- DT Exchange SDK version 8.2.8.
Version 8.2.7.0
- Verified compatibility with DT Exchange SDK version 8.2.7.
Built and tested with:
- Google Mobile Ads SDK version 11.2.0.
- DT Exchange SDK version 8.2.7.
Version 8.2.6.1
- Added
didFailToPresentWithError
callbacks in rewarded ad. - Added
IAAdDidExpire
delegate method in interstitial and rewarded ads. - Now requires minimum iOS version 12.0.
- Now requires Google Mobile Ads SDK version 11.0 or higher.
- Included
Info.plist
in the frameworks withinDTExchangeAdapter.xcframework
.
Built and tested with:
- Google Mobile Ads SDK version 11.0.1.
- DT Exchange SDK version 8.2.6.
Version 8.2.6.0
- Verified compatibility with DT Exchange SDK version 8.2.6.
- Removed the deprecated
willBackgroundApplication
delegate methods from the banner and interstitial ad implementations.
Built and tested with:
- Google Mobile Ads SDK version 10.14.0.
- DT Exchange SDK version 8.2.6.
Version 8.2.5.0
- Verified compatibility with DT Exchange SDK version 8.2.5.
Built and tested with:
- Google Mobile Ads SDK version 10.14.0.
- DT Exchange SDK version 8.2.5.
Version 8.2.4.0
- Verified compatibility with DT Exchange SDK version 8.2.4.
Built and tested with:
- Google Mobile Ads SDK version 10.9.0.
- DT Exchange SDK version 8.2.4.
Version 8.2.3.0
- Verified compatibility with DT Exchange SDK version 8.2.3.
Built and tested with:
- Google Mobile Ads SDK version 10.7.0.
- DT Exchange SDK version 8.2.3.
Version 8.2.2.0
- Verified compatibility with DT Exchange SDK version 8.2.2.
Built and tested with:
- Google Mobile Ads SDK version 10.5.0.
- DT Exchange SDK version 8.2.2.
Version 8.2.1.0
- Verified compatibility with DT Exchange SDK version 8.2.1.
- Removed support of the
armv7
architecture. - Now requires minimum iOS version 11.0.
- Now requires Google Mobile Ads SDK version 10.4.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 10.4.0.
- DT Exchange SDK version 8.2.1.
Version 8.2.0.0
- Verified compatibility with DT Exchange SDK version 8.2.0.
Built and tested with:
- Google Mobile Ads SDK version 10.2.0.
- DT Exchange SDK version 8.2.0.
Version 8.1.9.1
- Now requires Google Mobile Ads SDK version 10.0.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 10.0.0.
- DT Exchange SDK version 8.1.9.
Version 8.1.9.0
- Removed use of deprecated gender, birthday and location mediation APIs.
- Verified compatibility with DT Exchange SDK version 8.1.9.
Built and tested with:
- Google Mobile Ads SDK version 9.14.0.
- DT Exchange SDK version 8.1.9.
Version 8.1.7.0
- Verified compatibility with DT Exchange SDK version 8.1.7.
- Adapter is rebranded to "DT Exchange".
Built and tested with:
- Google Mobile Ads SDK version 9.13.0.
- DT Exchange SDK version 8.1.7.
Version 8.1.6.0
- Added support for passing
muteAudio
extra inGADMAdapterFyberExtras
class. - Updated the adapter to use the
didRewardUser
API. - Now requires Google Mobile Ads SDK version 9.8.0 or higher.
- Verified compatibility with Fyber Marketplace SDK version 8.1.6.
Built and tested with:
- Google Mobile Ads SDK version 9.11.0.
- Fyber Marketplace SDK version 8.1.6.
Version 8.1.5.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.5.
Built and tested with:
- Google Mobile Ads SDK version 9.5.0.
- Fyber Marketplace SDK version 8.1.5.
Version 8.1.4.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.4.
- Added support for the arm64 simulator architecture.
Built and tested with:
- Google Mobile Ads SDK version 9.1.0.
- Fyber Marketplace SDK version 8.1.4.
Version 8.1.3.1
- Verified compatibility with Google Mobile Ads SDK version 9.0.0.
- Now requires Google Mobile Ads SDK version 9.0.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 9.0.0.
- Fyber Marketplace SDK version 8.1.3.
Version 8.1.3.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.3.
Built and tested with:
- Google Mobile Ads SDK version 8.13.0.
- Fyber Marketplace SDK version 8.1.3.
Version 8.1.2.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.2.
Built and tested with:
- Google Mobile Ads SDK version 8.13.0.
- Fyber Marketplace SDK version 8.1.2.
Version 8.1.1.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.1.
Built and tested with:
- Google Mobile Ads SDK version 8.12.0.
- Fyber Marketplace SDK version 8.1.1.
Version 8.1.0.0
- Verified compatibility with Fyber Marketplace SDK version 8.1.0.
Built and tested with:
- Google Mobile Ads SDK version 8.12.0.
- Fyber Marketplace SDK version 8.1.0.
Version 8.0.0.0
- Verified compatibility with Fyber Marketplace SDK version 8.0.0.
Built and tested with:
- Google Mobile Ads SDK version 8.12.0.
- Fyber Marketplace SDK version 8.0.0.
Version 7.9.0.0
- Verified compatibility with Fyber Marketplace SDK version 7.9.0.
Built and tested with:
- Google Mobile Ads SDK version 8.11.0.
- Fyber Marketplace SDK version 7.9.0.
Version 7.8.9.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.9.
Built and tested with:
- Google Mobile Ads SDK version 8.10.0.
- Fyber Marketplace SDK version 7.8.9.
Version 7.8.8.1
- Moved ad event
didEndVideo
to rewarded ad callbackIAAdDidReward
.
Built and tested with:
- Google Mobile Ads SDK version 8.9.0.
- Fyber Marketplace SDK version 7.8.8.
Version 7.8.8.0
- Now requires minimum iOS version 10.0.
- Verified compatibility with Fyber Marketplace SDK version 7.8.8.
Built and tested with:
- Google Mobile Ads SDK version 8.9.0.
- Fyber Marketplace SDK version 7.8.8.
Version 7.8.7.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.7.
Built and tested with:
- Google Mobile Ads SDK version 8.8.0.
- Fyber Marketplace SDK version 7.8.7.
Version 7.8.6.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.6.
Built and tested with:
- Google Mobile Ads SDK version 8.5.0.
- Fyber Marketplace SDK version 7.8.6.
Version 7.8.5.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.5.
- Now requires building against Xcode 12.5 or higher.
Built and tested with:
- Google Mobile Ads SDK version 8.5.0.
- Fyber Marketplace SDK version 7.8.5.
Version 7.8.1.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.1.
- Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher.
- Added standardized adapter error codes and messages.
- Updated the adapter to use the
.xcframework
format.
Built and tested with:
- Google Mobile Ads SDK version 8.0.0.
- Fyber Marketplace SDK version 7.8.1.
Version 7.8.0.0
- Verified compatibility with Fyber Marketplace SDK version 7.8.0.
Built and tested with:
- Google Mobile Ads SDK version 7.69.0.
- Fyber Marketplace SDK version 7.8.0.
Version 7.7.3.0
- Verified compatibility with Fyber Marketplace SDK version 7.7.3.
- Now requires Google Mobile Ads SDK version 7.69.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 7.69.0.
- Fyber Marketplace SDK version 7.7.3.
Version 7.7.2.0
- Verified compatibility with Fyber Marketplace SDK version 7.7.2.
- Now requires Google Mobile Ads SDK version 7.67.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 7.67.0.
- Fyber Marketplace SDK version 7.7.2.
Version 7.7.1.0
- Verified compatibility with Fyber Marketplace SDK version 7.7.1.
- Now requires Google Mobile Ads SDK version 7.66.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 7.66.0.
- Fyber Marketplace SDK version 7.7.1.
Version 7.6.4.0
- Verified compatibility with Fyber Marketplace SDK version 7.6.4.
- Now requires Google Mobile Ads SDK version 7.65.0 or higher.
- Added GADMAdapterFyberExtras class, enabling publishers to pass keywords and userData to Fyber Marketplace SDK.
Built and tested with:
- Google Mobile Ads SDK version 7.65.0.
- Fyber Marketplace SDK version 7.6.4.
Version 7.6.3.0
- Verified compatibility with Fyber Marketplace SDK version 7.6.3.
Built and tested with:
- Google Mobile Ads SDK version 7.64.0.
- Fyber Marketplace SDK version 7.6.3.
Version 7.6.2.0
- Verified compatibility with Fyber Marketplace SDK version 7.6.2.
- Now requires Google Mobile Ads SDK version 7.64.0 or higher.
Built and tested with:
- Google Mobile Ads SDK version 7.64.0.
- Fyber Marketplace SDK version 7.6.2.
Version 7.6.0.0
- Verified compatibility with Fyber Marketplace SDK version 7.6.0.
- Now requires Google Mobile Ads SDK version 7.62.0 or higher.
- Updated the adapter to support inline adaptive banner requests.
- Added support for rewarded HTML.
- Added new reward callback: IAAdDidReward (for both rewarded video and rewarded HTML). IAVideoCompleted is no longer used for rewarding.
Built and tested with:
- Google Mobile Ads SDK version 7.62.0.
- Fyber Marketplace SDK version 7.6.0.
Version 7.5.6.1
- Temporarily removed Fyber Marketplace SDK-specific logging.
Built and tested with:
- Google Mobile Ads SDK version 7.60.0.
- Fyber Marketplace SDK version 7.5.6.
Version 7.5.6.0
- Verified compatibility with Fyber Marketplace SDK version 7.5.6.
- Updated the minimum required Google Mobile Ads SDK version to 7.60.0.
Built and tested with:
- Google Mobile Ads SDK version 7.60.0.
- Fyber Marketplace SDK version 7.5.6.
Version 7.5.5.0
- Verified compatibility with Fyber Marketplace SDK version 7.5.5.
- Updated the minimum required Google Mobile Ads SDK version to 7.59.0.
Built and tested with:
- Google Mobile Ads SDK version 7.59.0.
- Fyber Marketplace SDK version 7.5.5 .
Version 7.5.4.0
- Verified compatibility with Fyber Marketplace SDK version 7.5.4.
- Removed support for the i386 architecture.
Built and tested with:
- Google Mobile Ads SDK version 7.57.0.
- Fyber Marketplace SDK version 7.5.4.
Version 7.5.3.0
- Verified compatibility with Fyber Marketplace SDK version 7.5.3.
Built and tested with:
- Google Mobile Ads SDK version 7.55.0.
- Fyber Marketplace SDK version 7.5.3.
Version 7.5.1.0
- Verified compatibility with Fyber Marketplace SDK version 7.5.1.
- Fixed a crash that occurred when initializing the Fyber SDK.
Built and tested with:
- Google Mobile Ads SDK version 7.55.0.
- Fyber Marketplace SDK version 7.5.1.
Version 7.5.0.0 (Deprecated)
- This version has been removed. Please use version 7.5.1.0 or higher.
- Verified compatibility with Fyber Marketplace SDK version 7.5.0.
- Adapter will now initialize the Fyber SDK before making an ad request if the Fyber SDK has not been initialized yet.
Built and tested with:
- Google Mobile Ads SDK version 7.53.0.
- Fyber Marketplace SDK version 7.5.0.
Version 7.4.0.0
- Initial release!
- Added support for banner, interstitial and rewarded ad formats.
Built and tested with:
- Google Mobile Ads SDK version 7.52.0.
- Fyber Marketplace SDK version 7.4.0.