New User Learning Plan

 

ECO provides an easy-to-use interface and an advanced feature set that empowers industry-leading application performance analysis for both native and web applications.

Getting started with ECO is straightforward. After integrating with low-code sensor integration, access the out-of-the-box metrics and metadata to monitor application performance metrics and explore dimensional attributes across your web and native application data.

Summary of what you can do:

Sensor Integration

Perform low-code integration of Conviva ECO sensor to enable automatic, and semantic-less data collection.

Perform These Tasks: ECO Sensors

Conviva ECO integration workflow, for example, for Android:

  1. Configure Gradle dependency.

  2. Initialize the tracker so that it auto-collects events, tracks application specific events, and disables event caching.

  3. Set the user id (viewer id).

  4. (Optional) Track application specific events and state changes.

For platform-specific app sensor integration instructions, refer to:

Blocking Events and Configuring Network Request

Block Event allows you to efficiently restrict event reporting to limit ingest to the most relevant and meaningful events from the sensor, ensuring the accuracy and relevancy of your experience-centric data.

The Configure Network Request tab allows you to set collection rules for conviva_network_request events. When the rules are configured, the Conviva sensor collects events that match these rules. You can then select the collected events as raw data for mapping and metric building. The Management tab also displays all configured collection rules for review and update.

Blocking Events

Perform These Tasks: View Image:

  1. To access the Block Event page, click Block Event from the main page.

  2. On the “Set Block Rules” section, from the “Block Event Name” drop-down list, select the event that you want to block. For example, choose conviva_network_request.

  3. To set block rules, choose one of the options based on your requirements.

    • To block all the events that you selected in step 2, select Block All.

    • To block the specific events that are based on the events you selected in step 2, select Block if…, and fill out the key values that the specific event owns. You can add multiple block rules for different specific events by clicking Add OR Rule.

      For example, if you want to block the conviva_network_request event that triggered when loading images, select Block if…, and fill out the key values as .png, .jepg, and .jpg.

  4. To apply the block rules that you set, click Block Event from the top right corner.

Learn more: Semantic Mapper

  

Configuring Network Request

Perform These Tasks: View Image:

  1. To begin creating rules, click Add New on the left side.

  2. To set rules, fill out the fields in the right pane.

  3. Click Save. The Conviva sensor collects the conviva_network_request events that match the rules.

Learn more: Management

Using Trends

The Trends dashboard provides an easy-to-use interface with an advanced feature set that enables application performance monitoring and user behavior analysis within your applications.

Using out-of-box Metrics to Perform App Analysis

Conviva provides a set of out-of-box metrics, such as App Crashes, and Avg Screen Load Time, to help you quickly access application performance monitoring and user behavior analysis across your web and native applications. Using these metrics, view metric time series in the Trends metric widgets to discover time series performance patterns and anomalies. Also, in Trends drill-down across dimensional values in the dimension drill-down tables to discover impacts and root causes.

For the detailed definitions of out-of-box metrics, check ECO Metrics.

Perform These Tasks: View Image:

1. On the Trends page, select the time range, such as Last 24 hours, and select metrics based on your requirements. For example, selecting Avg App Startup Time, Avg Network Request Duration, Active Users, Screen Loads, Avg Screen Load Time, and App Crashes to analyze the app performance and user experience.

  
2. Check the metric widget time series and distributions for data insights and performance. Select and slice the data to drill down specific anomalies.

3. To get more comprehensive data, click a widget you want to know more about, and check the dimension table. For example, clicking the Avg Network Request Duration widget. Based on your requirements, check the different dimension tables under the different tabs.

  • Trends: displays the readings as per the applied primary and secondary filters. This helps you to analyze the data and check the anomalies if any.

  • Users: provides events and data, such as user ID, app name, country, and city, related to user activities. Click a client ID or a user ID to go to the user timeline for comprehensive and granular analysis of a session.

  • Network Request: displays network request-related data in a tree map format or table format. It helps you analyze the app performance and guide to enhance user experience.

Learn more: ECO Trends

Creating User Defined Metrics in Trends

Enable to create user defined metrics directly in ECO.

Using Presets

Offer pre-defined features as quick starting points for commonly used metrics and metadata use cases:

  • User Experience

  • Server Side Performance

  • Events

Perform These Tasks: View Image:

  1. Click Presets on the ECO.

  2. Select a preset use case from the displayed list.

  3. Check the preset page.

Learn more: Preset

 

  

 

Performing Drill-down Analysis

Use drill-down analysis to effectively analyze app issues, identify error messages, and gain insights into user behavior.

Perform These Tasks: View Image:

  1. Check metrics from the ECO dashboard.

  2. Explore dimensional data from the Dimension table.

  3. Deepen analysis with user timeline.

Learn more: Performing Drill-Down Analysis

Event Discovery

