Explore More(Beta)
Overview
Explore More enhances user engagement by providing seamless content discovery. When users interact with your chosen trigger action, a full-screen webview opens with additional content. As users navigate back, they're presented with personalized recommendations, creating an immersive browsing experience that keeps them engaged longer.
Basic requirementsBefore you start, make sure that you meet the basic requirements:
- You are using Android Classic as your integration method.
- You are using Taboola SDK
4.0.22or higher.- Your Taboola Account Manager has instructed you to go ahead with the Taboola SDK integration.
Need a hand? Please reach out to your Taboola Account Manager.
First steps
Complete the Basic Integration steps first.
Enable the feature
Create Explore More using the TBLClassicPage instance that you have already created.
ImportantOnly one instance of Explore More can be initialized per page and opened once.
page.initExploreMore(
context,
tblExploreMoreListener,
placementName,
mode,
customSegment);page.initExploreMore(
context,
tblExploreMoreListener,
placementName,
mode,
customSegment)
Parameters
context- The Android Context.tblExploreMoreListener- A class instance that listens for Taboola SDK Explore More events (i.e. implements theTBLExploreMoreClassicListener).placementName- The placement name, as provided by Taboola - e.g."Feed - Explore more".mode- The UI Mode ID of the placement, as provided by Taboola - e.g."thumbs-feed-01".customSegment- Optional. Custom segment for loading Explore More content. See Custom Segments.
Manual trigger
To show Explore More, call showExploreMore on your TBLClassicPage instance. You choose when to display it.
page.showExploreMore(fragmentManager);page.showExploreMore(fragmentManager)
Parameters
fragmentManager- The Android FragmentManager.
ImportantExplore More can only be shown once per
TBLClassicPageinstance.
Automatic trigger
Instead of triggering Explore More manually, you can configure it to display automatically when the user presses the back button. This is useful for root screens where pressing back would normally exit the app. When the back button trigger is enabled, the first back press shows Explore More, and the second back press performs the default action.
ImportantThe back button trigger only works on root screens. If the activity is not a root activity or has fragments in the back stack, the trigger will not be set.
page.setExploreMoreBackButtonTrigger(
activity,
onBackPressedDispatcher,
viewLifecycleOwner,
fragmentManager);page.setExploreMoreBackButtonTrigger(
activity,
onBackPressedDispatcher,
viewLifecycleOwner,
fragmentManager)
Parameters
activity- The Android Activity instance.onBackPressedDispatcher- The OnBackPressedDispatcher from the activity.viewLifecycleOwner- The LifecycleOwner for the view.fragmentManager- The Android FragmentManager.
ImportantUse either the manual or automatic trigger, not both.
Event handling
TBLExploreMoreClassicListener
To get notified about Explore More events, implement TBLExploreMoreClassicListener:
void exploreMoreDidOpen() {
// Called when Explore More is successfully opened
}
void exploreMoreDidClose() {
// Called when Explore More is closing
}
void exploreMoreDidReceiveError(String error) {
// Handle error here
}fun exploreMoreDidOpen() {
// Called when Explore More is successfully opened
}
fun exploreMoreDidClose() {
// Called when Explore More is closing
}
fun exploreMoreDidReceiveError(error: String) {
// Handle error here
}While reading the documentation, take a look at our Sample App.
Updated about 9 hours ago
