MEC Weekly Digest | January 20, 2020
Duplicate Resolution Update
- Update: Lisa Carr and Lynn Cornier at the COE have been working with teams from UIS and Advancement to identify and begin resolution on more than 40,000 duplicate contacts. These duplicates were identified as contacts that had multiple records for a single campus name and email but separate records containing Advance ID, student ID, or employment ID.
- Progress: To date, the team has merged 29,471 contacts. The survivor record is the record that was generated from HRMS and/or Campus Solutions. An additional 11,596 are continuing to be actively investigated and verified prior to a merge.
- Other Duplicates: Duplicates that are not Advancement-related will be addressed once this project is complete. MECs can continue to add duplicates to the DCR spreadsheet for processing if they believe the duplicate will not be caught based on the criteria of the project above. Please send questions or concerns to Jennifer or Daniella.
Salesforce and Marketing Cloud Connector
- Update: SFMC believes that the discrepancies we are seeing between Salesforce and Marketing Cloud (see January 13 weekly digest) are due to issues with connector. A fix has been identified, and the COE hopes to implement and test next week. We will provide more information as soon as it becomes available.
Campaign Report Upload for MC
- Issue: MECs use the Campaign Report Upload for MC functionality on a regular basis but sometimes forget to update the associated report criteria for their own campus/department.
- Impact: Reports are created that contain incorrect filters and email preferences.
- Solution: Daniella updated the report description to help remind us of what we need to edit: "Please replace CU President News and SYS Email with your Campus/Department. Replace Meets eComm Contact Criteria with Deceased for transactional reports. **Do not delete** This report is used on the campaign record to run a campaign member report."
Transactional Email Logic
- Issue: The System team has noticed that some transactional reports are being built incorrectly and are therefore not actually transactional.
- Solution: When building a transactional report, please structure your report logic as follows:
- REMOVE Meets eComm Contact Criteria
- ADD Deceased = False
- Ensure that no email preference categories are selected
Salesforce Field "Email Present?"
- Issue: The System team has noticed that some MECs are using the Email Present? field to try and limit the number of records that appear in reports. While the Email Present? field is included in Salesforce report templates, it is designed to be used as a placeholder only (see training materials for commercial and transactional reports).
- Solution: MECs should replace the Email Present? field with the associated email field for their communication.
Email Preference Requests for Q1 of CY20
- Update: Thanks to all of you who submitted your email preference requests to the COE for consideration in Q1 of CY 2020. Nalini has reported that requests have been approved. We don't have a firm deadline for completion of the work, but it's safe to expect sometime in March near the end of Q1. If you submitted a preference request, please double check the spreadsheet to ensure that everything is accurate before work begins.
- Update: Discover Reports in Marketing Cloud are now available for all users. The System team plans to announce this in the January eComm newsletter. For those of you who have not yet reviewed information on Discover Reports, please see the Discover Reports in Marketing Cloud wiki.