Let us help you navigate the resources in the eComm wiki so you can get the answer you're looking for when you need it. Select the eComm application for which you have a question (Salesforce, Marketing Cloud, or Cvent) and then view resources by category. Can't find what you need in this wiki? Submit a help ticket at cu.edu/ecomm/submit-help-ticket.
Often when a Contact is not receiving emails, there are several logical reasons why, including actions taken by constituents themselves. If you are investigating why a Contact is not receiving communications, review the steps below to troubleshoot.
A crucial role of an eComm Specialist is to create audiences. Before diving into the multi-step process, it's important to have a basic understanding of terminology and the end-user experience.
Want to continually grow an audience you can email via Marketing Cloud? eComm can provide a simple subscription form along with a Salesforce audience that will update automatically with subscribers (thanks to a behind-the-scenes integration). Users can add the subscription URL to their website then send emails to that audience as desired.
One of the eComm specialist’s roles in Cvent includes managing how stakeholders can access Cvent data in real-time, without a steep cost. Follow the steps below to create Portal Users and Publish Reports there for easy access.
Learn how to create a Data Extension as you typically would, then Import the data from a file (rather than 'start' it). Just remember, you'll need the Contact 18 ID to Import successfully.
Learn about the information required to add/modify/delete email preferences and what you'll be responsible for managing once edits are complete.
Learn how you'll be notified about eComm outages and unplanned maintenance. Salesforce users can set their own Salesforce Chatter Notifications and Post in Salesforce Chatter.
Learn about the information required to add/rename/delete a business unit and what you'll be responsible for managing once complete.
By implementing a simplified Marketing Cloud business unit and preference model across all campuses, the eComm team will reduce costs, streamline the constituent experience, and decrease the level of backend management needed. The current model has 151 business units and 373 associated preferences. This project aims to reduce these numbers by at least 50%.

Pages