Personalized E-blasts

Hi everyone,

Our Development office would like to create an email message to our patrons that refers to them as Donors, or Subscribers, or board members or certain other (selected) Constituencies.  

They plan to use Constituency Codes to determine how each patron is referenced and they have ranked the Constituency Codes accordingly.  They will Extract the patrons with an Output Set that pulls the Codes (after we add Constituency Codes to Ouput Sets).

Do any of you have experience in personalizing e-blasts in this way?   Some people are concerned that we are limited to referring to a patron as either a benefactor or a subscriber (when they are both).  I don't know if that will be an issue or not but would be  very interested to know how other organizations personalize their e-blasts.  Thank you.

Debby

Parents
  • We have done a number of different personalized emails using TMS. It's really quite easy, you just need to make sure that the data you have is clean. Is there any particular reason why you aren't considering a Prefix, First Name, Last Name type personalization? It would avoid the issue of patrons having multiple consituencies all together. The coding with TMS is very simple, you just need to link up the data from your output file to the code in the email. We also use this for inserting membership level, membership donation amount, membership increase donation amount etc. On the ticketing side we use this to provide different offers (so 10%, 15%, 20% etc.), different paragraphs of text to address members and non members all within in one email. This prevents us from having to create multiple emails to address all the different variables.

    I'd be happy to share more if you'd like. Feel free to email me.

    Paula

Reply
  • We have done a number of different personalized emails using TMS. It's really quite easy, you just need to make sure that the data you have is clean. Is there any particular reason why you aren't considering a Prefix, First Name, Last Name type personalization? It would avoid the issue of patrons having multiple consituencies all together. The coding with TMS is very simple, you just need to link up the data from your output file to the code in the email. We also use this for inserting membership level, membership donation amount, membership increase donation amount etc. On the ticketing side we use this to provide different offers (so 10%, 15%, 20% etc.), different paragraphs of text to address members and non members all within in one email. This prevents us from having to create multiple emails to address all the different variables.

    I'd be happy to share more if you'd like. Feel free to email me.

    Paula

Children
No Data