@pchoe Thinking on my toes here, but I don’t think there is an out of the box Call to Action historical object in Gainsight, at least from what I’ve noticed. Instead, you could build a report using the Call to Action object and drag the Created Date field into filters, filtering for Created Date = this year, which will get all CTAs created this year so far (YTD). From there, you can add filters to narrow your report down to the specific CSM you want to see this data for, plus filtering for Status = On Track and whichever CTA type you’re looking for.

To put it a bit more clearly, the filters would be similar to this:

• Created Date = This Year
• Status = On Track
• CSM = >insert desired name here]
• Type = Tinsert desired type here]

To get the KPI, you can do a distinct count of the CTA GSID to give you the number of CTAs matching your filter criteria, and then you can add necessary fields to the drilldown as needed.

Thanks for the attempt, I used the same filters you provided but it gives me the same records for our report that shows Current On Track VOs by IM. Hopefully in the future Gainsight is able to provide reporting on this historical data.

We would benefit from a report object of Previous Status or Previous Priority.

Hey ​@pchoe , like ​@kstim mentioned there isn’t an out of the box way to do this however, there are a couple of ways you could probably capture this, depending on how “accurate” you wanted to be with your counting (or, more likely how often you expect users to change a Status during the day):

1. The simplest way would be to have a field on CTA that is “Days spent in On Track status”, where you use a Horizon Rule to bring in On Track CTAs and increment the field by +1. You’d want to likely run the rule more than once per day, but only *update* the field once per day. Or you could just run it daily, and if a CTA shows up you know it was in that status at least once during the day so you get an n+1 still.
   1. There’s variations of this, but you’re basically snapshotting the data, looking for “CTAs in On Track”, and then incrementing your count for any given CTA if it was in that status, and not incrementing if it wasn’t.
   2. It’s also important that the rule runs daily, or you would miss out.
   3. The actual rule build might not be simple, but conceptually less build out than the other idea
2. Alternately, you can track *every time* a CTA is moved into On track status using a Real Time rule: 

   

   You would need a custom MDA where you would load a record per CTA each time it went *into* the On Track status. This would probably be the most accurate, but you could get some oddly high numbers if users for some reason change it multiple times in a day.
   From here, you could build reports on this data grouping those change records by CTA, to see how many records were ever in on track status, and even how many times they moved in and out of the status.

You could also do some combination of the two, depending on what is important to you to know.