Hello friends,
The chart below is a graph of total subscription sales since the on-sale date, which would be 0 in the chart. But for some strange reason, 22/23 sales is way out by its lonesome in week 6. I'm not sure what's causing that, but I'm sure that I've fixed this in the past; I just can't remember where I did it.
Would any of you have any thoughts as to how I could get that blue-green line at week 6 back over to zero? I'm using a filter of Order Weeks Since On Sale.
Happy to provide more clues if needed.
Thank you, friends!
W
Oh hang on. I think I got it, maybe, almost. My subs MOS date for this year was actually Feb 4 because that's when everything got built and set up. Subs sales to public began Tuesday. So I think if I fix the Subs MOS date for my packages, that might move the line back to zero.
Yes, that is the kind of thing I would look at. Also look at the dates on the performance screen in the title, production, production season, performance hierarchy.
Does anyone remember which date is actually used for these weeks since on sale off set values? (I’m not in a place to look at the moment.)
We can also discuss at analytic Coffee in a few hours.
Hi Will,
Look at the Performance On-sale Date dimension from Tessitura v15 Help System - Seats and Tickets Cube (tessituranetwork.com)
Fields in this dimension reference the Default Sales Dates Start Date for a performance. As each mode of sale can have a different start date, the Default Sales Start Date field can be used to record a single on-sale date to use for reporting in Tessitura Analytics. Note: Prior to v15.0, the Default Sales Dates Start Date value on a performance was used as only a default value field (to assist with pricing and MOS setup) and had no actual sales functionality or reporting ramifications. As such, the data in the field may not have been reflective of actual sales dates. The v15.0 upgrade sets the Default Sales Date Start Date to the earliest MOS start date on the performance, unless it has been already changed from the performance create date (the default value for the field). Moving forward, this date should be set on all new performances to the official on-sale date you want to record for use with Tessitura Analytics.
Fields in this dimension reference the Default Sales Dates Start Date for a performance. As each mode of sale can have a different start date, the Default Sales Start Date field can be used to record a single on-sale date to use for reporting in Tessitura Analytics.
Note: Prior to v15.0, the Default Sales Dates Start Date value on a performance was used as only a default value field (to assist with pricing and MOS setup) and had no actual sales functionality or reporting ramifications. As such, the data in the field may not have been reflective of actual sales dates. The v15.0 upgrade sets the Default Sales Date Start Date to the earliest MOS start date on the performance, unless it has been already changed from the performance create date (the default value for the field). Moving forward, this date should be set on all new performances to the official on-sale date you want to record for use with Tessitura Analytics.
This date is then compared against Order Dates to determine the Order Weeks Since Onsale. If the Default Sales Date Start Date is 3 weeks after a given order's Order Date, then it will appear as -3 in Analytics. If these are "internal" orders, testing, or maintenance related, one could change their order dates to align with the configured on-sale dates. Otherwise, verify that the Default Sales Date Start Date on each of the performances is set to what you would expect. This field can be found on the Performance setup page Tessitura v15 Help System - Performances (tessituranetwork.com).
Thanks, Chris! This was helpful and did the trick.