Prerequisites

• Use XCode 15.2 or higher

• Target iOS 12.0 or higher

Step Summary

1. Import the Library

2. Add Info.plist App id

3. Add Info.plist Ad networks

4. Add Info.plist ATT Configuration

5. Background Task Configuration

6. Continue with Implementation type

1. Import the Mobile Ads SDK

Cocoapods

The simplest way to import the SDK into an iOS project is to use CocoaPods.

Open your project's Podfile and add this line to your app's target:

Then from the command line run:

If you're new to CocoaPods, see their official documentation for info on how to create and use Podfiles.

2. Add Info.plist Google App Id

Add the App Id to your info.plist file.

3. Add Info.plist Ad Networks

Add the Ad Networks to your Info.plist file.

4. Add info.plist ATT configuration

Since iOS 14 Apple introduced the Apple Tracking Transparency framework, which requires that every app needs to disclose what tracking data they collect.

For the R89SDK, after showing the Consent Management Platform (CMP) we will automatically display the ATT permission dialog.

To configure the ATT request dialog in your app add the NSUserTrackingUsageDescription to the app’s Info.plist.

Use the same description text or one that better fits your app's purpose.

5. Background task configuration

With the purpose of providing better analytics the R89SDK needs to track the advertisement session while the application is in the background. It internally uses the BgTaskScheduler and BGAppRefreshTask from the iOS framework. Before enabling the background modes add the “Background Modes“ capability to your project.

Open

After adding the “Background Modes“ capability enable both “Background fetch“ and “Background processing“ modes.

Open

Next, in your Info.plist, add the task identifier com.refinery89.background under the BGTaskSchedulerPermittedIdentifiers key. Here's how it should look:

6. Choose an Implementation Type

Single Tag Implementation

This is what you are looking for? continue here → https://refinery89.atlassian.net/wiki/x/HgCVTQ

This Implementation provides a way that with minimal code you can remotely control where and how to show the ad inventory.
You will have full remote control over Ad Inventory configurations and with the addition of tags to your wrapper, you will have where you show the inventory.

This is the easiest monetization setup, because all configurations for the Units are done in the Remote Server, you just need to add the tags on the “white spaces of your app” where you might or might not place ads, so no need to manually request request the ads in those places.

This option is recommended under the following circumstances:

• You App is native and you are able to add tags to your views

• Wants to Disable and enable Inventory slots without updating the application.

• Wants tos Edit the ad units remotely over the web without updating the application.

• Wants to Change Formats, slot place, sizes, etc.

Manual Implementation

This is what you are looking for? continue here → https://refinery89.atlassian.net/wiki/x/FoCaTQ

Manual configuration means that you have remote control of General Ad Settings over the web or our tech support, but you need to add the ads manually, so instead of just placing the tags you need to create a wrapper and use it to do a request for the format that you want.

This option is recommended under the following circumstances:

• Wants control over the logic of showing the Inventory.

• You are using a framework that we don’t support but you can use native android code.

• You have a web-application but you are not using our monetization in your web and want to place ads natively

Webview Implementation

This is what you are looking for? continue here → https://refinery89.atlassian.net/wiki/x/MgCLTQ

If your application is a web-application and your monetization is already in place in the web through our Header Tag or Adsense. It’s mandatory by google to have a native cmp when selling ad inventory on apps, use our sdk for sending consent from the phone to the cmp in the web view, this will improve performance metrics of the ad inventory in the web-application since now instead of web inventory it will be targeted as app.

This option is recommended under the following circumstances:

• You have a web-application and you are using our web monetization tag and CMP

• You need to send consent data to you web monetization solution (only our header bidding or adsense)

• You need to properly target the ads inside the webview

• You need to show ads both inside the webview and outside (combine with manual)

Comparison table