Best Practices for Tnew and Mail2 Integration

We're starting our implementation of Tnew and Mail2 and are wondering the best ways to integrate the system and acquire email addresses. So far we are looking at using Interests or the Mailing List Preference Tab. Does anyone have experience with these that could tell me some of the positive or negatives for each method?

This is my first time posting (new to Tessitura), so I hope this is in the right place!

Thanks,
Grace

Grace Geller
American Repertory Theater | Marketing and Communications Manager

 

Parents
  • Hi Grace,

    We decided against using the embedded Mail2 Subscription centre in the TNEW Mail Preferences tab for a) aesthetics and because b) hardly anyone was using it, anyway.

    In relation to Interests, we use them on our TNEW sign up form.  A stored procedure runs nightly which adds an attribute and attribute value to the constituent record which we can then use to pull lists.  This works for our business needs because we are a national presenter and have 7 versions of e-news which is geography specific and the attributes and values help us manage this.  To the outside world, it looks like we just have one e-news list. Having a different interest for each location wasn't the most appealing choice for us.  Another procedure updates the attribute value so we don't email the patron accidentally if s/he opts out using the Mail2 subscription centre.

    As Christopher said, Interests are not tied to Mail2 lists.  Since Mail2 public/private lists and the email addresses they contain are stored in local SQL tables, it would be easy to create a procedure(s) to do something similar to what we have plus update mailing restrictions/preferences in the constituent record if someone unsubscribes from a list or "Globally Unsubscribes".

    Cheers,

    Kevin

Reply
  • Hi Grace,

    We decided against using the embedded Mail2 Subscription centre in the TNEW Mail Preferences tab for a) aesthetics and because b) hardly anyone was using it, anyway.

    In relation to Interests, we use them on our TNEW sign up form.  A stored procedure runs nightly which adds an attribute and attribute value to the constituent record which we can then use to pull lists.  This works for our business needs because we are a national presenter and have 7 versions of e-news which is geography specific and the attributes and values help us manage this.  To the outside world, it looks like we just have one e-news list. Having a different interest for each location wasn't the most appealing choice for us.  Another procedure updates the attribute value so we don't email the patron accidentally if s/he opts out using the Mail2 subscription centre.

    As Christopher said, Interests are not tied to Mail2 lists.  Since Mail2 public/private lists and the email addresses they contain are stored in local SQL tables, it would be easy to create a procedure(s) to do something similar to what we have plus update mailing restrictions/preferences in the constituent record if someone unsubscribes from a list or "Globally Unsubscribes".

    Cheers,

    Kevin

Children