Experience Metric Use Cases

 

These use cases provide a hands-on way for you to quickly implement custom experience metrics using Metric Builder and other ECO features. Custom experience metrics are commonly used for analyzing the application performance and user experience. Typical workflow to create an experience metric:

  • Event Mapper: Confirm that mapped event(s) are available. If they are not, map event(s).

  • Metric Builder: Assign event(s) to the experience metric, using the metric templates when applicable.

  • Semantic Mapper: Deploy new metric to Trends and other pages.

  • ECO: Display the new metric for advanced experience analysis.

Full Login Time Monitoring

Slow login times can limit the number of users who successfully access the system. During login issues, users may either abandon the process or encounter timeout errors.

The custom experience 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.

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

    Before creating the Full Login Time metric, ensure that you have the required mapped events set up:

    • 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. Metric Builder: Assign event(s) to the custom metric.

    Use Metric Builder to assign mapped events to the new metric.

    1. Click the Metric Builder tab on the Data Modeling page.

    2. Click the add new icon on the left side of the Metric Builder page.

    3. Select the suitable item and fill out the metric fields.

      • Metric Type: Time Interval Metric

      • Metric Name: Full Login Time

      • Description: The time it takes for login to process.

      • Definition

        • Initial Event: Login_Click

        • Follow-up Event: Load_Home_Menu

        • Pairing Logic: First-First Pair

        • Count: first pair

    4. Click Save to save your metric configuration.

  3. Semantic Mapper: Deploy new metric to Trends and other pages.

    Use Semantic Mapper to deploy the metric.

    1. Click the Semantic Mapper tab.

    2. On the Semantic Mapper page, click Deploy.

      The deployment takes several minutes to take effect.

  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.

Full Registration Time

A difficult or slow registration process causes high abandonment rates.

The custom experience metric Full Registration Time not only measures technical performance but includes the time it takes to fill out a registration form. This metric 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.

  1. Event Mapper: Confirm that mapped event(s) are available. If they are not, map event(s).

    Before creating the Full Registration Time metric, ensure that you have the two mapped events set up:

    • 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. Metric Builder: Assign event(s) to the custom metric.

    Use Metric Builder to assign mapped events to the new metric.

    1. Click the Metric Builder tab on the Data Modeling page.

    2. Click the add new icon on the left side of the Metric Builder page.

    3. Select the suitable item and fill out the metric fields.

      • Metric Type: Time Interval Metric

      • Metric Name: Full Registration Time

      • Description: The time from starting the registration or sign-up process until the registration is complete.

      • Definition

        • Initial Event: Start_Registration

        • Follow-up Event: Page_Registration_Success

        • Pairing Logic: First-First Pair

        • Count: first pair

    4. Click Save to save your metric configuration.

  3. Semantic Mapper: Deploy new metric to Trends and other pages.

    Use Semantic Mapper to deploy the metric.

    1. Click the Semantic Mapper tab.

    2. On the Semantic Mapper page, click Deploy.

      The deployment takes several minutes to take effect.

  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 longer a user takes to find something they want to watch, the less likely they are to watch anything.

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

  1. Event Mapper: Confirm that mapped event(s) are available. If they are not, map event(s).

    Before creating the Time to First Play metric, ensure that you have the two mapped events set up:

    • 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. Metric Builder: Assign event(s) to the custom metric.

    Use Metric Builder to assign mapped events to the new metric.

    1. Click the Metric Builder tab on the Data Modeling page.

    2. Click the add new icon on the left side of the Metric Builder page.

    3. Select the suitable item and fill out the metric fields.

      • Metric Type: Time Interval Metric

      • Metric Name: Time to First Play

      • Description: The time from when a user logs in to the system, until the user plays a video.

      • Definition

        • Initial Event: Load_Home_Menu

        • Follow-up Event: Video_Start

        • Pairing Logic: First-First Pair

        • Count: first pair

    4. Click Save to save your metric configuration.

  3. Semantic Mapper: Deploy new metric to Trends and other pages.

    Use Semantic Mapper to deploy the metric.

    1. Click the Semantic Mapper tab.

    2. On the Semantic Mapper page, click Deploy.

      The deployment takes several minutes to take effect.

  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.

Live Video Attempt to Play Time

The longer the duration between clicking the video play button and the actual start of video playback, the less likely users are to watch the video

The custom experience metric, Live Video Attempt to Play Time, measures the duration from initiating video playback to actual playback commencement. This metric aids in identifying user engagement with video content and facilitates analysis of any underlying factors contributing to delays in playback.

  1. Event Mapper: Confirm that mapped events are available. If they are not, map events.

    Before creating the Live Video Attempt to Play Time metric, ensure that you have the two mapped events set up:

    • A mapped event that shows when a user clicks the video play button. In the use case, the mapped event is Live Video Attempt.

    • A mapped event that shows when the video starts playing immediately after clicking the play button. In the use case, the mapped event is Live Video Play.

  2. Metric Builder: Assign events to the custom metric.

    Use Metric Builder to assign mapped events to the new metric.

    1. Click the Metric Builder tab on the Data Modeling page.

    2. Click the add new icon on the left side of the Metric Builder page.

    3. Select the suitable item and fill out the metric fields.

      • Metric Type: Time Interval Metric

      • Metric Name: Live Video Attempt to Play Time

      • Description: The time between the video sensor attempt and play.

      • Definition

        • Initial Event: Live Video Attempt

        • Follow-up Event: Live Video Play

        • Pairing Logic: Last-First Pair

        • Count: multiple pair

    4. Click Save to save your metric configuration.

  3. Semantic Mapper: Deploy new metric to Trends and other pages.

    Use Semantic Mapper to deploy the metric.

    1. Click the Semantic Mapper tab.

    2. On the Semantic Mapper page, click Deploy.

      The deployment takes several minutes to take effect.

  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 Registration Time Login Time