Track pricing event changes in Analytics?

Hi there,

Is there any way to track price changes that have been made using pricing events in tessitura.

Essentially, I would like to single out one zone in a performance, and on the x (horizontal) axis i'd like to track time in days, then on the y axis i'd like to have the price of a standard ticket. Then as dynamic pricing changes happen, i'd like to see how the price for that zone has changed over time.

If i can then overlay current sales levels for that price of that zone, i can see if our pricing changes are having any effect on demand.

Any help much appreciated!

Cheers

James

  • Hi James,

    Price Events are used to evaluate and provide Analytics values for Home, Current, and as of Order Date pricing, but the distinct price events, their dates and prices, are not available in Analytics standard. The closest recommendation I can offer in Analytics is to produce a chart that looks the Max Seat Order Date Base Values on tickets over time using Order Date, and broken about by Zone. (Also, if you use price layers, filtered to just the Ticket Price layer category).

    To include another value on a widget like this, we'd need to either limit the widget to a single zone (or at least only zones that share the same price events and pricing over time), or create a value per zone for both the price over time and sales over time.

  • Hi Chris,

    This is really helpful... thanks!

    I'll give this a go in our setup.

    Cheers...

    James

  • Hi Chris, this might be perfect timing because we are using price layers for dynamic pricing and have been wondering the best way to report on this via analytics as well.  As it seems this would work for price layers, may I ask if you can send me a .dash file that I can import into our Tess environment?  Would be greatly appreciated!

  • Michael and James,

    I'm attaching the dashboard that I used above, but with an enhancement that includes a price layer filter. The top set of widgets are as provided above, where they take a simple [Max Seat Order Date Base Price] over time. In cases with price layers, typically the "Ticket Price" is the highest value / max layer for any given seat, and while it's easy to distinguish your pricing between zones, it doesn't reflect the full price across all layers. 

    I've added a second set of widgets that take the combined price layer [Seat Order Date Base Price] over time with this formula:

    MAX(
    [Perf Seat Key] ,
    [Total Seat Order Date Base Value]
    )

    Benefit from this shift:

    • Not only does it reflect all layers and the full value of the seat... it will also respect a price layer filter and show the value based on the layers filtered for inclusion.
    • If you need to use price layers instead of price events to implement dynamic pricing, because you have to send the incremental revenue to another GL, then this will allow the inclusion of those layers in the [Seat Order Date Base Price] over time.

    Best,
    Chris

    78104PriceEvents.dash

  • Thanks so much, Chris.  I will import this at the start of the week.  I'll follow up with you to let you know how all goes.