Versions Compared

Version Old Version 8 New Version 9
Changes made by

Robert Apikyan

Robert Apikyan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

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 will be 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.

Go into production

For going into production you will need to use your ids:

  • Remove the methods R89SDK.setDebug() and addTestingSingleTagData() .

  • Change the App ID in the manifest for the production one.

  • Change the GADApplicationIdentifier 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.setLogLevel(LogLevels.DEBUG) but not needed.

How does it work?

We monitor your app to determine the active route/screen at any given moment. For each route/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.