• Replies 4 replies
  • Subscribers 338 subscribers
  • Views 62 views
  • Users 0 members are here
Related

emarket_ind VS market_ind?

Aaron Waapu
$organization

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 Waapu
MRC 

 

Parents
  • $organization

    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.

Reply
  • $organization

    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.

Children