Integrating Tapjoy with Mediation

This guide is intended for publishers who want to use the Google Mobile Ads SDK to load and display ads from Tapjoy through waterfall mediation. It covers how to add Tapjoy ads to an ad unit's mediation configuration, and how to integrate the Tapjoy SDK and adapter into an iOS app.

Supported formats and platforms

The Ad Manager mediation adapter for Tapjoy has the following capabilities:

Formats
Banner
Interstitial
Rewarded
Native
Features
Adaptive banner
Automatic data collection

Requirements

• iOS deployment target of 8.0 or higher

• Latest Google Mobile Ads SDK

Step 1: Set up Tapjoy

Sign up or log in to your Tapjoy dashboard.

Add app

Add your app to the Tapjoy dashboard by going to the apps list on the top right and clicking the Add App button. You will be prompted to enter details about your app.

Fill out the form and click the Create Now button to add your app to Tapjoy dashboard.

You can skip the integration steps presented by Tapjoy and can move on to creating placements to be used with Ad Manager mediation.

Placement, virtual currency, and content

Placement

Navigate to Monetization > Placements and click the Create Placement button in the top right corner. Even if you have an existing placement, it's best to create a new one for Ad Manager, so it can be tracked and reported on separately.

Enter a Name for your placement, check the Mediation checkbox, and select AdMob from the drop down list. Click Create when done.

The Placement Name entered here will be used to set up your Ad Manager Ad Unit for mediation in the next section. "Ad Manager Mediation" has been used in this example, but you can call your placement whatever you like.

Note: Create a new placement for each Ad Manager interstitial or rewarded ad unit that you want to mediate to Tapjoy.

Virtual currency

Navigate to Monetization > Virtual Currency and click the Create Virtual Currency button in the top right corner.

Fill out the form and click Create now. Use NO_CALLBACK as the Callback URL. This ensures that the Tapjoy SDK avoids an unnecessary call to your server.

Note: The currency value and name will not be forwarded by the Tapjoy adapter. So, any generic values can be chosen for your Currency name and amount. See the Using Rewarded Ads section of this guide for more details.

Content

Navigate to Monetization > Create Content to create content to be shown with the placements.

For additional instructions on creating content, select the tab corresponding to your preferred ad format:

Interstitial

Click the Create button for the Interstitial Video content. Provide a Name for the content and choose iOS as the Platform. Select the virtual currency created earlier as the Virtual Currency. Select the Interstitial placement created earlier. Click the Save button at the bottom when finished to create your content.

Rewarded

Click the Create button for Rewarded Video content. Provide a Name for the content and choose iOS as the Platform. Select the virtual currency created earlier as the Virtual Currency. Select the Rewarded placement created earlier. Click the Save button at the bottom when finished to create your content.

Locate SDK Key

In addition to the Placement Name, you also need the SDK Key for setting up your Ad Manager ad unit.

Navigate to Settings > App Settings. Your SDK Key can be obtained from your App Info under the Application Platforms tab.

Locate reporting keys

You will need your Publisher OAuth Key and your Mediation Key. Your Publisher OAuth Key can be obtained in the same page under the API Keys tab.

Your Mediation Key can be obtained in the same page under the Mediation Keys tab under the Reporting API Key column. It will be labeled as "AdMob." Google Ad Manager publishers should still use this value, despite the name mismatch.

Step 2: Configure mediation settings for your Ad Manager ad unit

Sign in to your Ad Manager account. Navigate to Delivery > Yield groups and click the New yield group button.

Enter a unique Name for your yield group, set the Status to Active, select your Ad Format, and set the Inventory type to Mobile App. Under the Targeting > Inventory section, select the Ad Unit ID to which you want to add mediation.

Next, click the Add yield partner button.

If you already have a Yield partner for Tapjoy, you can simply select it. Otherwise, select Create a new yield partner.

Select Tapjoy as the Ad network and enter a unique Name. Enable Mediation and turn on Automatic data collection, and enter the Publisher OAuth Key and Mediation Key obtained in the previous section. You don't need to enter a Username and Password. Click Save when done.

Once the Yield partner is selected, choose Mobile SDK mediation as the Integration type, iOS as the Platform, and Active as the Status. Enter the SDK Key and the Placement Name obtained in the previous section and a Default CPM value.

Click Save at the bottom of the page when done.

Note: Automatic data collection takes a few days to gather data before it can accurately calculate a Dynamic CPM value for a mediation network. Once the eCPM can be calculated, it will be automatically updated on your behalf.

Using rewarded ads

In the settings for your rewarded ad unit, provide values for the reward amount and reward type. Then, to ensure you provide the same reward to the user no matter which ad network is served, check the Override reward settings from third-party ad networks when using mediation box.

If you don't apply this setting, the Tapjoy adapter defaults to a reward of type "" (empty string) with a value of 1. The Tapjoy SDK does not provide specific reward values for its rewarded ads.

Step 3: Import the Tapjoy SDK and adapter

