1741 Release - 2017-10-12

We developed and recently released a way for our Implementation team to augment and configure the logic we use to pick the best attributes for mastercustomers (ie deduped records representing multiple “child records”), out of the attributes available in their child contact records. This is now available for the group of attributes below (the groups are designed to make sense and ensure consistency of information) . Please contact your IPM if you would like to discuss the logic with which those attributes are picked today (and whether you would like to change it).

• Email attributes group : the following fields are picked together from the same child record which contains the best information (for those attributes at least), according to a configurable logic : EmailAddress, DoNotEmail (and the derecated Preferences field), EmailStatus.
• Phone attributes group : the following fields are picked together from the same child record which contains the best information (for those attributes at least), according to a configurable logic : PrimaryPhone, SecondaryPhone, MobilePhone, DoNotCall.
• Address attributes group : the following fields are picked together from the same child record which contains the best information (for those attributes at least), according to a configurable logic : Address1, Address2, Suite, Zip, ZipExt (the +4), City, State, Country, CountryCode, Certified, DPVConfirm, DoNotMail, NCOADateUpdate, MoveType, MoveDate.
• Personal information attributes group : the following fields are picked together from the same child record which contains the best information (for those attributes at least), according to a configurable logic : FirstName, MiddleName, LastName, Gender, Title, Salutation, Age, BirthDate, BirthYear, BirthMonth, DoNotText.