Most of the time we are looking to backfill data for 30 days. We don’t need a whole year’s worth; yet that is the only option. We have exceeded our quote of backfilling due to this constraint. Please allow the user to specify how much backfill data is required.
+3This is a really good callout. Often, changes are made in the product before they’re mapped in PX; the lag time isn’t too long, but you still want to be able to capture the feature usage between deployment in product and instrumentation in product mapper. Backfilling in such scenarios doesn’t require a 365d query - I didn’t realize there is a backfill quote so from a customer’s perspective being able to better manage backfill processes would be great, and also for Gainsight there must be a benefit here in terms of computing power (processing for 365d when 1d or 7d would do).
Allowing users to select a custom date range for backfill would be much more flexible than being limited to the default 365-day period. In many cases, only a specific time window needs to be backfilled, so this would reduce unnecessary processing and improve usability.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
