Hi,
We get our email list subscribers from MailChimp (MC) as the other department in our org uses MailChimp and we depend on that department for user list. Usually, I import the MC list on Tess and I update the MC list wth unsubscribes from Wordfly. We email our newsletter once a month
Recently, I noticed that we have users who unsubscribe from MC list and since Tess and MC don't communicate, this poses an issue. I created a list of users whose email restriction needs to be updated to "Do Not Email". How do I bulk update email restriction?
Thank you for your help!
Polliana
Hi Polliana,
We also use a non-integrated email system, and I’ll do bulk updates using a bit of SQL code. If you have a DBA, it should be super simple for them to do.
Cheers,
Kathleen
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Polliana Mendonca Sent: Tuesday, February 14, 2017 10:50 AM To: Kathleen Smith Subject: [Tessitura Development Forum] bulk update email restriction
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!
I think it depends how your organization tracks contact restrictions. If it’s on the bottom right of the general tab in the constituent you would need a DBA to bulk update those constituents on the back end. If you use attributes there is an out-of-the-box Tessitura utility to update attributes- you can find it on here by searching “Manage Attributes Utility”. This is assuming you have constituents identified in Tessitura already as a List Manager list but if the file is coming from MailChimp without Constituent IDs you’d first need to either use the “Constituent Import Utility” to get them into Tessitura which also offers an option to add an Attribute in the process. (Or again you could also have your DBA import the list on the back end matching by email address.)
Hope this helps!
Chuck
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Polliana Mendonca Sent: Tuesday, February 14, 2017 10:52 AM To: Buchanan, Charles Subject: [Tessitura Development Forum] bulk update email restriction
Hi Kathleen,
Thank you for your help. I'll ask the DBA to work on it.
Hi Charles,
I have managed to map the list with the Constituent ID so the email addresses have an ID and I imported the list on Tess. The unsusbribes are tracked using the email restriction feature and not Attributes.
Our Wordfly updates the email restriction when someone unsubscribes from our newsletter. If I use attributes as a way to restrict email communication, can wordfly also update that attribute?
Thank you,
Ok, that makes sense and you're right Wordfly defaults to update the general tab contact restriction. If that's working for you I'd probably stick with that over moving to an attribute. It just means you’ll need your DBA to do any bulk updates. But also theoretically you could change the
LP_UPDATE_EMAIL_PROMOTION stored procedure which handles the Wordfly unsubscribes and brings them to Tessitura to point to an attribute or really anywhere in Tessitura.
Details here: https://support.wordfly.com/hc/en-us/articles/204768424-LP-UPDATE-EMAIL-PROMOTION-Stored-Procedure
I forgot to mention that we are moving to use the contact point purposes instead of the general tab or attributes because these are attached to specific email address. The benefit is you don’t have a constituent unsubscribed, you have an email address and you know which email address if the constituent has multiple. We also have run into the need for a quick way to bulk update a list of constituents with CPPs so we are working with our DBA to build a custom utility to do that. You could also look at doing this for your contact restriction if there is going to be a need to do this ongoing vs always sending it to be done by the DBA on the back end.
All the best,
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Polliana Mendonca Sent: Wednesday, February 15, 2017 10:29 AM To: Buchanan, Charles Subject: RE: [Tessitura Development Forum] bulk update email restriction