Email Deliverability in Salesforce Marketing Cloud: Why Reach Is a Strategic Business Requirement

An organization can carefully segment its campaigns, design customer journeys, and invest substantial amounts in marketing technology. However, the commercial value of that investment remains limited when messages do not reach their intended recipients. Email deliverability therefore deserves a place in the governance of Salesforce Marketing Cloud, alongside decisions about data, content, and automation. After all, reach affects not only campaign performance, but also the reliability of customer communications and management information. For European B2B organizations, this issue is more complex than the percentage of messages sent might suggest. Emails pass through public mailbox providers and corporate security gateways, while local teams and external applications may communicate on behalf of the same brand. A change in domain settings or sending patterns can therefore affect multiple countries and business units. Anyone assessing only one campaign often recognizes those interdependencies too late. The question for leadership is what proportion of the commercially relevant audience remains reachable and which processes depend on that reach. It also raises the question of who is responsible when the quality of the sending chain deteriorates. Salesforce supports sending and monitoring, but the organization determines how domain management, contact policies, and follow-up are organized. That interdependence makes deliverability both a management and an operational responsibility.

Delivered Does Not Mean Visible in the Inbox

A sending report can paint a reassuring picture when few messages bounce immediately. However, technical acceptance does not prove that the recipient saw the message in the inbox. A receiving server can accept a message and then send it to a spam folder or quarantine. As a result, reach problems can remain invisible in a report that shows only sent and accepted messages. Salesforce explicitly makes this distinction for Account Engagement. A delivered status means that the receiving server has accepted the message. The receiving environment then determines what happens to it. In Marketing Cloud Engagement, delivery problems can also become apparent after initial acceptance. For management reporting, this requires separate interpretations of acceptance, possible inbox placement, and response. A campaign with little response may be insufficiently relevant, but filtering or limited reach may also play a role. These possibilities require different investigations and different measures. Changing a subject line, for example, will not correct an error in domain authentication.

An organization can assess its marketing investment only when it understands what proportion of its intended audience it can actually reach.

Reputation Develops Across the Entire Sending Chain

Receiving parties evaluate emails using various signals, including authentication, domain and IP reputation, sending patterns, and complaints. Correct technical configuration can support trust, but it does not guarantee inbox placement. Audience quality, frequency, and relevance also influence how communications are received. Sender reputation therefore develops from a combination of infrastructure and actual sending behavior. Within a multinational, multiple teams and suppliers can influence that reputation. A central marketing team may work carefully, while a local business unit or external event platform sends large volumes irregularly using a related domain. Without an overview, it remains unclear which application uses which sender domain and who can resolve an issue. A manageable sending inventory therefore contains at least the following four elements:

• Document the application, sender domain, communication type, and responsible owner for each sending stream.
• Record which internal systems and external suppliers are authorized to send on behalf of each domain.
• Make clear who reviews and approves DNS changes and new sending applications.
• Link each sending stream to an incident response process involving marketing, IT, and the relevant business unit.

This inventory makes clear where a technical change can have commercial consequences. It also supports decisions to separate marketing communications from critical operational messages where appropriate. Separation reduces dependencies, but it does not eliminate the need for careful management of each stream. The configuration must therefore be assessed as a whole, including the use of domains, IP addresses, suppliers, and responsibilities.

Authentication Is a Basic Requirement for Trust

