bulk update email restriction

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

Parents
  • 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,

     

    Chuck

     

     

     



    Charles Buchanan
    Manager, Database Marketing & Analysis
    New York Philharmonic
    David Geffen Hall
    10 Lincoln Center Plaza
    New York, New York 10023
    Office:
    212-671-4899
    nyphil.org

     





    The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender and destroy any copies of this information.

    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

     

    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,

    Polliana

Reply
  • 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,

     

    Chuck

     

     

     



    Charles Buchanan
    Manager, Database Marketing & Analysis
    New York Philharmonic
    David Geffen Hall
    10 Lincoln Center Plaza
    New York, New York 10023
    Office:
    212-671-4899
    nyphil.org

     





    The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender and destroy any copies of this information.

    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

     

    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,

    Polliana

Children
No Data