Skip to main content
spencer_engel
spencer_engel
Expert ⭐️
July 12, 2019

How to historically snapshot data to the MDA

  • July 12, 2019
  • 15 replies
  • 1695 views
Hi everyone -

Have you ever wanted to historically report on a customer's ARR over time, only to find that it's actually really hard to find that information since there's no historical record of it? How about trying to figure out the average amount of days your customers are in a certain lifecycle stage? Or trying to figure out who all the named CSMs have been on an account over the course of a year or two?

The easiest way in Gainsight to keep track of such information is by creating a snapshot table in the MDA. In this video, I explain how to set up an MDA object as well as a rule that can load to such a table. Please let me know if you have any questions in the comments below.



    15 replies

    Show previous replies
    spencer_engel
    spencer_engelAuthor
    Expert ⭐️
    May 19, 2020

    @spencer_engelis there a way to use this solution to grab a date in the past?  I want to see how which CSM accounts were assigned to a certain ARR amount on January 1st of this year.  Is this possible with this solution? Or maybe you have another to do this?

    @ablnsj If you have been snapshotting your ARR since January 1st (using this solution), then yes, absolutely you can see which CSM accounts were assigned to which ARR levels back then by filtering on the date. If you have not been snapshotting - whether in Gainsight or elsewhere - up to this point, then you’re likely out of luck unfortunately.

      K
      kytpowell
      Contributor ⭐️⭐️⭐️
      April 5, 2022

      @spencer_engel I am trying to snapshot a date a specific usage metric was achieved. But once that snapshot date is there, I do not want it to get overwritten. This is all just a single row of data per account/subscription vs. a new snapshot every time the rule runs. Any ideas how I can get it to work like that? 

      spencer_engel
      spencer_engelAuthor
      Expert ⭐️
      April 6, 2022

      Yeah, then you would just have two dates. So think of the “snapshot date” as its own entity unique to the snapshot table. This will be one of your identifiers. The other date related to the usage data would be treated just like the other usage-related metrics.

      K
      kytpowell
      Contributor ⭐️⭐️⭐️
      April 13, 2022

      @spencer_engel I think the roadblock I am running into is in the same rule I am snapshotting dates for 6 different metrics. So if I use the date as an identifier, it will not update the other metrics. And if I create separate actions for each metric, or different rules for each metric it will then create new rows based on each metric vs one row per subscription with all the metrics listed. 

      J
      johnny
      Helper ⭐️
      September 28, 2022

      at 5:13 you mention the rule operation being of type: UPSERT.

      Pardon me for asking:

      I assumed the intent was to write each day a new record regarding the status of the customer stage while setting the rule to run daily.

      Why not set the operation type as INSERT ?

      Guess what I’m asking is why would you want an update element in there as well?

      Terms & ConditionsAccessibility statement