Triggered Emails for Concurrent Shows

Hi Kari - we at the Boston Symphony have concurrent shows all the time, so this is something we've run into as well.  We use Prosepct2 to handle this for us.  If you'd like to reach out to me for more, happy to go over with you.

Thanks

Mike

Hi Kari - at the National Ballet of Canada we run triggered, and dynamic, campaigns all the time via WordFly. Our productions tend to be straight runs but, for things like performance reminders and thank you emails, we often vary the content depending on the performance date they're attending. As long as your output set has a element that includes the ID of the production (or performance) they attended the previous day you should be able to dynamically change the content on the triggered campaign. On our performance reminders we have a custom element for "next performance". You could try creating one for something like "previous performance". After that it would just be a matter of using that ID as a key for a bunch of if/then statements in the email.

I'm happy to talk to you more about this if want to reach out directly.

Best,
Steve

Hi Kari,

We use WordFly and I have been reviewing our setup with Tessitura Consulting this week since we had a similar issue. Our performance reminders vary greatly between shows with different key artwork, partner restaurant offers, sponsors, etc. So we build unique campaigns and templates per production. Their recommendation was to use a filter on your output set that filters by production. So this means you'd need to make a different output set for each production running concurrently.

I'm still working this out for myself and can report back how it goes.

Gabriela

We also use Wordfly to manage our trigger emails, which we send every weekend. We don't have concurrent things running, usually just one performance per day and we use attendance season and attendance perf date. However, this won't work if your festival and mainstage are the same season. Our different offerings are set up as different seasons. The other way you could do it is to set up suppression list that you include in your email list. Doing it that way isn't as hands off, but it would allow you to suppress each performance from each other. We have pretty extensive notes about how to create trigger emails, if you'd find them helpful I'd be happy to share them with you.

Oh, interesting! I'm posting on behalf of our Marketing department and don't work directly with Wordfly so I will mention this to our Digital Strategy Manager!

That would be fantastic if you could let me know how it goes! Especially since you're also a theatre. :)

Our solution for The New Victory is to have a parameter for venue within each output set element, and then we have one output set per venue and run one (WordFly) triggered campaign for each. Some weekends, multiple campaigns run and cover all the audiences; some weekends, we only need the main stage one running.

On the content side, we build a blend of universal and dynamic elements (IF statements based on Venue name or whatever other data point applies) and are able to maintain just one Template (WordFly lingo again there) for the whole of the season. 

Kari Litteer (she/they) said:

I was wondering how everyone built triggered emails when you have concurrent shows happening?

We set up separate WF campaigns, with separate underlying SQL views, etc., per production.