What do the package data coding fields mean?
Learn what each field in the package data coding file means and which fit best with your data.
🔶Contextual Data
The contextual data populates columns the first columns of the file. Here you will find the values taken directly from your CRM. These values will not change when you apply new coded values.
⭐Use these values to guide your decision-making when data coding.
In this section you will find
Package Name | The name of the package |
Package Type | The type of the package |
Season Name | The name of the season in which the package was sold. Where available, this field will be populated with values taken from your CRM. If your CRM does not include Season names, we will generate a value for this field. |
Year | The season year in which the package was sold. If the season spans two years (starting in 2024 and ending in 2025), the closing year will show here. If your CRM does not include Seasons, we will generate this value based on your financial year. |
🔶Changeable Data
The Changeable Data contains both current and updatable coding cells, and populates the final columns of the file. The 'Current Value' columns contain the current coding values - these may have been populated automatically by the system, taken directly from you data or created manually by a user.
🔹New Package Name
🗝️ This is a key field and must be completed to use the Subscription Tracker
This field populates automatically with the values contained within your system. Coded values will appear in the Subscription Tracker and in the Ticket coding file and UI.
Tip - take this opportunity to standardise your package names. Try removing references to season year or day of the week - aim to only keep the most relevant information, and standardise it across all seasons as this will make it easier to analyse in the Subscription Tracker.
Example:
Consider these packages:
Saturday Eve 3-Pack | Saturday Evening Trio | Saturday Matinee |
Saturday Eve 4-Pack | Saturday M Capitol Theatre | Saturday Matinee Complete |
Saturday Eve Complete | Saturday M Eccles Theatre | Saturday Matinee Essential |
Saturday Evening | Saturday Mat 4-Pack | Saturday Matinee Trio |
Saturday Evening Complete | Saturday Mat Complete | |
Saturday Evening Essential | Saturday Mat Conversion |
You may wish to group them in several ways. Some examples would be:
- Group all these packages into
Saturday
- Group them into
Matinee
andEvening
- Group them into
Complete
,Essential
,Trio
andOther
.
🔹New Package Type
This field is initially coded based on trends in your data. There are two possible coding options to select from:
Fixed | A type of ticket package where patrons commit to a set series of performances on specific dates and seats throughout the season. |
Flex/CYO | A type of ticket package where patrons are generally able to pick and choose the performances they wish to attend and the seats in which they sit. |
🔹Series Name
🗝️ This is a key field and must be completed to use the Subscription Tracker
This is a custom field so will not be populated by the system and must be coded manually. It is also a key part of the Subscription Tracker, and must be completed for that tool to work.
Tip - If your organization does not sell Subscriptions in multiple Series, try using a generic label here.
🔹Min Performances
Where trends can be identified, this field may initially get coded based on what we see in your data.
🔹Max Performances
Where trends can be identified, this field may initially get coded based on what we see in your data.
🔹Day of Week
Where trends can be identified, this field may initially get coded based on what we see in your data. There are several fixed coding options for you to choose from:
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
Saturday |
Sunday |
Weekdays |
Weekends |
Mixed |