Categorized in: 

MEC Weekly Digest | November 7, 2022

Campus User Groups

  • Anschutz: In response to a survey to Anschutz users, Jason Thomas and team kicked off monthly lunch and learn sessions. Checkout the presentation and recording from the well attended Sept. session on email best practices.
  • UCCS: Kayla Gronseth Boyer and Eric Nissen have also been hosting monthly lunch and learn sessions. Checkout materials from the Sept. session to review email and event best practices including three checklists for quick reference:

Super Users

  • Update: As mentioned in the Oct. MEC meeting, we are exploring increased, specialized user access for high-frequency users to alleviate eComm specialist tasks.
    • Manage Campaigns: If a Report or Data Extension is based on a Salesforce Campaign and requires frequent, small changes, all Salesforce users can manage Campaign Members (and even add new contacts) without involving an eComm specialist
    • Cvent Portal Manager: Users who regularly need Reports published to the Portal can have Cvent Portal Manager access. We've reached out to good candidates based on the number of Reports currently published to the Portal. Let know if you have a user in mind that hasn't been identified.
    • Cvent Event Approval (free): As a pilot, users who have hosted more than 10 free events in the last 6 months have been invited to a Nov. 14th session to review the Cvent approval checklist and get access to approve events. If all goes well we will expand to another group; users who have hosted more than 8 free events in the last 6 months.

Access to Submit License Changes

  • Action: As follow-up from our Sept. MEC meeting, eComm specialist who are responsible for license changes need access to the work-flow in Salesforce to complete this task. Access will be granted after reading the license change wiki and passing a short quiz.

CRM Team Structure Changes 

  • Update: eComm specialists and stakeholders received an email from Aaron Mansfield regarding changes to the CRM team structure in UIS. 
  • Summary: UIS has traditionally been divided into two reporting structures: service strategy (where me, Mel, and Lauren have been housed) and service delivery (where Jeff, Claire, and Daniella have been housed). Our new CRM team structure brings all of us under the same team umbrella to increase efficiency. See org chart below.
  • Jen Mortensen's New Role: Jen will be serving as Interim Director of CRM in addition to her current eComm responsibilities (some of which Mel and Lauren are graciously taking off my plate).
  • New Service Areas: This change brings multiple CRM-related service areas under one umbrella so we can more effectively address the holistic nature of CRM. UIS services now under the CRM team umbrella include assessment and analysis, technical implementation, marketing strategy, copywriting, graphic design, web experience, and user enablement.
  • Overall CRM Landscape: This change will also give eComm a more prominent seat at the table in conversations surrounding various CRM implementations both enterprise-wide and at the campus level. We're excited about the opportunities that this change presents to work more strategically together in the larger CU CRM context.

Marketing Cloud: Datorama now 'Intelligence Reports' 

  • Datorama Overview: While functionality has remained the same, Datorama has been renamed to 'Intelligence Reports' (found under Analytics Builder). 

Ongoing Opportunities

  • Einstein: Big thanks to Lauren Galena for providing a real-time overview of Einstein at our Oct. MEC meeting. The recording has been published to the wiki and we'll continue to explore Einstein's capabilities based on activation in several business units.
    • Users in a Business Unit with Einstein enabled will receive an invitation for an overview on Tuesday, Nov. 15 from 11-11:30 AM. 
    • If you'd like to have Einstein enabled in a specific business unit, add details to the Request Einstein spreadsheet by submitting a help ticket and selecting "Marketing Cloud >> Einstein" (no need to actually submit the ticket). 
  • Journey Builder: Big thanks to Claire Hamilton for providing three examples of current Journey Builder pilots at our Oct. MEC meeting. The recording has been published to the wiki and the team is eager to explore additional use cases. Find next steps by submitting a help ticket and selecting "Marketing Cloud >> Journey Builder, Dynamic Content or Automation Studio" (no need to actually submit the ticket).
  • Dynamic Content: Resources for Dynamic Content are now available and MECs or users are welcome to work directly with Melanie Jones to implement their use cases. With their access, MECs can leverage Dynamic Content on their own.
    • If you'd like to work with Melanie Jones on a Dynamic Content example, add details to the Dynamic Content spreadsheet by submitting a help ticket and selecting "Marketing Cloud >> Journey Builder, Dynamic Content or Automation Studio". 

New/Updated Wikis and Resources

Ongoing Data Monitoring