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.
Salesforce rolls out updates every quarter. Find a summary of updates that impact eComm along with a link to the full release notes.
Salesforce is at the heart of eComm, but it would be nothing without other systems across CU. Most of eComm's Salesforce Contacts come from a nightly updated source system, enriched with engagement data from eComm's other applications (Marketing Cloud & Cvent), constituents, and eComm Specialists.
When you launch your event, Cvent integrates with Salesforce to automatically share registrant participation information. Cvent then provides numerous methods for tracking attendance for your event or sessions. Use this insightful, actionable data to make your next event even better!
Track attendance for your event or sessions by marking who showed up. With Cvent, you can mark them one at a time, import a list of participants all at once, or use OnArrival to mark participants onsite.
Interested in being part of a collaborative community devoted to eComm? Start by updating your Chatter Group(s) email frequency and you'll receive posts via email (i.e., every post, daily digest, or weekly digest). There is one group devoted to Marketing Cloud & Salesforce and a second group for Cvent.
Interested in creating your own Salesforce Dashboard? Learn about considerations and next steps.
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 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.
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