Using CocoaPods (recommended)

• Add the following line to your project's Podfile:

  pod 'GoogleMobileAdsMediationTapjoy'
  

• From the command line run:

  pod install --repo-update

Manual integration

• Download the latest version of the Tapjoy SDK, and link Tapjoy.embeddedframework in your project.

• Download the latest version of the Tapjoy adapter from the download link in the Changelog and link TapjoyAdapter.framework in your project.

Step 4: Additional code required

No additional code is required for Tapjoy integration.

Step 5: Test your implementation

Test ads can be enabled on the Tapjoy dashboard under Settings > App Settings > Test Devices. Create a new test device using the device's Advertising ID as shown below:

To get your device's advertising ID, add the following code in your app. Make sure to import AdSupport framework into your app before using the code below.

Swift

let advertisingId: String = ASIdentifierManager.shared().advertisingIdentifier.uuidString
print("Advertising ID: \(advertisingId)")

Objective-C

NSString *advertisingId = [[[ASIdentifierManager sharedManager] advertisingIdentifier] UUIDString];
NSLog(@"Advertising ID: %@", advertisingId);

Next, modify the content you created earlier.

To modify your content, first navigate to Monetization > Placements and click the User Initiated tab. Next, select the drop down for the content you want to edit, and choose Edit.

Under the content's Basic section, check the Only for Test Devices checkbox. Then click Save at the bottom of the page. That's it! You now have a working mediation integration with Tapjoy.

Optional steps

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.

The section below shows you how to enable or disable personalized ads for Tapjoy.

In Tapjoy SDK version 11.12.2, Tapjoy added a user consent API. The following sample code sets user consent to "1" on the Tapjoy SDK. If you choose to call this method, it is recommended that you do so prior to requesting ads via the Google Mobile Ads SDK.

Note: Your app must reference Tapjoy adapter 11.12.2.0 or higher and Tapjoy SDK 11.12.2 or higher to use the code below.

#import <Tapjoy/Tapjoy.h>
// ...

[Tapjoy setUserConsent:@"1"]; // user does consent

See Tapjoy's Release Notes for more information.

Network-specific parameters

The Tapjoy adapter supports additional request parameter which can be passed to the adapter using the GADMTapjoyExtras class. This class includes the following property:

• debugEnabled - Set this to YES to enable logging in Tapjoy SDK for debug mode.

Here's a code example of how to set this parameter at ad request:

Swift

let request = GAMRequest()
let extras = GADMTapjoyExtras()
extras.debugEnabled = true
request.register(extras)

Objective-C

GAMRequest *request = [GAMRequest request];
GADMTapjoyExtras *extras = [[GADMTapjoyExtras alloc] init];
extras.debugEnabled = YES;
[request registerAdNetworkExtras:extras];

Verify your adapter and SDK versions

To log the adapter and SDK versions, use the following code snippet:

Class<GADMediationAdapter> adapterClass = NSClassFromString(@"GADMediationAdapterTapjoy");
if (adapterClass != nil) {
  GADVersionNumber adapterVersion = [adapterClass version];
  GADVersionNumber sdkVersion = [adapterClass adSDKVersion];
  NSLog(@"Adapter version: %ld.%ld.%ld.%ld",
        adapterVersion.majorVersion,
        adapterVersion.minorVersion,
        adapterVersion.patchVersion / 100,
        adapterVersion.patchVersion % 100);
  NSLog(@"SDK version: %ld.%ld.%ld",
        sdkVersion.majorVersion,
        sdkVersion.minorVersion,
        sdkVersion.patchVersion);
}

Logging the adapter version in Swift is not possible since the dynamic runtime feature does not exist in Swift, making it infeasible to dynamically create the class from the class name. If this is needed in Swift, it needs to be written in Objective-C and imported using a bridging header.

Error codes

If the adapter fails to receive an ad from Tapjoy, publishers can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following classes:

Format	Class name
Interstitial	GADMAdapterTapjoy
Rewarded	GADMAdapterTapjoy

Here are the codes and accompanying messages thrown by the Tapjoy adapter when an ad fails to load:

Error code	Reason
101	Tapjoy server parameters configured in the Ad Manager UI are missing/invalid.
102	Tapjoy SDK failed to initialize.
103	The Tapjoy adapter does not support the ad format being requested.
104	Tapjoy sent a successful load callback but no content was available.
105	An ad is already loaded for this network configuration.
106	Tapjoy SDK returned a video failure error callback.

Tapjoy iOS Mediation Adapter Changelog

Version 12.9.0.0 (In progress)

• Verified compatibility with Tapjoy SDK 12.9.0.
• Now requires minimum iOS version 10.0.

Build and tested with

• Google Mobile Ads SDK version 8.13.0.
• Tapjoy SDK version 12.9.0.

Version 12.8.1.0

• Verified compatibility with Tapjoy SDK 12.8.1.

Build and tested with

