Analytics Dashboard on refund protection sales by production

Hi all,

I am trying to build include a widget to include in an Analytics dashboard that monitors sales of our refund protection product 'Booking Protect'.

I am having some trouble putting together any data on what productions are popular for taking out Booking Protect with. Ideally I would like widgets that show me one widget showing how many sales we have of Booking Protect for each production season, and another which shows what percentage of all sales for a production season include Booking Protect.

Booking Protect is sold as a 'seat' for a specially set up performance in Tessitura. If someone protects their order with Booking Protect, in Tessitura they are adding a single seat to that event to the order. So really I am trying  see what else is in those orders.

Finding this tricky as other dashboard or methods for looking at crossover are looking at all bookings for a customer, whereas this has to be limited to what is within the order.

Does anyone have any good ideas on how I might be able to do this? I had the thought that there might be other instances where you are trying to report on what else is within an order, rather than what else a customer has bought at any one time. 

Another slight complication is that in my other widgets looking at sales of Booking Protect, I am not using the standard data elements for this (like "Ticket Count" or "Ticket Paid Count") as it comes through with no results. I believe this is because these data elements only look at seats sold with price layers in the 'Ticket Price' price category, whereas Booking Protect seats are sold with price layers which are in their own price category. I don't think there is anyway around this but it means that for looking as sales I am using order counts. 

Hope that all makes sense!

Thanks in advance for any help!

Donald Graham
Ticketing Systems & Data Manager
Birmingham Hippodrome

  • Hi Donald,

    I love this question. Assuming a pivot widget with Production Season on rows and a Ticket Count value. One could add a value that is

    SUM ( [Order ID] , ( [# unique SLI ID] , [Production Season = Booking Protect] ) )

    This says... for the orders in the production season row, how many tickets (distinct count of SLI ID) within those orders are in the Booking Protect production season. The formula filter on production season will override the production season grouping on rows to get the count.

    Then duplicate that value and divide by the overall ticket count for the percentage of all sales in the production season that are protected.

  • Hi Chris,

    Thank you very much for your reply - very helpful. 

    I have added as you suggest and managed to get some figures which not only look right to me but also stand up to some checking. I will continue to play about with it as I imagine I will get some feedback or further requests from my colleges.

    One more thing that you might be able to help with this: at the moment the widget still includes "Booking Protect" as a production season on my pivot table. Is there a way I can 'hide' it from the table without filtering it out? Can this be done by using the formatting or design options?

    Thanks, Donald

  • Hi Donald, 

    Using the Production Season field on Rows, select the filter (funnel) icon and deselect Booking Protect. The value formula doesn't need that production season in scope for the widget in order to do the calculation.

  • Hi Chris,

    I was having trouble filtering out the Booking Protect season as you suggest. But raising it with our ES contact we realised that I still had another filter by production season on the widget from when I was doing some testing. Even with this other filter turned off, it was still not letting me filter again. But by deleting this other filter I was able to filter out the BP season as you suggest, which worked great.

    Thanks again for your help. The resulting pivot tables are giving us a really good insight into where BP is popular. 

    Donald

  • Fantastic! Thanks for letting me know :)