Tessitura Custom Fields
In this Article:
Custom fields are utilized for storing information about your contacts. These fields can be used in automations, segments, forms, and more.
Personalization tags, often called tokens, are used to supply specific values to the custom field which can be used in a variety of places, such as Segmentation and Automation logic, SMS, Site Messages, Campaigns, etc. All personalization tags begin and end with a percent % and will be created in an all uppercase syntax. For example,
%FIRSTNAME%
Be advised personalization tags are case sensitive within campaign content, SMS, Site Messages, etc and will not populate if there is not an exact match.
Tessitura custom fields are automatically created in your Prospect2 account and will update based on data fields that are returned from Tessitura during integrated processes.
When an integrated process runs, custom fields are updated with specific data from Tessitura such as performance, order, custom, and web content.
Common Tessitura Custom Fields
Each time you process a Tessitura Integrated Import or Data Sync: Tag, the following custom fields are automatically created and updated with values returned from Tessitura directly in your Prospect2 dashboard. If your List Manager list has an Output Set defined, the additional data points included in your Output Set will be returned upon final import or data sync, in addition to the default fields listed below.
| Custom Field Name | Data Example | Details |
| CUSTOMER_NO | 123456 | Contact's Constituent ID within Tessitura |
| SOURCE_NO | 1234 | If the List Manager list in Tessitura was promoted prior to importing into Prospect2, the SOURCE_NO associated with the promotion is updated on contact records. If the List Manager List in Tessitura was not promoted prior to importing into Prospect2, the SOURCE_NO defined for P2DefaultSource in the T_DEFAULTS System Table is updated on contact records. |
| PREFIX | Dr. | The prefix of name 1 on the constituent record |
| FIRST_NAME | John | The first name of name 1 on the constituent record |
| LAST_NAME | Smith | The last name of name 1 on the constituent record |
| Johnsmith@email.com | Email address returned from Tessitura | |
| SALUTATION | Dr. Smith | Envelope Salutation. The esal1_desc value associated with the record |
| LSAL_SALUTATION | Dr. John Smith | Letter Salutation. The lsal_desc value associated with the record |
| POSTAL_CODE | 60103 | Zip code of the primary mailing address on the constituent record in Tessitura |
| COUNTRY | USA | Country of the primary mailing address on the constituent record in Tessitura |
| STATE | NY | State of the primary mailing address on the constituent record in Tessitura |
| GEO_DESC | Boston/Washington | Geographic area defined on the constituent record from TR_GEO_AREA |
| GEO_AREA | 3 | ID number of GEO_DESC |
Performance Data
When a Performance-based Scheduled Trigger runs, the following fields are automatically created in your Prospect2 dashboard. The personalization tags can then be used for content personalization or segmentation.
Performance data is only retrieved from the performance level in Tessitura.
| Custom Field Name | Data Example | Details |
| PERFDATA__TITLE | The Magic Flute | The title of the performance |
| PERFDATA__PERF_NO | 72 | The performance ID |
| PERFDATA__PERF_CODE | 72 | The performance code |
| PERFDATA__TEXT1 | Text content | The text1 field at the performance level |
| PERFDATA__TEXT2 | Text content | The text2 field at the performance level |
| PERFDATA__TEXT3 | Text content | The text3 field at the performance level |
| PERFDATA__TEXT4 | Text content | The text4 field at the performance level |
| PERFDATA__DAY_NO_FULL | 23 | [DD] Day of the month for the performance |
| PERFDATA__DAY_OF_WEEK_FULL | Wednesday | Day of the week of the performance |
| PERFDATA__MONTH_NO_FULL | 11 | [MM] Month number of the performance |
| PERFDATA__MONTH_FULL | November | Full month name of the performance |
| PERFDATA__YEAR_FULL | 2050 | [YYYY] year of the performance |
| PERFDATA__YEAR_SHORT | 50 | [YY] year of the performance |
| PERFDATA__TIME_24HOUR | 20:00 | 24 hour time representation of the performance time |
| PERFDATA__TIME_12HOUR | 8:00 PM | 12 hour time representation of the performance time |
| PERFDATA__DT_1 | Nov 23 2050 8:00PM | Pre-formatted performance date and time |
| PERFDATA__DT_2 | 23 Nov 2050 | Pre-formatted performance date |
| PERFDATA__DT_3 | 23/11/2050 | Pre-formatted performance date |
| PERFDATA__PERF_DATE_1 | Nov 23, 2050 | Pre-formatted performance date |
| PERFDATA__PERF_DATE_2 | 11-23-2050 | Pre-formatted performance date |
| PERFDATA__COMPOSERFN | Wolfgang | Composer first name (if present) |
| PERFDATA__COMPOSERMN | Amadeus | Composer middle name (if present) |
| PERFDATA__COMPOSERLN | Mozart | Composer last name (if present) |
| PERFDATA__FACILITY_DESC | Autumn Ridge PAC | Facility description |
| PERFDATA__PROD_SEASON_NO | 23 | Production season number of the performance |
| PERFDATA__DURATION | 200 | Duration (in minutes) of the performance |
| PERFDATA__NUM_ACTS | 3 | Number of acts in the performance |
| PERFDATA__DOORS_OPEN | 3 | Doors open time |
| PERFDATA__DOORS_CLOSE | 3 | Doors close time |
Order Data
When a Performance-based Scheduled Trigger runs, the following fields are automatically created in your Prospect2 dashboard. The personalization tags can then be used for content personalization or segmentation.
| Token | Data Example | Details |
| ORDER__ORDER_NO | 123 | The order number with the performance in the reminder |
| CUSTOMER_NO | 1234 | The customer number on the order |
| ORDER__EADDRESS_NO | 1234 | The database id of the identified email address |
| ORDER__ORDER_DT | 2050-11-02 15:18:00 | The date and time of the order |
| ORDER__ORDER_DT_1 | Nov 2 2050 3:18PM | The date and time of the order |
| ORDER__ORDER_DT_2 | 02 Nov 2050 | The date of the order |
| ORDER__ORDER_DT_3 | 29/11/2050 | The DD/MM/YYYY date of the order |
| ORDER__NOTES | Sample order notes | Any notes populated in the order notes field |
| ORDER__DELIVERY_DESC | Hold at Box Office | The delivery method description for the order |
| ORDER__CUSTOM_1 | Any text in this custom field | Order Custom field 1 value |
| ORDER__CUSTOM_2 | Any text in this custom field | Order Custom field 2 value |
| ORDER__CUSTOM_3 | Any text in this custom field | Order Custom field 3 value |
| ORDER__CUSTOM_4 | Any text in this custom field | Order Custom field 4 value |
| ORDER__CUSTOM_5 | Any text in this custom field | Order Custom field 5 value |
| ORDER__CUSTOM_6 | Any text in this custom field | Order Custom field 6 value |
| ORDER__CUSTOM_7 | Any text in this custom field | Order Custom field 7 value |
| ORDER__CUSTOM_8 | Any text in this custom field | Order Custom field 8 value |
| ORDER__CUSTOM_9 | Any text in this custom field | Order Custom field 9 value |
| ORDER__CUSTOM_0 | Any text in this custom field | Order Custom field 0 value |
| ORDER__LSAL_DESC | Dr. John Smith | Your defined LSAL format for your Tessitura environment |
| ORDER__ESAL1_DESC | Dr. John Smith | Your defined ESAL1 format for your Tessitura environment |
| ORDER__ESAL2_DESC | Dr. John Smith | Your defined ESAL2 format for your Tessitura environment |
| FIRST_NAME | John | First name of Name1 of the patron account |
| LAST_NAME | Smith | Last name of the Name1 of the patron account |
| ORDER__FNAME2 | Jane | First name for Name2 on the patron acct |
| ORDER__LNAME2 | Smith | Last name for Name2 on the patron acct |
| STATE | NY | State value from patron's primary mailing address |
| ORDER__ZONE_NO | 12 | Zone ID from T_ZONE |
| ORDER__ZONE_DESCRIPTION | Mezzanine | Zone name from T_ZONE |
| ORDER__ZONE_TIME | 10:15 | Zone time value for timed admissions |
| ORDER__ZONE_START_TIME | 10:00 | Zone start time |
| ORDER__ZONE_END_TIME | 12:00 | Zone end time |
| ORDER__SECTION | Orchestra Front | Section description |
| ORDER__SEAT_INFO | B112, B114, B116, B118 | Comma-delimited string of row + seat numbers |
| ORDER__SLI_STATUS_ID | 12 | Order sub-lineitem status ID |
| ORDER__SLI_STATUS | Ticketed, Paid | Order sub-lineitem status description |
Using Web Content
Web content can be retrieved from the Title, Production, Production Season, or Performance level in Tessitura.
• Do not use any non-alpha characters: Non-alpha characters (&*%#’:”) will be stripped completely
• Do not use any spaces: Spaces will be replaced with an underscore.
Example: New WC With spaces & stuff becomes WC__NEW_WC_WITH_SPACES__STUFF
• Be advised personalization tags are case sensitive within campaign content, SMS, Site Messages, etc and will not populate if there is not an exact match.
You can use web content to populate more than just text fields within your email campaigns. You can populate an image by providing the image URL in the web content field in Tessitura, and then place the personalization tag within the image URL field in your email campaign, as you would any image URL.
Additionally, you can use valid XHTML in your web content and it will render the HTML in the email campaign in place of the tag.
Custom View Data
Custom View-based Scheduled Triggers are required to include the following columns in the exact format listed below. Any additional column titles you choose to include in your custom view can be used for personalization or segmentation. Custom fields and personalization tags that are created by custom view-based Scheduled Triggers will begin with CUSTOM__
| address | email@email.com | address is REQUIRED. This is the email address for the patron to which the custom reminder will be deployed. |
| custom_date | YYYY-MM-DD | custom_date is REQUIRED. This is the date that is used by the Tessitura Date Selection window in the automation. It must be in YYYY-MM-DD format. |