Conviva LiveLens, Paths and Funnels enable event discovery as an important precursor to the development of meaningful and actionable metrics. These dashboards or tabs help identify and analyze key event flows essential for metric creation, such as network request response codes and UI element names.

  • LiveLens: Shows a real-time list of the event names and tags as they occur while using your application. With this feature, monitor the event flows (initial and follow up events) for application activities to discover and confirm the event mappings for building metrics.

  • Paths: Visually shows the pattern of events in sequential path flows. This dashboard helps you understand the sequence and composition of events, providing insights for metric creation and potential issue identification.

  • Funnels: Visually tracks conversion rates across key event progress for selected dimensions. This dashboard helps you understand each step in conversion rates, such as from starting the login process to login success, and highlights potential conversion blocks.

 

Exploring Events in Real Time

Perform These Tasks: View Image:

1. Access the demo website and perform online actions, such as selecting and purchasing food.

Note: This Conviva demo website simulates the processes and user behaviors for online food ordering.

2. From the ECO menu, click Activation, then click the LiveLens tab on the Activation page to access the LiveLens page.

3. By default, the Find Myself By IP Address option and the current IP address are automatically selected.

If you follow the recommendation in step 2 to use the same network for the demo website and the ECO application, click Find to continue.

If not, use the search engine on the device that opens the demo website to find the IP address, enter the IP address, and then click Find to continue.

4. From the pop-up table, locate your client ID and click the client ID to open the Real-time Timeline area.
5. Explore the events in the Real-time Timeline area and related event details.

The Real-time Timeline area shows follow-up events after clicking the Purchase button on the demo website.

Expand the purchase events to view the details.

6. From the Real-time Timeline area, identify the required messages to map two purchase events for creating a metric that measures the purchase processing duration:

  • Mapped event name: Payment Start Event

    • Event Name: purchase

    • Tag Key: status

    • Tag Value: start

  • Mapped event name: Payment Success Event

    • Event Name: purchase

    • Tag Key: status

    • Tag Value: success

For more details on how to map events and use complex event combinations to create metrics, check Semantic Mapper and Metric Builder.

  

Check Event Sequence and Conversation Rate

1. Click Paths in the ECO main menu.

2. In the pop-up window, fill out the fields with the time range, global filter, view paths (starting with or ending with), click Generate Paths to display paths for the configured settings. In this example, discover the events following visiting the login page on the web player app.

App Name: Web Player

Starting with Event: Login Page View

3. Review the created Paths to discover events.

From the created paths, you can identify several events appearing after visiting the login page, such as Login Request, Bad Event, Register Page View, conviva_page_view, and Unsuccessful Login.

The Login Page View and Unsuccessful Login events can be used to create a login failure metric for tracking the conversion rate from the starting login process to unsuccessful login.

4. To check the conversion rate from the starting login process to unsuccessful login, select the Login Page View and Unsuccessful Login events.

From the funnel diagram, determine if the conversion rate shows sufficient activity to support the metric creation. In this case, 11.32% is substantial.
5. Click View Funnel and the Funnel dashboard opens automatically.
6. To track specific data conversion, set the breakdown event. For example, to check the conversion rate in different browsers, select Browser name from the drop-down list and choose specific browsers such as Chrome, Safari, Firefox, and Edge.

7. Review the detailed conversion rate for different browsers.

With these steps, using the Login Page View and Unsuccessful Login events for a login conversion rate metric provides significant login insights.

Activating Data

ECO data activation enables you to map new events and create metrics to efficiently explore and manage the current application events for enhanced insights and do data analysis for more complex scenarios.

Mapping New Event

  • Map events as ECO trend drill-down entities to enable deeper analysis using dimensional drill-down.

  • Map events to create customized metrics.

Perform These Tasks: View Image:

  1. Click Map New Event on the Activation page from ECO.

  2. Specify the event name along with the tag key and tag value that consist of the mapped event.

  3. Select a suitable category, type the event name in the Set Mapped Event field, and then click Save.

  4. Click Deploy from the top right corner.

Learn more: Map New Event

       

Building Fully Customized Metrics

Customize metrics to analyze data for complex scenarios, such as analyzing the login process time.

Perform These Tasks: View Video:

  1. Click Metric Builder on the Activation page from ECO.

  2. Set the metric type and provide metric data, and then click Save from the bottom right corner of the Metric Builder page.

  3. Go to the Semantic Mapper page, and click Deploy from top right corner.

  4. Go to the ECO dashboard and make sure that the created metric is in the User Defined Metrics list.

Learn more: Metric Builder

Using Templates to Create Custom Metrics

Enable efficient custom metric creation with the assistance of pre-filled fields and commonly used event associations.

Perform These Tasks: View Image:

1. On the Welcome page, click View All Metric Templates.

2. From the use case list, select a required use case. In this case, choose Login Start to Success Conversion Rate. Click Create This Metric with Wizard

3. Fill out required fields with wizard and click Next Step to complete the two required events configurations. Define metrics and click Create.

       

