Creating a Performance-Based Tessitura-Integrated Scheduled Campaign

Knowledge Level: 
Time: 15 minutes
Suggested Skills: Tessitura
Objective: A performance-based, Tessitura-integrated scheduled campaign is a great way to manage performance-specific reminders and follow-ups efficiently and effectively. Due to the varied ways in which arts organizations structure their productions and performances, there are many different ways in which you can implement performance-based scheduled campaigns. This article provides a basic outline of elements and steps to consider when building your campaign. If this article does not answer your question(s) contact or consider building your campaign as a custom-view based scheduled campaign.

The elements of a Performance-based Tessitura-integrated Scheduled Campaign include:

  • The Associated Draft Campaign (design)
  • Keywords
  • Pricetypes
  • Schedule

Before we go into the steps of creating a performance-based campaign, let's review each element and how they contribute to the overall campaign.

The Associated Draft Campaign

This serves as the design of the email campaign your patrons will receive. You can use tokens to produce personalized content specific to the recipient. For example [Contact.First Name] can be used to include their first name, as well as Tessitura specific information like performance title, date, time and location, saving you potential hours per week through automation rather than manual updates! Learn more about tokens and Tessitura. Additionally, you can utilize Dynamic Content within your scheduled campaigns to further segment your audience, allowing you to target messaging only to the appropriate contacts. 


You can use one or multiple keywords separated by commas to limit the performances in which your scheduled campaign will pick up. For example, if you in input a keyword of "Broadway" that you have set up in Tessitura and applied to some performances, only those performances with the "Broadway" keyword will be selected when this scheduled campaign job runs. If you input a comma-separated string of keywords in the field above to suppress performances with certain keywords, then the combination of keyword fields will be used to determine which performances are selected.


You can use one or multiple pricetypes separated by commas to limit the orders in which your scheduled campaign will pick up. For example, if you in input a pricetype ID of 55 that was used for orders in Tessitura, only those sub line-items using pricetype 55 will be selected when this scheduled campaign job runs. If you also input a comma-separated string of pricetype IDs in the field above to suppress order SLIs with certain pricetypes, then the combination of pricetype fields will be used to determine which orders are selected. Mixed orders with pricetypes and suppressed pricetypes are totally suppressed in this evaluation, meaning if an order has some SLIs with an included pricetype, and some SLIs with the suppressed pricetype, the order is suppressed. 


Your performance-based campaign can run once on a daily, weekly or monthly basis at the top of any hour. Your Tessitura Date Selection Window will ultimately determine which performances are pulled for every deployment. 

To get started, go to Tessitura Integration > Scheduled Campaigns > Create New Scheduled Job


Give the scheduled job a name


Select Performance-Based type from the dropdown menu


Provide any keywords or pricetypes (optional)


Associate the draft campaign with the scheduled job.


Select the hour in which to send individual deployments.


Select the frequency of individual deployments.


If weekly or monthly is selected in Step 6, select day of week or day of month.

If daily is selected, you can skip this step as daily will run every day.


Set your Tessitura Date Selection Window

This is the interval of time before or after a performance in which the scheduled job should run for individual deployments. It determines which performances the scheduled job considers within your criteria. For example, assuming the above scheduled job will run today, it will consider performances that are scheduled for tomorrow. It is tomorrow because the formula is [Today] + [1]. If this should be a performance follow-up, rather than a reminder, you would insert a negative number (like -1) and the formula will pull performances scheduled yesterday because the formula is [Today] + [-1]. You can always use the 'Test Window' to determine which day(s) the date selection window contains. 

Still need help? Contact Us Contact Us