I'm building out widgets to look at our animal Encounter programs. One of the metrics we're looking at is Total Sold Seats vs Total Available Seats. The numbers appear correct for each program, except one.
This program has one seat available per performance, three performances per day, for the rest of the year (starting 10.8.20, through 12.31.20). Pulling information from the number of performances through Season Maintenance, it returns a total of 249 performances, and therefore 249 seats (the rest are blackout-held).
However, Analytics for a few days has returned a total of 717 total seats available. Even dividing 717 by 3 yields 239, not 249.I've switched it from 'Sum' to 'Auto' for calculation, which doesn't change the total. I used a bit of bucketing to have it only look at seats with status = available, and that reduced the number to 714.Why is it returning such a large number?
Hi Nathanael,
I suggest filtering to show only Sea Lion Spotlight. Add Perf Seat Key, Price Layer Category, and Price Layer on rows. See if that clears it up, and then I suggest a support ticket for additional research.
Thanks,Chris
The count has now changed since I viewed it last. It now shows a total of 7 seats sold, and only seven available.
I verified that the list of performances have much more than 7 total seats available.
The Sold count is correct, but there should be ~249 (barring holds and whatnot). When I created a widget only for Spotlights, adding in the Perf Seat Key/Layers/etc, it presents the same information:
I'm going to submit a support ticket- these seem quite odd numbers to get.
Have you received any word back on the ticket you submitted? We have been running into a similar issue on one of our dashboards.
The TASK folks are looking into it- I've submitted the .dash file just this morning, so I hope to have insight soon!They also advised me to turn off the 'Suppress Unsold' keyword for that Production, so I've done that and am now waiting for a full data warehouse load to see if that clears things up.
The latest update:
It seemed to be something to do with a full Analytics warehouse load, which seems to happen once per week. Since the latest full load, the numbers have been much lower, resulting in reasonable numbers.
I'm not sure why the numbers swung from very high to very low, then settled, but they have settled.