Skip to main content
Alex Doherty
Contributor ⭐️⭐️
May 25, 2023
New Idea

Query Builder Date Range should not be limited to 6 months.

Related products:PX Analytics
  • May 25, 2023
  • 2 replies
  • 123 views

We need to be able to track feature usage across multiple years for several reports in the Query Builder. We are currently unable to do this as it is limited to 6 months (we could only get it extended to cover 1 year when we requested this feature).

Ideally we would want no limit in the Date Range so we can generate reports spanning many years.

    2 replies

    skalle
    Gainsight Employee ⭐️
    skalle
    Gainsight Employee ⭐️
    June 6, 2023

    Hi Alex,

    Today what we have is a soft limit of 6 months.  The reason why we have limits is to ensure that we don’t run into situations where if the number of events is a lot - we dont run into performance issues. This is one of the reasons we ensure we can do time range at a time and get data as per need and also extend date ranges per subscription, data basis.  

    That said, Can I dig a but deeper on usecases.

    Do your usecases need for a large date range or more comparision of metrics across similar date periods in past like Compare from Q1 2021 VS Q1 2023.  For large date range on UI - is it the trends or actual raw data that would help your usecases?

    However, please reach out to your CSM and provide us with the subscription id and the request. We will analyze your data and get back to you on the extension.

    Alex DohertyAuthor
    Contributor ⭐️⭐️
    June 6, 2023

    Thank you for your response. My CSM is aware of our case and advised we raise the idea here whilst they investigate.

    We want to do year on year analysis of the following use cases:

    • Identifying trends in feature usage - we need YoY data for this so we can identify feature adoption and retention.
    • Reviewing the lifecycles of various releases in an overlapping graph format - when are new releases adopted and how long do users stay on a specific release. 
      • This relates to our first point; do increases in release adoption coincide with newly added features?

    This will be used in LOTS of reports (there is an ever expanding list of features and releases to cover) so having a report per year/6 month period would dramatically increase our report count (even if we are JUST looking at the last 3 yearly releases, we may want to include more!) and requires extra management/processing.

    These reports would be arranged in various dashboards to give a top level view of the trends over the year. We will also export the raw data to csv format to do additional processing.

    It would be much easier for us to manage our dashboards with fewer "duplicate" reports as well as giving us a cleaner way to look and compare results over years.

      Terms & ConditionsAccessibility statement