4. Find the created metric in the User Defined list.

Learn more: Metric Builder

Setting Collection Rules for Network Requests

Set collection rules for conviva_network_request events. When the rules are configured, the Conviva sensor will collect events that match these rules. You can then select the collected events as raw data for mapping if necessary.

Perform These Tasks: View Image:

  1. To begin creating rules, click Add New.

  2. To set rules, fill out the fields in the right pane.

  3. Click Save. The Conviva sensor will collect the conviva_network_request events that match the rules.

Learn more: Configure Network Request

   

Viewing User Timeline

Drill down into session timelines for comprehensive and granular analysis of a session.

Perform These Tasks: View Image:

Access the user timeline for impacted viewers or by user id.

  • From the drill-down tables, select users tab to show the users impacted by the selected performance metric. Click the user name to go to the user timeline.

  • Click the User Timeline menu to access the user timeline page for specific user id.

Learn more: User Timeline

Using Custom Dashboards

Enable the combination of widgets and display options to highlight the insights that are most meaningful to your users and business.

Perform These Tasks: View Image:

  1. Click + New Dashboard, and select one or more data sources based on your requirements.

    • To use only app data, select Single Data Source and choose ECO from the Data Source list.

    • To use app data along with other types, such as VIDEO or AD, select Multiple Data Sources and choose ECO and other required data sources, such as VIDEO, from the Data Source list.

  2. In the edit mode, select the time range, and click New Widget.

  3. Fill out all required items, and click OK.

  4. Check the created dashboard.

  5. For complex analysis across different data displays, add more widgets following the same process.

Learn more: Custom Dashboards

   

  

    

  

Custom Metric Creation Use Cases

These use cases provide a hands-on way for you to quickly implement custom metrics using Metric Builder and other ECO features. The custom metrics in the use cases are commonly used for analyzing the application performance and user experience.

Full Sign-Up Time

The custom metric Full Registration Time measures the time from starting the registration or sign-up process until the registration is complete. This metric enables you to do analysis of registration process and identify whether the process is cumbersome.

Perform These Tasks: View Image:

1. Confirm mapped event(s) are available. If they are not, map event(s).

  • A mapped event that shows a user clicking a link, button, or loading a page to start the registration process. In the use case, the mapped event is Start_Registration.

  • A mapped event that shows the page load immediately following a successful registration. In the use case, the mapped event is Start_Registration.
2. Use Metric Builder to assign mapped events to the new metric, and click Save.
3. On the Semantic Mapper page, click Deploy.

4. Display the new metric in ECO.

  1. Navigate to the ECO page by clicking ECO from the main left menu.

  2. Click Metric and from the User Defined Metrics list, select the Full Registration Time metric.

  3. View the metric in the Trends dashboard and other ECO pages.

       

Full Login Time Monitoring

The custom metric Full Login Time measures the time taken for the entire login process, including the loading of the login form/page, user input of their username and password, form submission, and the subsequent loading of the page users are redirected to upon login. This metric is essential for analyzing application performance and identifying the root causes of slow login times.

Perform These Tasks: View preview image:

1. Confirm mapped event(s) are available. If they are not, map event(s).

  • A mapped event that shows either the button click event to load the login form/page or the page load event for the page containing the login form. In the use case, the mapped event is Login_Click.

  • A mapped event that shows the page load event that occurs immediately after a successful login. In the use case, the mapped event is Load_Home_Menu.
2. Use Metric Builder to assign mapped events to the new metric, and click Save.
3. On the Semantic Mapper page, click Deploy.

4. Display the new metric in ECO.

  1. Navigate to the ECO page by clicking ECO from the main left menu.

  2. Click Metric and from the User Defined Metrics list, select the Full Login Time metric.

  3. View the metric in the Trends dashboard and other ECO pages.

       

Time to First Play

The custom metric Time to First Play measures the time from when a user logs in to the system, until the user plays a video.

Perform These Tasks: View preview image:

1. Confirm mapped event(s) are available. If not, map event(s).

  • A mapped event that shows the page load immediately following a successfully logging in. In the use case, the mapped event is Load_Home_Menu.

  • This mapped event may vary based on whether you integrate the video sensor in your application. In the use case, the mapped event is Video_Start.

    • If you integrated the video sensor, use the predefined mapped event conviva_video_play.

    • If you do not integrate the video sensor, use a mapped even that shows a page load or button click indicating the start of video playback.
2. Use Metric Builder to assign mapped events to the new metric, and click Save.
3. On the Semantic Mapper page, click Deploy.

4. Display the new metric in ECO.

  1. Navigate to the ECO page by clicking ECO from the main left menu.

  2. Click Metric and from the User Defined Metrics list, select the Time to First Play metric.

  3. View the metric in the Trends dashboard and other ECO pages.

       

Learn ECO Learn ECO Learn ECO New ECO User New ECO User New ECO User