Prerequisites

  1. https://refinery89.atlassian.net/wiki/x/A4DVSQ

  2. https://refinery89.atlassian.net/wiki/x/BgDOSQ

You can show interstitial in many different places but we are going to discuss not where but how to show it. But first let’s explain a crucial concept.

After Interstitial

This is not passed as a separated object like the other Events because is mandatory to handle what happens after an Interstitial is closed. This is invoked in the SDK when:

Load, wait, then Show the Ad on Event

This way is much more efficient since the show is immediate as the user performs the action.

So consider a scenario where a button click triggers an Interstitial and, subsequently, the NewActivity is launched from MainActivity.

Load

Load then wait for the user to take an action on your app

#MainActivity.kt->onCreate()
val interstitialConfigId = ConfigBuilder.INTERSTITIAL_TEST_R89_CONFIG_ID
val activityToShowOver = this

var interstitialId = RefineryAdFactory.createInterstitial(
interstitialConfigId, 
activityToShowOver, 
afterInterstitial = {
    // Here you could load the next activity or fragment. Basically recover app flow
    Log.d("Interstitial", "After Interstitial")
    //Example
    val newActivityIntent = Intent(this, NewActivity::class.java)
    startActivity(newActivityIntent)
})

Show On Button Press

Some event takes place in you app, such as a button press, tab change or opening a link, screen transition.

If the Interstitial hasn’t Loaded yet or failed to load when you call show() method, afterInterstitial event will be called to recover app flow.

#MainActivity.kt->onCreate()
//Example of a button press
findViewById<Button>(<YOUR_BUTTON_ID>).setOnClickListener
{
    RefineryAdFactory.show(interstitialId)
}

Load & Show on Event

This will increase the time it takes to show the interstitial and then recover app flow.

Because its making the Ad Request when the user takes the action. You should use the previous approach where we make the request and store the ad ID for instant showing it when the user performs the actions.

This is how we use Interstitial we use in Demos because it’s pretty good at showing that it works but nothing more

#MainActivity.kt->onCreate()
findVIewById<Button>(<YOUR_BUTTON_ID>).setOnclickListener
{
  createInterstitial()
}

#MainActivity.kt

private fun createInterstitial()
{
	val interstitialAdId = ConfigBuilder.INTERSTITIAL_TEST_R89_CONFIG_ID
	val lifecycleEvents = object : InterstitialEventListener
	{
		/* 
		 * We need to call show on the onLoaded event and on the OnFailedToLoad event,
		 * this is to show the ad in both cases so the afterInterstitial event is called
		 */
		override fun onLoaded()
		{
			RefineryAdFactory.show(interstitialId)
		}

		override fun onFailedToLoad(error: R89LoadError)
		{
			RefineryAdFactory.show(interstitialId)
		}
		....
	}

	interstitialId = RefineryAdFactory.createInterstitial(
		interstitialAdId, this,
		afterInterstitial = {
			Log.d("Interstitial", "After Interstitial")
		},
		lifecycleCallbacks = lifecycleEvents
	)

}

Lifecycle Events

You can subscribe to these events with the same method but passing a new object as a parameter. Details about this object can be found in the Reference.

OnClose is not present because we have an after interstitial event that is mandatory to pass as a parameter and holds the same functionality that OnClose with special cases.