SPF, DKIM, and DMARC perform different functions in email authentication. SPF specifies which infrastructure is authorized to send for a given domain when the SMTP identity is checked. DKIM adds a cryptographic signature that allows a receiving party to verify the signing domain identity and the integrity of signed parts of the message. DMARC connects the result of SPF or DKIM to the visible From domain and provides a policy for messages that fail the check. This connection is called alignment and deserves separate attention. An SPF or DKIM check can pass even when the domain used is not sufficiently aligned with the visible From address. A supplier may also send on behalf of the same brand using a configuration that differs from the central marketing platform. New applications, DNS changes, and domain migrations must therefore be assessed for each sending stream. Google describes additional requirements for larger senders delivering to personal Gmail accounts, including SPF, DKIM, DMARC, and alignment. Yahoo publishes its own requirements for its receiving domains. Corporate receiving environments may also apply their own security checks and policies. An organization must therefore determine which requirements apply to its actual recipients and sending streams. For Marketing Cloud Engagement, Salesforce describes the configuration of authenticated domains, complaints, and unsubscribe headers in its supplement to the bulk sender guidelines, published on May 28, 2026. A Sender Authentication Package or Private Domain may form part of the solution. The available configuration, license, and domain settings must be checked for each environment. Account Engagement and Marketing Cloud Next have their own configurations; a correct setting in one product does not prove that another sending stream is also configured correctly.

A Dedicated IP Is a Choice About Ownership

The choice between a shared and a dedicated sending IP changes how responsibility for reputation is distributed. With a shared IP, the IP reputation is also influenced by other senders in the same pool. With a dedicated IP, the organization has more influence over its own sending behavior and must also maintain that reputation itself. The choice must align with volume, consistency, and available management expertise. A new dedicated IP requires a careful warm-up process and appropriate sending patterns. Immediately sending large volumes of messages to old or minimally engaged contacts can make it harder to build trust. Salesforce also describes volume thresholds and conditions for shared and dedicated IP addresses in Marketing Cloud Engagement. Assess those current conditions alongside your own agreement and actual sending profile. Domain reputation also remains relevant when the IP address changes. A different IP is no substitute for careful domain management, appropriate communication permissions, or sound recipient selection. Separating streams can reduce risks, but it creates additional management and monitoring responsibilities. The investment decision must therefore consider the entire sending architecture and the ability to manage it sustainably.

Unsubscribes Must Be Processed Across the Entire Chain

An unsubscribe option gives recipients control over commercial communications and helps limit unwanted contact pressure. For larger senders, Gmail and Yahoo, among others, require one-click unsubscribe for relevant marketing messages. This provision is separate from the visible unsubscribe option in the message content. Both elements must be appropriate for the communication type and applicable provider rules. One-click unsubscribe involves functionality in the message headers according to the relevant provider specification. A link to a preference center in the email can also be useful, but it does not automatically replace that header functionality. Salesforce states that the relevant headers are added by default to commercial messages in Marketing Cloud Engagement. Check an actual sent message and the classification used, because the mailbox provider itself determines whether an unsubscribe button is displayed. The organizational challenge begins when multiple systems can initiate communications. An unsubscribe recorded in one system must also be processed by other systems that can activate the same marketing communications. Document which source is authoritative, how changes are passed on, and how delays or errors are detected. The organization must also assess which legal basis, channel rules, and local requirements apply to the communication concerned.

Open Rates Are Not a Reliable Measure of Attention

Available interaction measurements are not equivalent to human attention. Apple Mail can retrieve remote content in the background, meaning a recorded open does not necessarily indicate that someone read the message. Corporate security software can scan links and generate activity that is recorded as a click. Both situations affect how campaign and contact data are interpreted. This distinction becomes important when marketing teams select audiences or adjust lead scores. A campaign that excludes contacts solely because no opens were recorded may lose commercially relevant recipients. Conversely, a score that treats every recorded click as purchase intent can send the wrong signals to sales. Salesforce describes how security software can cause non-human opens and clicks in Marketing Cloud Engagement. Account Engagement includes Metrics Guard to filter some of this activity. Salesforce states that this protection does not intercept all illegitimate activity. A reliable assessment therefore combines multiple permitted signals, such as explicit preferences, relevant form submissions, and commercial context. Even then, a distinction remains necessary between engagement, reachability, and actual purchase intent.

Make Diagnosis Manageable

A deliverability problem requires an analysis of where the disruption occurs. An issue can arise before sending, during transfer to a receiving server, or after acceptance by the receiving environment. Behavioral measurement can also be distorted without delivery itself having failed. The framework below helps assess these situations separately.

