Do iOS Get Started all the way until finishing step 3
Add the Initialization code for the SDK
Register all the app UIViewControllers
to the SDK
Add the tagged Wrappers, and tagged Buttons using the accessabilityLabel
Note the transition events
Add the testing Single Data
Test everything is working
Change everything to production code
Your app is now prepared for monetization with us.
We require the SDK to be initialized only once and as early as possible It can be done either inside your |
The first recommended place to initialize the SDK is the UIApplicationDelegate.application(_:didFinishLaunchingWithOptions:)
method.
import UIKit import R89SDK @main class AppDelegate: UIResponder, UIApplicationDelegate { func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { // This is for testing purposes, remove it on prod R89SDK.shared.setLogLevel(level: LogLevels.debug) // This is for testing purposes, remove it on prod R89SDK.shared.setDebug() addTestingSingleTagData() /* This is a later step */ R89SDK.shared.initialize( publisherId: "TestPublisherID", appId: "TestAppId", singleLine: true, publisherInitializationEvents: nil) return true } } |
Your |
This |
Use R89SDK.shared.registerUIViewController()
method and register each UIViewController
instance in your app that represents a screen. This helps the R89SDK to track the user’s navigation and screen transitions in the app.
import UIKit import R89SDK class MainViewController: UIViewController { ... override func viewDidLoad() { super.viewDidLoad() ... R89SDK.shared.registerUIViewController(uiViewController: self) } ... } |
Tagged Wrappers |
Check iOS Creating a wrapper if you want to know more details on how to create a normal wrapper.
Events can trigger other formats, right now the single tag supports:
Transitions events are detected by the single tag automatically after initialization. They happen when an activity or fragment is started from other activity or fragment.
Button Presses when a button is pressed, this works They are detected by adding the android:tag
attribute to the button.
In this example an interstitial would be triggered when we see the |
In this example an interstitial would be triggered when the button is pressed and when the interstitial is closed the |
Go back to the UIViewController
class where we initialized the code, we are going to test all the transitions, tagged wrappers and tagged buttons you have placed in the app.
Before initialization method we called addTestingSingleTagData()
that uses the SingleTagConfigBuilder
to create the testing data needed for debugging the sdk.
More info in → https://refinery89.atlassian.net/wiki/x/EgBWTw
When using the |
func addTestingSingleTagData(){ SingleTagConfigBuilder.shared.addAdScreenBuilder(isFragment:false,screenName: "InitialScreenViewController") .addBanner(wrapperTag: "banner_tag", getAllWithTag: true, wrapperRelativePositionInside: true, wrapperRelativePositionAfter: false) .addInterstitial(eventsToTrackTo: nil, eventsToTrackButton: "button_tag") .addInterstitial(eventsToTrackTo: "SecondSCreenViewController", eventsToTrackButton: nil) } |
This step is for testing purposes and you are only going to see test ads when using this approach, but this is very helpful to us if you provide this peace of code to tell us where you want to place the ads. Later when in production, this code have been removed and you have hopefully added flexible tagged wrappers and tagged all the button as possible so we can change your ad slots from the server without the need of updating the app. |
For going into production you will need to use you ids:
Remove the methods R89SDK.shared.setDebug()
and addTestingSingleTagData()
Change the App id in the info.plist for the production one
Change the appId
and publisherId
in the initialization method for the production ones
it’s also recommended to remove R89SDK.shared.setLogLevel(LogLevels.DEBUG)
but not needed
We monitor your app to determine the active screen at any given moment. For each screen, we maintain a record of events and tags that you have supplied, enabling us to place ads in those tagged views or during specific transitions and events from the record.
We have the capability to display Display ads on a tagged wrappers or trigger an Interstitial ads during the transition from one screen to another or in button press. And many other things All of this can be achieved without the need of coding specific triggers or manually adding the ad to the view. It is as simple as initializing the SDK.