Constituent E-mail Records - Bulk Updates and Best Practices

Hello all, 

I was wondering if a utility exists for updating e-mails on a household to each individual record on that household? Ever since implementing Tessitura, we have made it a point to consistently keep the A1 and A2 records up-to-date, and ensure that the correct A1 and A2 emails show up in contact details for the household. But what we would like to do is make sure that the emails also exist in the individual record for each constituent, starred as the primary for the individual. That way when we pull exports for marketing, we can pull lists by the primary email and it doesn't matter if A1 and A2 from the same house are on two separate lines - we're just going to be copying the column and pasting it into our email service. 

If anyone has ideas or best practices or tips from lived experience with these issues I'd be so grateful to hear them - thanks!

Parents
  • Unless you've changed it, the output sets for email address ought to pull the household primary eaddress for an affiliate if the affiliate lacks one.  Also, Wordfly and most mailing houses are only going to send one email to any specific address, so whoever comes up first in your list will get the email (assuming both are getting the same email address from the household), i e. personalization like Dear ________, and the second affiliate on the list will receive nothing.

  • "Unless you've changed it, the output sets for email address ought to pull the household primary eaddress for an affiliate if the affiliate lacks one" - Gawain, do you how to change this setting, one way or the other? 

    We've been going back and forth on where the e-mails should live - on the household, or on the individual record. And what we've arrived at is that it should probably be both. A1 and A2 should live on the household, probably with A1 flagged as primary, and then on their respective individual records, marked as primary on their individual records. 

    This way, development can run lists and extractions for mass mailings with A1 and A2 on the same line for a household. And then marketing can run lists and extractions by individual record. 

    The problem is, marketing is getting dupes when an A2 record doesn't have an email address at all, or one marked as primary. It's pulling in the A1 address from the household, and that creates two records in a column with the same email address and marketing needs to go through and manually update those to keep mailing lists clean and dupe-free. 

Reply
  • "Unless you've changed it, the output sets for email address ought to pull the household primary eaddress for an affiliate if the affiliate lacks one" - Gawain, do you how to change this setting, one way or the other? 

    We've been going back and forth on where the e-mails should live - on the household, or on the individual record. And what we've arrived at is that it should probably be both. A1 and A2 should live on the household, probably with A1 flagged as primary, and then on their respective individual records, marked as primary on their individual records. 

    This way, development can run lists and extractions for mass mailings with A1 and A2 on the same line for a household. And then marketing can run lists and extractions by individual record. 

    The problem is, marketing is getting dupes when an A2 record doesn't have an email address at all, or one marked as primary. It's pulling in the A1 address from the household, and that creates two records in a column with the same email address and marketing needs to go through and manually update those to keep mailing lists clean and dupe-free. 

Children
  • "Unless you've changed it, the output sets for email address ought to pull the household primary eaddress for an affiliate if the affiliate lacks one" - Gawain, do you how to change this setting, one way or the other? 

    The standard Email Address Output Element pulls from dbo.FT_GET_EADDRESS().  This pulls the primary EAddress for the customer_no provided, and if one does not exist the primary the household, if it is a primary affiliate, and if not it looks for non-primary active eaddresses in the same sequence.

    (That's not actually true, it's also potentially screening against EAddress Types and Contact Point Purposes and more, but 99% of the time...)

    You could create your own Output Set Element where you don't look to the Household.  The downside of this is that I'm not sure a custom Output Set Element is going to work with Contact Point Purposes, if you use those.

    We have something of the reverse problem, where we simply want to transact with the HH 99% of the time, but have a tiny number of constituents where both affiliates want to get separate communications.