Skip to main content
Gainsight Inc.

Instrument your Mobile Application with Product Mapper

ATTENTION: Documentation Updates are in Process
We are in the process of updating the screenshots, GIFs, and content to match the latest UX based on the Horizon Experience’s new look and feel. To learn more about the Horizon Experience in Gainsight PX, click here.

This article explains how to instrument your mobile application with Gainsight Product Mapper.

Overview

The Product Mapper feature allows you to model your application using a simple and powerful hierarchical tree structure that is designed to help you quickly and effectively map your application features and associate the tracked user events into the corresponding features and modules with zero codings. After the mapping is completed, you’ll be able to monitor account and user activity in your application, and see for example which features are more heavily used or which ones they’re unaware of.

Anatomy of Product Mapper

The Gainsight PX Product Mapper is composed of three elements; Modules, Features, and Rules.

Module

A Module in Product Mapper represents a section in your mobile application. Each section can have sub-sections or pages. For example, an e-commerce application can have modules like Home, Products, Sign in, Sign up, and so on. The Products module can further have sub-modules like Electronic equipment, home appliances, Kitchen needs, and so on. A module consists of pages in your mobile application. 

Feature

A Feature represents a page in your mobile application. A page or group of pages can be part of a module. For example, Sign in, Sign up, About us, can all be part of the Home module. You can create rules to track page views. Gainsight PX supports two kinds of rules for mobile applications:

  • Screen rule: This rule is used to track the number of visits for a page (feature) in your mobile application. You can also track which user visited.  
  • Custom event rule: This rule tracks events fired via API. 

Instrumentation with Product Mapper

This section explains how to create modules and features to the Product Mapper for your mobile application. You can modify or rearrange the modules or features, as required. A sample mobile application is used to demonstrate creating modules and features.  

Create Modules

This subsection explains the process of creating Modules in Gainsight PX. Once you create modules, you can add features under the modules.

To create Modules:

  1. Click the Product Mapper icon from the left pane.

1..png

  1. Select the mobile channel.

2..png

  1. Select the required mobile product.

3..png

  1. Click Create module or select the Module option from the + New menu.

4..png

  1. Enter a name for the module and hit the enter key. In the following image, a new module called Mobile is created.

5..png

Create Features

This subsection explains the process of creating Features in Gainsight PX. You can create a Feature under a module or keep it independent under your product tree.

To create Features:

  1. To create a feature under a module, right-click the required module, and select Feature

6..png

The new feature is created under the selected module. To create a feature independently, select the Feature option from the + New menu.   

  1. (Optional) Click Reorder and drag a feature or module, to change its position. 

7..png

Similarly, create modules and features as required. 

Create Screen Rule

This section explains how to create a Screen rule. Once you create features for your mobile page, you must create screen rules for tracking page views.

To create screen rule:

  1. Launch your mobile application (that has Gainsight mobile SDK).
  2. Navigate to the required screen to be tracked.
  3. Place both your thumbs on the screen for several seconds until you receive the Screen name and the screen class message.

8..png

  1. Select the required feature.
  2. Right-click the feature and select Screen rule. You can also click the Screen rule icon on the top right corner. 

9..png

  1. Enter a name for your rule.
  2. Select either Screen name or Screen class from the first drop-down menu.
  3. Select a suitable operator.
  4. Enter the name of the Screen name or Screen class (based on the option selected in step 7). A set of matching options are suggested. Select your Screen name or Screen class.
  5. Select either Android or iOS from the platform drop-down menu and select a suitable operator.

10..png

The above rule tracks the feature when a user views the page called screen mobile from the Android app.

To create multiple rules in a single feature, click + Add. For example, to create a feature that tracks both the sign-in page and sign up pages simultaneously, create two rules in the same feature. This feature jointly tracks all sign in and signup attempts. You must use the OR logic to ensure that the feature is tracked when either of the two rules is executed. The AND logic must be used when you want to track the feature only when both rules are satisfied.

11..png

You can view the analytics of the feature or modules from the Adoption report.

12..png

You can also view the features that a user has accessed, from the Recent Activity section of the Audience Explorer page.

13..png

Create a Custom Event Rule

This section explains how to create custom event rules. Custom event rules track those aspects of your mobile application that are not readily displayed on mobile. A developer must first create custom events in your own application and associated properties if any before you can create custom event rules. 

To create Custom event rules:

  1. Select the required feature. 
  2. Click custom event icon or right-click the required feature and select custom event. 

14..png

  1. Enter a name for the rule.
  2. Select the required event from the drop-down menu.

15..png

  1. (Optional) Click + Add to add properties for the event.

16..png

  1. Select a suitable operator for the property type and enter the name of the property.

17..png

  1. (Optional) Click + Add to add multiple Properties. You can apply AND or OR logic between properties. 

18..png

  • Was this article helpful?