Signal	Possible Explanation	Required Assessment
More bounces or blocks	Invalid addresses, a temporary disruption, or an authentication or reputation problem	Analyze the bounce category and server message for each receiving domain.
High acceptance, low response	Low relevance, filtering, or limited inbox placement	Compare audiences and campaigns; test placement where it can be measured.
Unexpected opens or clicks	Privacy features or automated security scans	Check patterns and the limitations of the reporting used.
Rising complaints or unsubscribes	Frequency, expectations, or audience selection are not sufficiently aligned	Investigate the source, campaign, and contact pressure; adjust the sending policy.

The table distinguishes observable signals from possible explanations. In Marketing Cloud Engagement, for example, the bounce category and SMTP message can be investigated through tracking or, depending on the configuration, a Tracking Extract or the _Bounce Data View. A permanent address error requires a different response from a temporary server disruption or a block caused by authentication. The receiving server does not always provide enough detail to identify a single cause immediately. When acceptance is high and response is low, inbox filtering is a possible explanation, not a proven diagnosis. A targeted test with relevant recipients or information from their email administrator can help determine where a message ends up. Such observations are samples and should not automatically be interpreted as inbox placement for the entire audience. Alongside the outcome, therefore, report which receiving domains were examined and where information is missing. When an issue occurs suddenly, the team first determines its scope and the data available. Does it affect one campaign, one country, one receiving domain, or multiple sending streams? The team then investigates recent changes in authentication, volume, audience, and message classification. Uncoordinated resending can make the problem worse and is therefore not a standard response.

Connect Reach to Commercial Value

For the CMO, deliverability concerns the relationship between marketing investment and the audience that can be reached. The CIO or person responsible for IT needs visibility into domain management, authentication, suppliers, and technical continuity. Sales needs reliable contact signals to prioritize follow-up. Finance must be able to assess which commercial processes are affected and what recovery and prevention will cost. A management dashboard must therefore start with a consistent denominator. For example, measure the number of messages sent and the proportion of definitively identified bounces for each campaign and receiving domain, and compare these with a previously selected period involving a comparable audience and sending practice. Analyze bounce categories separately, because a temporary problem does not require the same action as an invalid address or authentication error. Also show where information about actual inbox placement is unavailable. Suppose a manufacturer sends one message to each of 20,000 unique business addresses. In previous comparable sends, the final bounce rate was 1%; for this send, it is 8%. In this fictional example, that difference of seven percentage points corresponds to 1,400 additional bounced messages compared with the number expected at the previous rate of 1%. The figure is a signal for investigation, not proof that 1,400 customers missed a purchase. The commercial impact depends on the accounts involved, the content of the message, and the options for lawful follow-up. For important product updates, an account team may, for example, need to check whether the information can be shared through another appropriate contact point. For a marketing campaign, the priority may instead be to restore authentication, audience selection, or reputation. Finance can then weigh the costs of investigation, recovery, and any replacement communication against the estimated value of the affected process. A workable operating model establishes in advance when an issue must be investigated, who leads the incident response, and who decides when sending can resume. The threshold must be aligned with the organization’s own volume, historical range, and the business-critical nature of the messages. A technical block affecting a strategic account may require immediate follow-up, even when the overall bounce rate remains low. This creates a decision framework that considers both the scale and the commercial significance of an incident.

Reachability as Part of the Marketing Architecture

Email deliverability is an ongoing requirement for reliable campaigns, customer communications, and commercial reporting. Authentication and infrastructure establish a foundation for that reachability. Audience management, appropriate contact frequency, and consistent unsubscribe processing help determine whether that foundation retains its value. Monitoring then makes clear where the organization needs to intervene. CloudEngagePro approaches deliverability through the relationship between Salesforce Marketing Cloud, Account Engagement, data, and the organization. The management decision is where the greatest loss of reliable reach could occur and which dependencies cause that loss. This includes assessing the investment needed to reduce that risk and make recovery manageable. In this way, reachability becomes an explicit part of the marketing architecture and of the decisions based on it.