Hi, all-
I am looking for the event date from the T_ORDER_SEAT_HIST table in analytics, but can't seem to find it. I am trying to track sales by performance by day for purchases and returns. Thinking I may have to add it through use of the custom date fields, but was wondering if anyone has incorporated this into their dashboards already, or using another method I may be overlooking?
Thanks in advance!
Rachel
Hi Rachel,
T_ORDER_SEAT_HIST is a hash that is not optimized for reporting, and isn't currently available as a source in Analytics. There also isn't a simple custom field that would easily take this data into the Analytics data sources. Every ticket is only in the Seats and Tickets cube once, and introducing T_ORDER_SEAT_HIST would result in many dates associated with the same ticket. It's possible to do that, but it's not designed for that kind of data relationship currently.
The Finance cube, on the other hand, if you're okay with looking at money instead of tickets, DOES offer access to this kind of analysis. The Ticket Paid Amount values is the aggregation of both Purchases and Returns, and can be shown over time. You can also split it out and look at just Ticket Purchase Amount as compared to Ticket Refund Amount, and see the timeline and gaps between them.
And in case it's helpful, the Ticket Sales by Period report does include ticket counts via T_ORDER_SEAT_HIST, and shows the aggregation of purchases and refunds within the selected Sales Dates. So run for a given date, will offer the total tickets as the Total Purchased minus the Total Refunded.
Best,Chris
Chris Wallingford said:T_ORDER_SEAT_HIST is a hash that is not optimized for reporting,
T_ORDER_SEAT_HIST is a nightmare that I seem to be unable to ever wake from. It seems like I'm forced to go back to it for reporting at least once every six months.
SMH. I hear you, Gawain. I'm familiar with this pain point. A simple Community forum search for "T_ORDER_SEAT_HIST" makes it clear that there are reporting needs that have repeatedly led people to this table. I'm on the lookout for opportunities in the future to find a better way to fill these needs.
Thanks!
I've had to run triggered email campaigns out of it this year
Chris Wallingford
Not to go off on a little side thing here, but the #1 and #2 reporting issues I keep having trouble solving is 100% accurate reporting of sales against price layers (because we have been repeatedly told that payments are not tied directly to performances, and, while I understand the logic behind the argument, I feel like it can be fixed without having to violate that logic) and 100% accurate reporting of sales over time (because Ticket Sales by Period/T_ORDER_SEAT_HIST has problems I first pointed out 5+ years ago).
If I had solutions to those two problems, I would be a much happier man.
Thank you, Chris. I appreciate your thoughts on this topic. Ideally, we would like to report on tickets as well as money, but I understand the limitations. We have a custom report that gives us this information, but would be great to have it in analytics (hopefully one day!).