• Google Mobile Ads SDK version 8.5.0.
• Tapjoy SDK version 12.8.1.

Version 12.8.0.1

• Relaxed dependency to Google Mobile Ads SDK version 8.0.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 8.4.0.
• Tapjoy SDK version 12.8.0.

Version 12.8.0.0

• Updated the adapter to use the .xcframework format.
• Verified compatibility with Tapjoy SDK 12.8.0.
• Now requires Google Mobile Ads SDK version 8.2.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 8.2.0.
• Tapjoy SDK version 12.8.0.

Version 12.7.1.0

• Verified compatibility with Tapjoy SDK 12.7.1.
• Now requires Google Mobile Ads SDK version 7.67.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 7.67.0.
• Tapjoy SDK version 12.7.1.

Version 12.7.0.0

• Verified compatibility with Tapjoy SDK 12.7.0.
• Now requires Google Mobile Ads SDK version 7.65.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 7.65.0.
• Tapjoy SDK version 12.7.0.

Version 12.6.1.0

• Verified compatibility with Tapjoy SDK 12.6.1.

Build and tested with

• Google Mobile Ads SDK version 7.61.0.
• Tapjoy SDK version 12.6.1.

Version 12.6.0.0

• Verified compatibility with Tapjoy SDK 12.6.0.
• Now requires Google Mobile Ads SDK version 7.61.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 7.61.0.
• Tapjoy SDK version 12.6.0.

Version 12.4.2.2

• Updated the adapter to be more consistent in forwarding ad event callbacks:
  • Interstitial and rewarded ads now record clicks.
  • Interstitial ads now forward interstitialWillLeaveApplication: when clicked.
  • Rewarded ads now forward willDismissFullScreenView: when dismissed.
• Added standardized adapter error codes and messages.
• Now requires Google Mobile Ads SDK version 7.60.0 or higher.

Build and tested with

• Google Mobile Ads SDK version 7.60.0.
• Tapjoy SDK version 12.4.2.

Version 12.4.2.1

• Adapter now fails if the request to Tapjoy returns without any available content.
• Removed support for the i386 architecture.

Build and tested with

• Google Mobile Ads SDK version 7.57.0.
• Tapjoy SDK version 12.4.2.

Version 12.4.2.0

• Verified compatibility with Tapjoy SDK 12.4.2.
• Now requires minimum iOS version 9.0.

Build and tested with

• Google Mobile Ads SDK version 7.55.0.
• Tapjoy SDK version 12.4.2.

Version 12.4.1.0

• Verified compatibility with Tapjoy SDK 12.4.1.

Build and tested with

• Google Mobile Ads SDK version 7.53.1.
• Tapjoy SDK version 12.4.1.

Version 12.4.0.0

• Verified compatibility with Tapjoy SDK 12.4.0.

Build and tested with

• Google Mobile Ads SDK version 7.53.1.
• Tapjoy SDK version 12.4.0.

Version 12.3.4.0

• Verified compatibility with Tapjoy SDK 12.3.4.

Build and tested with

• Google Mobile Ads SDK version 7.52.0.
• Tapjoy SDK version 12.3.4.

Version 12.3.3.0

• Verified compatibility with Tapjoy SDK 12.3.3.

Version 12.3.2.0

• Verified compatibility with Tapjoy SDK 12.3.2.

Version 12.3.1.0

• Verified compatibility with Tapjoy SDK 12.3.1.
• Added bidding capability to the adapter for interstitial and rewarded ads.

Version 12.2.1.0

• Verified compatibility with Tapjoy SDK 12.2.1.
• Updated the adapter to use the new rewarded API.
• Now requires Google Mobile Ads SDK version 7.42.2 or higher.

Version 12.2.0.0

• Verified compatibility with Tapjoy SDK 12.2.0.

Version 12.1.0.0

• Verified compatibility with Tapjoy SDK 12.1.0.

Version 12.0.0.0

• Verified compatibility with Tapjoy SDK 12.0.0.
• Added adapterDidCompletePlayingRewardBasedVideoAd: callback to the adapter.

Version 11.12.2.0

• Verified compatibility with Tapjoy SDK 11.12.2.

Version 11.12.1.0

• Verified compatibility with Tapjoy SDK 11.12.1.

Version 11.12.0.0

• Verified compatibility with Tapjoy SDK 11.12.0.

Version 11.11.1.0

• Verified compatibility with Tapjoy SDK 11.11.1.

Version 11.11.0.0

• Verified compatibility with Tapjoy SDK 11.11.0.

Version 11.10.2.0

• Updated the default reward amount to 1.
• Removed the support for armv7s architecture.
• Verified compatibility with Tapjoy SDK 11.10.2.

Version 11.10.1.0

• Verified compatibility with Tapjoy SDK 11.10.1.

Version 11.10.0.0

• Verified compatibility with Tapjoy SDK 11.10.0.

Version 11.9.1.0

• Initial release. Supports reward-based video ads and interstitial ads.