YoY Analytics

I've struggled to do percentages-over-time graphs as well.

Working in the Plans cube, my starting point would be to do a line chart with Calendar Month Sort on the X-Axis, and a formula of [Total Contribution Amount] / [Total Goal Amount] on values, with Fiscal Current Year Offset on the break by.

I've not worked out this particular question on my own.

One of the tricks is to start with a pivot table before you try to chart.  This will make sure that the values you are graphing are correct. 

The "Goal Amount" you will likely find is the biggest challenge.  You may want only the goal amount from one contribution not the sum of the goal amounts that might live on all of the contributions. Here is a conversation over in the TAMATO group that might be a bit helpful.

https://community.tessituranetwork.com/topical_groups/tessitura-analytics-for-marketing-and-ticketing-operations-tamato/f/discussions/23105/budget-amount-not-showing-what-is-expected

Thanks, Tim! I'll have to look into this. Appreciate your suggestion.

Thanks, Tom. I did start with a pivot table to verify my numbers, which is where I'm having a difficult time with the last year same point in time portion.

That other post is helpful! Thank you for sharing. It is so nice having a community to learn and share from/with others!

Hi Rachel,

The last year, same point in time piece, is something I have been struggling with a bit as well...and my understanding is that this isn't something that is 'easily' doable out of the box at this point.  It was mentioned though that this is being considered for future releases...as the year-to-date, year-over-year piece is important for attractions like Museums/Zoos.

The 'solution' that is working for us is that we have filtered our dashboards by the 'Fiscal Week' (Performance Date) and although we have to add the 'new week' every week, it gives us a pretty good idea of where we are at. This works for us based on what we need, but it is manual.

Here is a few other threads that might help...

If you created separate widgets for each year, you could probably do something like this to get them to update 'automatically'
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_shared_reports-9/23110/dashboard-to-run-from-july-1-to-dashboard-run-date

This post about relative dates in general has some info
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_shared_reports-9/22799/relative-dates-in-analytics

This thread (referenced in the one above), that talks about some custom formulas that might help...I personally found these a little too complex to maintain, but they might work for you!
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_shared_reports-9/22047/analytics-weekly-sales-contributions/63423#63423

Derrek,

That's encouraging that it is being considered for future releases (I now see that note in the responses to your post). 

Thank you for suggesting the fiscal week filter. I think I may need to follow this approach.

Furtermore, your post from a couple months ago is very helpful. Not sure how I didn't come across it when I was searching the forum before. 

Thanks for your help!

Rachel

You may have moved well past this, but I've maybe built something out that's similar--

Basically, my formula says (([Total Amount], [Campaign FY filtered to last year], [Days in date, offset by 365 days in code])/([Total Amount],[Campaign FY, filtered again to last year]))

The date code is something I nabbed from a Dashboard Chris Wallingfordhad shared and it reads:

{
  "last": {
    "count": 1825,
    "offset": 366
  },
  "custom": true
}

I'm going for % to actual a year ago today, but goal should be easy enough to sub in.

Screenshot below, though I've multiplied the formula above by the FY20 goal because I'm actually trying to set a pacing benchmark.

Thanks, Kate! Appreciate your reply.

Could you please clarify why your count is set to 1825 and the offset 366?

I am concerned about missing gifts prior to the start of the campaign fiscal year the gift is for, but am wondering if the way you have it set up catches those?

I basically want all dates as of today (yesterday since that's when the data is updated) as of a year ago to compare to this current FY to date.

Hi Rachel!

The short answer is "because Chris Wallingford modeled it that way." But if I understand it correctly, the code is asking Analytics to consider the prior 5 years of gifts (5x365=1825) and then offset by a whole year (so, basically, consider every contribution from six years ago up until a year ago). The code should do exactly what you're worried about--catch those FY19 gifts that were actually made in FY18 and earlier.

By switching out either of the numbers, you can either expand the window of consideration or shift the offset. You could also pull a figure for, say, 3 months ago by switching the 366 to 90.

Thank you!!! I thought that was the reasoning, but am still learning. Very much appreciate the logic spelled out :)