I am still dealing with issues from our summer discounts from 6 months ago!
Here is the issue:
To make things easy for our Front Desk this year, instead of doing it all as a Promo/Source Code (like the year before which gave inaccurate numbers because the Front Desk forgot to switch the source code between orders) I created a Discount for the in-person sales and then kept the Promo/Source code for online sales.
This worked great in built out and for our front end; however, because pricing rules/sources and discounts are two completely different things, reporting on them has been a nightmare. I have 2 different widgets set up; one has the discounts, the second has pricing rules. The problem is the Total Attendance is the same for both, but the breakout is different and we don't know why. I don't know if I built the widgets wrong, or if its because I'm trying to get Tessitura to do something it simply won't.
What our org needs: Total number of attendance by Ticket Type for ALL discounts (discounts and pricing rules combined); separated by discount.
So basically I want to combine the two widgets into one clean widget.
Attached is the dashboard file (ignore the comp reason widget, that is completely correct and what we need).
CLM71223-CompReason&Discounts.dash
Hi Chelsea - I wonder if the differenced in the breakout is to do with the pricing rules qualifying tickets vs tickets with pricing rules applied? If you add the 'pricing rules' from the seat & tickets details you should be able to see if this is the difference in your breakout. Q = ticket that qualified the pricing rule for the discount & R are the tickets the rules where applied to. Discounts don't use qualifying rules so that might be the difference?
You could get both discounts to show in the same widget using bucketing - create a bucket for the tickets with pricing rules & then also a bucket for those using discounts & one showing overall ticket numbers
Your bucketing for pricing rules would use the pricing rules from the pricing rules section & then you could optionally select which rules to include in the ticket numbers.
you would create buckets for each as required & end up with something like (discount column blank as we don't use them like you do)
or Mode of Sale - as Anne already suggested!
That still isn't clear enough for my staff. I basically need the impossible I think. The pricing rule number needs to be combined with the discount number. For example (the same example I just gave Anne): if we sell 25 CT Summer Free tickets online (using source code) and 75 in-person (using discount), I just need the widget to tell me that we sold 100 CT Summer Free tickets.
I think you could still do this with bucketing - ( [total ticket count] , [pricing rule] ) + ([total ticket count] , [discount type] )
Good idea Jo. Use the separate widgets to confirm the total.
Ok, so what original filter am I going to have to change the formulas on. And I still need it to list out every single discount and pricing rule we use. Over the course of the summer we run 3 campaigns that will overlap.
How do I tell Analytics that I need it to show that combo for each of the 3 different discounts without it looking ridiculously cluttered?
Sorry Chelsea - as soon as you ask the widget to list the discounts it's going to split the amounts out as they are 2 different things pricing rules & discounts - bucketing them together is the only way I can think of to give you both the combined total of onsite & online without 2 different amounts. 3 campaigns with 3 discounts is 9 columns so maybe not too bad to try?