Tokens with Tessitura
|Suggested Skills: Tessitura|
|Objective: Email designs can be personalized for individual recipients by using tokens to populate custom field values. By utilizing information in Tessitura with output sets, there are even greater possibilities for the range of uses in your emails. mail2 fields use [straight brackets] and include the prefix "Contact." in the syntax of the token. See performance-based and order-based tokens in the bottom two charts.|
1. Always ensure your tokens are also in the plain-text version of your email. This is because the process to register valid tokens for both the HTML and plain-text versions are utilized through only one version, the plain text, although it will also register it for the HTML version. Your tokens will appear properly on both versions but this ensures your data will remain consistent.
2. All tokens are case-sensitive.
Tessitura System Tokens
These fields are automatically imported with every Tessitura import. This is defined in the SQL stored procedure: LWP_M2_GET_EXISTING_SEGMENT. Simply add or subtract from that table to change the default standard custom fields with each import. Otherwise, simply select an output set during your import to provide additional information on a per-import basis.
|[Contact.Customer_No]||123456||Contact's Constituent ID within Tessitura|
|[Contact.Source_No]||1234|| If list is promoted: source number associated with promotion.
If not promoted: m2DefaultSource in system table T_Defaults
|[Contact.prefix]||Mr.||The prefix of name 1 on the constituent record|
|[Contact.First Name]||John||First name of name 1 on the constituent record|
|[Contact.Last Name]||Smith||Last name of name 1 on the constituent record|
|[Contact.Email]||Johnsmith@email.com|| Email address of recipient.
If contact was added via Tessitura, this is determined by your email purpose, eaddress type and primary indicator settings during import.
For scheduled campaigns, mail2 searches for an email in these places (in order):
1. an email address associated with the order
2. an email address associated with the customer_no with the default address type as defined in m2DefaultEaddressType in T_DEFAULTS
3. an email address associated with the customer_no marked as primary
4. an email address of the primary affiliate with the m2DefaultEaddressType
5. an email address associated with the primary affiliate marked as primary
Remember to place these tokens in the correct syntax. For example, perfdata__title will be in your email campaign as [Contact.perfdata__title].
|perfdata__title||The Magic Flute||The title of the production|
|perfdata__perf_no||72||The performance ID|
|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||2011||[YYYY] year of the performance|
|perfdata__year_short||11||[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 2011 8:00PM||Pre-formatted performance date and time|
|perfdata__dt_2||23 Nov 2011||Pre-formatted performance date|
|perfdata__dt_3||23/11/2011||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__numacts||3||Number of acts in the performance|
Remember to place these tokens in the correct syntax. For example, order__order_no will be in your email campaign as [Contact.order__order_no].
|order__order_no||123||The order number with the performance in the reminder|
|order__customer_no||1234||The customer number on the order|
|order__order_dt_1||Nov 2 2011 3:18PM||The date and time of the order|
|order__order_dt_2||02 Nov 2011||The date of the order|
|order__order_dt_3||29/11/2011||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__fname||Mickey||First name of Name1 of the patron acct.|
|order__lname||Mouse||Last name of the Name1 of the patron acct.|
|order__esal1_desc||Dr. John Smith||Your defined esal_1 format for your Tessitura environment|
|order__prefix2||Mrs.||Prefix for Name2 on the patron acct.|
|order__fname2||Minnie||First name for Name2 on the patron acct|
|order__lname2||Mouse||Last name for Name2 on the patron acct|
|order__esal2_desc||Dr. John Smith||Your defined esal_2 format for your Tessitura environment|
|order__customer_type||Individual||The customer type of the constituent account|
|order__business_title||Lynch2||Business title tied to the customer_no|
|order__perf_no||72||Performance ID that made this order eligible|
Using Web Content
Web content can be used at the Title, Production, Production Season, and Performance level of a performance to extend the data available to insert into your campaign. You can re-purpose existing web content, or create new content and assign it to any level of the performance setup and it can be pulled and used automatically in your scheduled campaign. Web content is limited to 4000 characters.
- Do not use any non-alpha characters.
- Do not use any spaces.
- Tokens are case-sensitive, in mail2 all tokens will be lowercase.
mail2 automatically creates a token for use with your new content that begins with "wc__". If you have web content called TrafficAlert and you assign it to a show, the token to use with the content would be: [Contact.wc__trafficalert]. The web content name will be translated to all lower case for the token, and any non-alpha characters are stripped out. So, the web content name is TrafficAlert, but the token is [Contact.wc__trafficalert]. You can also use images to populate within a token. Simply include the image URL in the web content field in Tessitura, and then place the token within the image URL field in your email campaign, as you would any image URL.
You can use valid XHTML in your web content and it will render the HTML in the email campaign in place of the token.