Overview

What are the main components of InMobi LTVP?

InMobi LTVP contains 3 main components:
• Insights: This component provides detailed analytics and allows you to view reports on application metrics such as users, purchase behaviour, revenue, and engagement.
• Segments: This component allows you to segment users based on behaviour such as time spent, purchase history, country, carrier and so on.
• Actions: This component allows you to apply monetization and engagement actions by user.

What are Insights and how do they work?

The Insights component allows you to view user, revenue, and engagement metrics. You can also view reports on custom events.

What are Segments and how do they work?

The Segments component allows you to set up groups of users based on the following characteristics:
• User Behaviour Characteristics: such as time spent and purchase history
• Demographic Characteristics: such as country, carrier, device, and so on. Segments then serve as targeting parameter in actions.

What are Actions and how do they work?

The Actions component is used for creating and applying actions on particular user segments. Actions are also known as the insight driven “campaigns” taken by developers on particular user segments to increase monetization, and engagement levels. They allow for quick set up and launch of campaigns by a specific user (Virtual goods sale, reward, cross promote or display ads).

Can I use InMobi LTVP with third party monetization (mediation/incentivized) platforms?

Absolutely, InMobi LTVP can be used with the power of other mediation/incentivized platforms by using custom actions.

Integration

What is the Integration effort required?

Integration requires a one-time set up process. This process has been divided into 3 steps for easier understanding:
• Set up application and slots on portal
• Download and Integrate with SDK (for both events and actions)
• Test the events and actions using test applications

How do I set up apps and slots on the portal?

Application setup is very simple – Provide the application name, URL and OS platform. Slots are placement name/size in the developer’s application where actions are to be displayed. These slots are independent of slots created in other platforms.

How do I Integrate with the SDK?

SDK Integration is a two-step process:
• Integrate Events: Call events API for relevant events such as session, purchase and so on in the application.
• Integrate Action: Call actions API with slot ID in different places in the application. For more information, see the Integration Guides / documents.

Do I need to download any other SDKs/components to get it working?

The InMobi LTVP SDK bundle includes the following:
• InMobiLTVP-1.0.0.jar: This library contains the LTVP insights code
• InMobiCommons-3.6.0.jar: This library contains code for authentication, logging and so on.
• InMobiAdNetwork-3.6.0.jar: This library contains code for rendering LTVP actions

Docs folder – This folder contains Java docs for the API. You will need to include all 3 jars in your libs folder. The steps for iOS are similar.

How do I test the Integration steps?

The following steps are recommended for testing integration:
• Registering: Register a test application in the system and use the AppID for test integration.
• Testing: Test events, segments, and actions for the test app – This testing is actually done in production systems and reflects the actual performance.

Does InMobi LTVP collect data in the background while the app is running?

No. All data collection happens when the developer calls APIs in InMobi LTVP. This makes it much easier to test the integration and guarantees that InMobi LTVP will never impact your application by collecting data at an inopportune time.

Is the app data collected secure? Is this PII?

Data collected is only exposed in reporting at an aggregate level. Actions targeting is not traceable to the actual user and this is not considered PII. Also, data collected for each application is never shared with any 3rd party.

What happens when the user does not have a network connection?

InMobi LTVP requires a network connection for uploading to data collection servers. If users do not have a network service when running an application, then all data is stored in a queue for uploading later. If the queue fills, InMobi LTVP stops collecting data until the queue is cleared.

Is it possible to delete or reset data?

After data is received and processed, it cannot be selectively deleted. Hence, it is recommended that you create two application ID’s; one for development and one for production. This will keep your development and testing data separate.

How often is the data under Segments refreshed?

The segmentation engine is scheduled to run every few minutes. This is sufficient for current set of action use cases.

Is there a refresh rate for the “serve ad” action? What about the other actions?

The refresh rate will apply only in the case of banner ads. Interstitial ads and other actions do not have a refresh rate.

If I have set up multiple Actions for a slot, which one will get rendered?

If there are multiple Actions that are applicable for a given slot, then only one of them is selected, randomly. To ensure that only a specific Action is served for a given slot, bind only the desired Action to the slotID.

How do I use InMobi Display Ad action? Do I need a separate integration with InMobi network/ mediation?

InMobi Display Ad allows for showing display ads from InMobi to your users. This action type does not require any separate integration with InMobi network.

How can I use external monetization solutions (mediation, offerwalls)?

You can use Custom Action specifically for external monetization solution. After you get a callback from custom action with appropriate instruction in the handler code, you can call the desired external monetization solution.

How is an Action rendered?

InMobi LTVP supports 2 kinds of Actions:
• Interstitial: An interstitial action is rendered as a full-screen offer (usually best shown during paused app state such as level complete, main menu and so on). The lifecycle allows the developer to separate the call load and show. After the showAction is called, the action takes over webview to show the action. All actions types (Virtual Goods Sale, Display Ad, Rewards, Announcement, and Cross Promote) are supported.
• Banner: A banner action is rendered as a banner offer (usually best shown anytime during app usage such as top or bottom bar). The lifecycle allows for single load. The action is then presented to the developer to inject into the appropriate place in app (top, bottom). Currently, only Display Ad action is supported in banner.

Can I reuse Segments/Actions across apps?

No. In the current release, Segments and Actions are created uniquely for each app. Although, In the future we plan to allow for creating and reusing templates both within and across apps.

What are the integration best practices that should be followed?

These are some of the suggested best practices:
• Data collection should never happen in a loop. This can cause excessive amounts of data to be stored and uploaded.
• Only one Session should be used inside an application. If multiple objects or multiple keys are used, then there is a risk of sessions clashing each other.
• All sessions should be closed. It is a good practice to have a single application exit point, and close the session there.