Campaign config for performing arts orgs

Hi Nick,

Here at 92Y we use separate campaigns for each of our program areas, creating new campaigns for every fiscal year.  For example, 16 School of Arts, 16 School of Music, 16 Harkness Dance Center, etc..

For fiscal year 16, we 35 different campaigns for ticketing only.  We use the same campaigns for Subs and single ticket sales together.

The only canned campaign reports we use for ticketing is the Revenue by Source and Appeal and the Appeal Response reports.  The other canned Campaign reports are primary used for Development. 

Hope this helps,

Tatiana

Tatiana Jofat

Director, Tessitura Support

P: 212.415.5481 | F:212.415.5788

92^nd St Y, 1395 Lexington Avenue, New York, NY 10128

92Y.org  | Facebook | Twitter

From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nick Reilingh
Sent: Monday, April 11, 2016 3:09 PM
To: Tatiana Jofat
Subject: [Tessitura Ticketing Forum] Campaign config for performing arts orgs

Hi folks -- cross-posting this to Finance for visibility.

Wondering what some typical configurations look like out there in the performing arts org world. For ticketing campaigns, the examples I am most familiar with have one campaign for single ticket sales for the entire fiscal year, and another campaign for subscriptions, another for fees, and that's basically it. But I'm starting to think this is more typical for organizations that just produce one type of event year-round, like opera houses or symphonies.

For orgs that produce a wide variety of events, how do you structure your campaigns for ticketing? One campaign for the entire FY? One for each season of events? Or more granular, like one for each series of productions, or even one campaign per production? Separate campaign for subs, or no?

It would be great to get some quick feedback from a few people. If you want to offer more, how much value would you say you get out of the canned campaign reports with regard to your configuration?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Nick,

Here at 92Y we use separate campaigns for each of our program areas, creating new campaigns for every fiscal year.  For example, 16 School of Arts, 16 School of Music, 16 Harkness Dance Center, etc..

For fiscal year 16, we 35 different campaigns for ticketing only.  We use the same campaigns for Subs and single ticket sales together.

The only canned campaign reports we use for ticketing is the Revenue by Source and Appeal and the Appeal Response reports.  The other canned Campaign reports are primary used for Development. 

Hope this helps,

Tatiana

Tatiana Jofat

Director, Tessitura Support

P: 212.415.5481 | F:212.415.5788

92^nd St Y, 1395 Lexington Avenue, New York, NY 10128

92Y.org  | Facebook | Twitter

From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nick Reilingh
Sent: Monday, April 11, 2016 3:09 PM
To: Tatiana Jofat
Subject: [Tessitura Ticketing Forum] Campaign config for performing arts orgs

Hi folks -- cross-posting this to Finance for visibility.

Wondering what some typical configurations look like out there in the performing arts org world. For ticketing campaigns, the examples I am most familiar with have one campaign for single ticket sales for the entire fiscal year, and another campaign for subscriptions, another for fees, and that's basically it. But I'm starting to think this is more typical for organizations that just produce one type of event year-round, like opera houses or symphonies.

For orgs that produce a wide variety of events, how do you structure your campaigns for ticketing? One campaign for the entire FY? One for each season of events? Or more granular, like one for each series of productions, or even one campaign per production? Separate campaign for subs, or no?

It would be great to get some quick feedback from a few people. If you want to offer more, how much value would you say you get out of the canned campaign reports with regard to your configuration?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!