To those on Mail2: Are all email restrictions stored only on the Mail2 custom tab after migration or do you also store them on mail purposes? I'm wondering where restrictions are stored for emails not loaded into Mail2 such as older records with no recent transactions. If they are kept in both Mail2 and mail purposes, how do you ensure users update them in both places? Or, do you have a procedure that syncs opt-out changes in Mail2 with email purposes and vice versa? Is it still possible to pull lists based on restrictions if they are only in the Mail2 custom tab?
Thank you in advance for the feedback.
Chuck Buchanan
92nd Street Y
What I did when we went live with mail2, is I did an extraction on all of my e-marketing restrictions folks in Tessitura and then imported them into mail2 as unsubscribed. This synched them up on the mail2 custom tab.
This is helpful for us as well, thank you! We were wondering if, once you are fully integrated with Mail2, do you still mark folks as email restriction in Tessitura, or do you only mark them in Mail2?
I'm now working at the New York Philharmonic where we also use Mail2. We have a stored procedure here that runs in the background syncing Constituents within Tessitura marked "Do Not Email" with Email addresses in the Mail2 dashboard marked "Global Unsubscribe". This solution is not ideal as Mail2 operates on an email addresses level and Tessitura operates on an individual/constituent ID level. Meaning if I have 3 email addresses and globally unsubscribe from 1 through an email campaign my entire Tessitura account will receive the "Do Not Email" contact restriction, rather than that one particular email address I intended. There might be a better solution for this in version 12 with the ability to add purposes to email addresses ...
Slight typo - I meant if there is an ability to add contact restrictions by email address in the future this could be useful. There currently are purposes for email addresses.