Skip to main content
New Idea

Enable Add Columns and surface additional data in PX Engagement Performance (In App Performance)

Related products:PX Analytics

Molly.McQ

Currently, when viewing Engagement Performance in PX (Analytics > Engagements > In App Performance), the column data is limited, and although there is additional data surfaced when we export to CSV, we are not able to add any columns/data in PX for quick insights into key data points, like view date.


PX Engagement Performance displays the count of views, completions, clicks, and visits, along with the user’s name, email, account name, inferred city, and inferred country. Yet, we have no visibility of when the user even viewed the engagement until we Export CSV to reference Latest View, a time date field that is limited to the last view. When a single user views an engagement multiple times, which often happens at our org, we are currently only able to see the Latest View; we have no insight into the initial/previous view dates/times.

Furthermore, we have no data in the Engagement Performance or associated csv related to the date/time the engagement was completed or clicked (CTA). This is important information that helps us better understand our users and their behavior, but like the initial/previous view data mentioned above, this data is missing.

Overall, there is critical data not currently captured here that should be. Also, users must export/navigate elsewhere to view related data that could be surfaced directly in the PX Engagement Performance for a more efficient and user-friendly experience.

This request has 2 parts:

  1. Add the following fields to the Engagement Performance/Export CSV data:
    - a. First/Initial View (date time)
    - b. Completed Date (date time)
    - c. Click Date (date time)
  2. Allow users to Add Columns to view in PX Engagement Performance to select and pull in additional data as desired manually (reference functionality in CS: Cockpit). For example, suppose the above fields were added but not displayed by default. In that case, these could be displayed in the Engagement Performance by simply adding the field as an additional column via Add Columns.

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings