When faced with a failed send, a send to 0, or failed Data Extension, review the items below. Often, the root cause is something over which you have control rather than a systemic failure in Salesforce or Marketing Cloud. If there is an outage or broad issue, users will be notified as soon as possible.
Person of Interest or POI data is used for Contacts with a non-traditional, close affiliation with CU. As of March 2023, POIs make up 32K+ Contacts. Some examples include Security / Training, Volunteer and Student Athlete.
Have an email in full HTML but want to send it from Marketing Cloud? It's doable (not to mention a great approach), but it must be approached a certain way to ensure CAN-SPAM compliance, including a footer for recipients to opt-out. Find details on how to test the recipient's experience, instructions on how to create an HTML email correctly, and the most common misstep we come across.
Reports can often have the same contact listed numerous times, so identifying the unique count is important to confirm the Report criteria is accurate. Having a total 9,000 unique contacts when expecting 250 is an indicator of incorrect criteria and should be investigated.
Does a contact need to start (or stop) receiving a communication of yours? If your Report or Data Extension is based on a Salesforce Campaign, users can manage Campaign Members and create new Contacts when needed. Those audience changes will be reflected the next time the corresponding Report is sent to or Data Extension is started. It's a great way for users to continually manage small changes to an audience, without involving an eComm specialist.
For organizations with a large number of Salesforce users, Public Groups optimize performance and bring efficiency. Given eComm's 300 person userbase with an average of 20 new licenses each month, we couldn't manage without them.
While Cvent has a feature to "allow partial payments," we never want to enable it. Collecting credit card information to process part of the payment now and the other portion at a later time doesn't align with CU's approach to protecting cardholders and it should not be enabled under any circumstances. The good news is, by default, this setting is disabled across all events and most users remain unaware of this functionality. Follow these instructions to confirm your paid event doesn't have this feature enabled.