Good morning,
Our guided tours have been suspended since we shut down in March and we don't plan on bringing them back in the near future. But, as we plan for the day that we do, our visitor services manager would like to see a chart showing the average attendance by zone for the last year or two by day of the week. I'm guessing I need to use bucketing to do this, but I was curious if anyone else as put something like this together yet. (I"ll have to go back and rewatch that video!). Here's our setup -- we offer our tours 4 times a day Tues-Sat and 3 times on Sun. I am looking for a bar chart that shows the average number of tickets sold on each day of the week in each of those 4 time slots for a specified time period (not each individual day).
Any advice would be most appreciated.
Thanks!Anne RobichauxThe Historic New Orleans Collection
That makes sense to me. I'm not sure why asking "How many zones are there, where zone = X" is returning such high numbers.
I'm trying to think through why how to refine the question for Analytics. The question is, essentially, "How many times has X zone been offered, for a given time frame". For Mystic, given that there is only ever one zone per day, I could modify things to be (# of Perf ID) as a substitute for (# of 10:30 Smallfoot Zones), which would avoid having to divide by 44.
In your case, I'm not sure how to break that up without using explicit numbers.To make matters even weirder, my original second formula (# of Zone ID , Zone = 10:30 Smallfoot) is now (as of 12.1.20) returning a different number! Now, when I select just one performance (11/15/20 in this case), it returns 20 as the number of zones. When I do two days (11/15 and 11/16), it returns '40'. Again, that number doesn't mean anything- total zones for the seat map were 45. Total zones available on that day were 17. 20 seems a random number.I'm going to submit a TASK to see if I can sort this out.
Please let me know what you find out. In my case, I think the issue is solved but I'd love to know why it isn't working the way you originally set it up since it seems like that should work and would be the most accurate.
How have you resolved the issue on your end?I'll keep you posted! I just submitted a TASK with the .dash file attached.
In our case, TASK recommended going down the # of Unique Perf ID route, rather than # of Unique Zone IDs. Again, this works because we have each zone running only once per day.I might be overthinking things. Each zone that you have per day, I assume that each zone is separately labeled, and has a separate ID? In that case, each zone (1, 2, 3, or 4) would be synonymous with the number of performances.We could do something like this:
Categories of Zone, to break things out.
Values of Total Ticket Count, and 'Avg Tix per Perf'
Does that work? It's been a few days since I dived into this, I might be missing something.
If you wanted to use bucketing, and have each Value be a separate zone, you could use:
where Zone is filtered by whichever zone you'd like.
I also used Unique Perf ID and it gave me exactly what I needed, number wise. It isn't working as a bar chart for me because our numbers are so low that you can't see the averages (in most cases it is averaging less than one person per zone!). But because the numbers are all small it is easy enough to compare them in a pivot table. Here's what I came up with for each timeslot. Thanks again for all of your help. Our Visitor Services Manager was very pleased with the final result.
Great! You're quite welcome- I'm glad it worked out. Pivot tables are my favorite, usually.