We've recently launched some new functionality whereby 'group bookers' (i.e. those booking more than 10 tickets who we permit to reserve and pay later) can edit their reservations online. They can't yet create new reservations online, which is still being done through our phone room. They can just add or remove seats from the order, pay off or cancel their pre-existing reservation.
Naturally I'm being asked about take-up of the new functionality, but I'm not really sure how to pin this down in Tess. I'm not looking for anything particularly granular. Even if I could just say how many people have been on the site and made changes to their reservation, that would be a great start.
In seats and tickets cube, the mode of sale doesn't really help me since that will remain as the original source, the phone room, irrespective of if there are later changes to the reservation. I thought about using the Created By criteria, but that seems to refer only to who originally created the order, rather than who might have later added seats to it later. I don't think the finance cube would help me either since some of those using this functionality won't be paying for anything, just adding or removing seats from an unpaid order. Even if I was to try to count only those who paid off their reservations via the website, I'm not sure how I would distinguish these transactions from straight website sales.
Huge thanks in advance to anyone who might be able to point me in the right direction on this!
Lawrence.
Hi Lawrence thanks for posting! You might find cross-posting to the new Ticketing & Admissions Community Group and/or the EU Museums & Attractions Community Group an idea - hopefully you'll get some responses over there.
Gill, Community Manager
I'll only answer if you cross post on analytic Coffee!
I only have the sandbox which is v16 (long story) but you might be able to do something in the Seats & Tkt Cube and SLI Status.
Now help mentions that create date dimension refs the sli create date which would be handy for when stuff was moved and where but I'm getting a SLI create date as 4 years prior to the order date in my example - might be a sandbox thing - dash attached
Fields in this dimension reference the creation date on a sub line item or membership scan. For imported ticket history, the order date is referenced.
https://www.tessituranetwork.com/Help_System_v160/Tessitura-Analytics/Data-Dictionary/Seats-and-Tickets-Cube.htm
SLItest.dash
I've also observed garbage in the SLI create date field in Analytics (v15): I think it's unreliable generally.
That's good (but sad) to know. It could be a contender.
Definitely sad to hear, Gawain. The Seats & Tickets CREATE DATE comes from the SLI Detail (Price Layer), as they can be added at later times than the initial SLI. In cases where there is no SLI Detail, the create date from the SLI is used. The documentation isn't explicit about that and I've requested an update. For membership scans, it's the date of the scan. And for imported Ticket History, it's the date of the order. If you're finding any of this to not be the case, I'd love for our Support teams to have a chance to get to the root of the issue, if you have the opportunity to take it up with them.
Cheers,Chris
I was comparing the create date to the create_dt in T_SUB_LINEITEM and found significant discrepancies, but instead I should have looked at create_dt in T_SLI_DETAIL?
It's been a long time, but I had been hoping to use it as a substitute for transaction date, and I understood at the time that it was just fundamentally unsuited to that.
Correct on both counts: T_SLI_DETAIL and that will not equate to transaction date.
ahh transaction date. The Count Rugen to our Inigo Montoya