Hi guys! Greetings from South Wales.
I’m trying to answer what feels like it should be a pretty straight-forward question in Analytics- number of tickets sold and amount paid for them via the website in any given month. My concern around this though is the difference between the order date and transaction date, and the unavailability of the ticket paid count criteria in the Finance cube.
Our monthly revenue always come out different when the month is defined by order date rather than transaction date. And I get why- since additional products are often sold in existing orders offline by ticket office over future months. So in this instance I’d rather define the month by the transaction date- but then this is only available in the Finance cube, where I can’t use the ticket paid count criteria. Getting the number of tickets sold from Seats and Tickets cube, with the month defined by order date, and the revenue from Finance cube, with the month defined by transaction date, doesn’t feel right since they’re looking at different sets of transactions. For one it’s going to give a misleading impression of the average price paid.
Does anybody know another way around this? Perhaps I’m missing something obvious?
Many thanks!
Lawrence.
Wales Millennium Centre.
Sorry I didn't answer at the time, but I'm afraid the answer is that there simply isn't any kind of substitute for Transaction Date in the Seats and Tickets Cube. There's talk about that changing in some future version?
Hi Lawrence,
This topic is so interesting to me. I try to collect as much perspective and input as I can so that if there's an opportunity to make a change in the platform, we're ready. I'm curious... if a ticket were partially paid in one month and the balance paid in the subsequent month, would you expect that one ticket to be reflected in the ticket counts when reporting on the first month? ...when reporting just on the second month? ...when reporting on both months as a single period (e.g. the fiscal year as a whole)?
Would you ever want to filter or segment the amounts within a month by something for which a single ticket could fall into multiple segments, for example payment methods? If so, and a ticket where purchased partially with a gift certificate and the balance with a credit card, would you expect that one ticket to be reflected in the ticket counts when reporting only on gift certificates? ...when reporting on just credit cards? ...when reporting in aggregate with the payment method filter is removed?
Thanks for your feedback!
Chris, would the the "ticket count" refer simply to the reservation, with the other items being tracked by changes to "amount paid" or something like that?
Hi Gawain,
Hard to say... It depends on the desired outcomes. If we expect to be able to filter the widget to only refunds and see a ticket count, then that might be supported by tying the ticket count to the reservation... which feels similar to ticket layers in Seats and Tickets. At the moment, if we want to filter a widget to just a Facility Fee layer, the Ticket Count returns 0.