Hello Tessiturians,
A little confused between emarket_ind (in T_CUSTOMER) and market_ind (in T_EADDRESS).
Both flag active primary email address as 'OK to emarket' yet both are different.
I've also discovered inconsistencies in our data between the two and wonder if we are missing a daily job or something to match them up?
Eg: emarket_ind.T_CUSTOMER = yes market_ind.T_EADDRESS = no
but related to the same email address?
Should we be matching up this data so that it is consistent? If so, what has priority over the other? T_CUSTOMER? or T_EADDRESS?
Any feedback appreciated,
Aaron WaapuMRC
These are always left up to the organization to decide with recommendations based on previous use.
Best practices would point to the EMarket Indicator on T_CUSTOMER to be the restriction on any online communication (email, social, etc) for the constituent. The market_ind on EAddress can be used as a more specific restriction, such as to differentiate between work (no marketing) and personal (marketing permitted) email addresses for a constituent. That being said, your organization’s specific business practices may determine their use in a different way.
=>Ryan Creps
@Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Aaron Waapu Sent: Tuesday, July 28, 2015 8:33 PM To: Ryan Creps <rcreps@tessituranetwork.com> Subject: [Tessitura Technical Forum] emarket_ind VS market_ind?
Aaron Waapu MRC
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!
To follow up what Ryan said, these are not meant to be kept in-sync because they refer to different things -- the T_CUSTOMER ind refers to the constituent's overall preference, and the T_EADDRESS ind can be set per-address when a constituent has multiple eaddresses. We try to follow this, and this means the T_CUSTOMER ind takes priority over anything else when pulling lists and extractions. As such, we've documented standard criteria and exclusions to use when pulling lists that respects these preferences.
Ahhh I see, I see. Makes sense. Thanks Ryan & Nick.
This is tricky. Because of the way Tessitura evolved, e-mail restrictions were attached to the account when, for many purposes, they really belong on the individual e-mail address. When people unsubscribe, it is sometimes because they don't want to hear from us, and sometimes because they no longer want to receive e-mails at a particular address. Some people will unsubscribe one e-mail address and, at the same time, subscribe with another one.
WordFly updates the T_CUSTOMER emarket_ind as part of its unsubscribe process, which to me is overkill. I use a procedure to update the e-mail address being unsubscribed to a type I set up called TMS-Unsubscribe, with the marketing indicator check box unchecked. That way, this address will not be selected by extraction. I then reset the T_CUSTOMER value so that if there are other valid e-mails in the record, they may be used, where appropriate.
In cases where patrons indicate they do not want to receive any e-mails from us, the T_CUSTOMER setting, of course, stays put.
Any time patrons add an e-mail to our system, either by subscribing or by purchasing tickets or some other form of interaction with our web site, they have the opportunity to mark that e-mail address with a "no mail to this address" e-mail preference.
Lucie