Prerequisites

• Do Android Get Started all the way until finishing step 3

Step Summary

1. Add the Initialization code.

2. Add the Application class to the Manifest (in case you are using it)

3. Add the Tagged Wrappers, Tagged Buttons and

4. Note the Transitions Events

5. Add the testing Single Data

6. Test everything is working

7. Change everything to production code

8. Your app is now prepared for monetization with us.

Initialize the SDK

...

Then add this application class to the manifest you already had from the Android Get Started.

The code for adding the application is the following

...

Tagged wrappers

Tagged Wrappers are the container inside which the ads will show, they are normal wrappers with the android:tag attribute set. You need to add as many as you can, remember that placing a tagged wrapper does not mean we need to use it.

Check both https://refinery89.atlassian.net/wiki/x/A4DcSQ and Tagged Wrappers for more information

We recommend you add the wrappers using XML Views, since it’s easier than creating them using code, so something like this:

...

Events

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.

...

Example of transition:

class MainActivity : AppCompatActivity()
{
	override fun onCreate(savedInstanceState: Bundle?)
	{
		super.onCreate(savedInstanceState)
		setContentView(R.layout.activity_main_auto)
		
		findViewById<Button>(R.id.goToNewsPost).setOnClickListener {
			val intent = Intent(this, NewsPostDetailActivity::class.java).apply {
				putExtra("newsPostData", newPostData)
			}
			startActivity(intent)
		}
	}
}

...

Example of button press:

with this button code

# activity_main.xml
...
<Button
    android:id="@+id/play_video_trailer"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:tag="play_video_trailer_tag" />
...

...

...

Adding testing single tag data

Go back to the application class that was created at the start of the guide, we are going to test all the transitiontransitions, 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 → How to test Single Tag Implementation

fun addTestingSingleTagData()
{
    //Add a Screen that is an Activity, the screenName you can get it by logging this in you code -> 
    // MainActivity::class.simpleName -> MainActivity
    // NewsPostDetailActivity::class.simpleName -> NewsPostDetailActivity
    
    val screenBuilder = SingleTagConfigBuilder.addAdScreenBuilder(
        isFragment = false, 
        screenName = "MainActivity"
    )
    
    // Add a banner format to the wrapper with the tag main_activity_bottom_ad_container
    screenBuilder.addBanner(
      wrapperTag = "main_activity_bottom_ad_container", 
      getAllWithTag = false, /* Only the first tagged wrapper in "MainActivity" with this tag will be used for this banner*/
      wrapperRelativePositionInside = true /* the ad will be placed inside of the wrapper */
    )
    
    /* trigger interstitial when we transition from "MainActivity" (ScreenBuilder.screenName) TO NewsPostDetailActivity */
    screenBuilder.addInterstitial(
        eventsToTrackTo = "NewsPostDetailActivity", 
        eventsToTrackButton = null
    )
    
    /* trigger an interstitial when a button with this tag is pressed in "MainActivity" (ScreenBuilder.screenName) */
    screenBuilder.addInterstitial(
        eventsToTrackTo = null
        eventsToTrackButton = "play_video_trailer_tag" 
    )
}

Go into production

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

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

• Change the Google app App id in the manifest 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 works?

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.

...