Best Practices For Email Push SMS Delivery In Adobe Campaign Services

Delivery is the part of campaign marketing that most people assume is handled the moment they hit send. It is not. Getting a message out of Adobe Campaign is one thing. Getting it to land in an inbox, appear as a push notification on a locked screen or arrive as an SMS without being filtered or delayed is an entirely different problem. Each channel has its own delivery mechanics, its own failure modes and its own set of practices that separate programs that perform consistently from ones that underperform without anyone being entirely sure why.

Working across all three channels inside Adobe Campaign Services means understanding each one on its own terms before thinking about how they work together.

Email Delivery: Reputation Is Everything

Email delivery in Adobe Campaign starts with sending reputation and sending reputation starts long before the first message goes out. The IP addresses and sending domains attached to a Campaign instance carry a history that inbox providers read before a single piece of content is evaluated. A new IP has no history. A warmed IP with strong engagement signals gets treated differently at the inbox than one that has never sent before.

IP warming is not optional for new sending infrastructure. It is a structured process of gradually increasing send volume over several weeks, starting with the most engaged segments of the list. Starting with re engagement campaigns or cold lists during a warming period is one of the fastest ways to damage a sending reputation before it has been properly established.

Beyond warming, the practices that sustain strong email delivery over time are consistent and unglamorous. List hygiene matters more than almost any other variable. Hard bounces need to be suppressed immediately. Soft bounce thresholds need to be configured so that addresses that fail repeatedly are not continuously retried. Unsubscribes need to be honored within the timeframes required by applicable regulations and suppression lists need to be applied before each send, not manually maintained on an ad hoc basis.

Adobe Campaign provides bounce qualification rules that classify returns from mail servers and update recipient statuses accordingly. Those rules should be reviewed and customized to reflect the actual bounce codes coming back from the domains on the sending list rather than left on default settings that may not accurately reflect the sending environment.

Engagement signals also feed back into delivery performance. Inbox providers weight opens, clicks and replies as indicators of whether recipients actually want the messages being sent. Mailing to large segments of chronically unengaged contacts drags down overall engagement rates and signals to inbox providers that the program is not well targeted. Suppressing contacts who have not engaged in twelve months and running a structured re engagement campaign before mailing them again is better practice than carrying dead weight on an active list in hopes that volume compensates for low engagement.

Push Notification Delivery: Device and Permission Reality

Push notifications operate on a completely different technical rail from email. Delivery goes through Apple Push Notification Service for iOS and Firebase Cloud Messaging for Android. Adobe Campaign handles the dispatch to those services but what happens next is determined by the device, the operating system version and crucially, whether the user has granted notification permissions for the application.

The permission layer is the most significant variable in push delivery performance. A user who has not granted push permissions will never receive a notification regardless of how well the campaign is configured. Opt in rates for push notifications vary widely by app category and how permissions were requested at installation. Tracking opt in rates by device type and app version inside Adobe Campaign is the first step toward understanding the actual reachable audience for any push campaign.

Token management is the operational discipline that keeps push delivery working at scale. Device tokens change. Users reinstall apps. Tokens expire or become invalid when a user upgrades their device. Adobe Campaign needs to receive updated tokens from the mobile application through the SDK integration and invalid tokens need to be cleaned from the database regularly. Sending to a high volume of stale tokens inflates delivery attempt counts while depressing actual delivery rates and creates noise in performance reporting.

Payload size limits exist for both iOS and Android and violating them causes silent delivery failure. iOS caps notification payloads at four kilobytes. Android is more generous but still has limits. Rich media notifications that include images or custom data need to be tested across device types to confirm they deliver correctly before being used at scale.

Timing matters differently for push than for email. A push notification arrives with an audible alert and a screen interruption on most devices. Sending at times when users are likely to find that interruption welcome rather than intrusive affects not just engagement but longer term opt in retention. Users who find push notifications poorly timed disengage or revoke permissions. Either outcome degrades the channel over time.

SMS Delivery: Compliance and Carrier Reality

SMS delivery in Adobe Campaign involves a layer of complexity that email and push do not face in the same way. Messages route through a carrier network before reaching the recipient and carriers have their own filtering rules, throughput limits and compliance requirements that vary by country and by carrier relationship.

Sender ID configuration is the first place SMS delivery can go wrong. Depending on the market, SMS campaigns may need to send from a dedicated short code, a long code or an alphanumeric sender ID. The rules around which format is permitted vary by country and some markets do not support alphanumeric sender IDs at all. Getting sender ID configuration wrong does not always produce an obvious error. It sometimes results in messages that are delivered with a different sender display than intended, which affects trust and response rates.

Message encoding affects both delivery and character count. Standard GSM encoding allows 160 characters per message segment. Characters outside the GSM character set, such as certain currency symbols, curly quotes or characters from extended alphabets, trigger Unicode encoding which reduces the segment length to 70 characters. A message that appears to be well within the 160 character limit in a content editor can split into multiple segments on delivery if it contains non GSM characters, which increases cost and can affect how the message displays on the recipient device.

Opt out handling in SMS requires particular attention. Regulatory requirements in most markets mandate that opt out requests sent via reply SMS are honored immediately and that the number is suppressed from further marketing messages. Adobe Campaign supports automatic opt out processing through keyword recognition, but this needs to be configured and tested for each SMS sender and market rather than assumed to be active by default.

Throughput configuration in Adobe Campaign controls how quickly SMS messages are dispatched to the carrier. Sending too fast against a carrier connection that has lower throughput limits causes queuing and delayed delivery. For time sensitive SMS campaigns, understanding the throughput capacity of the configured external account and aligning expected send volumes to that capacity is essential. A flash sale SMS that arrives four hours after the sale has ended due to a delivery queue backlog is worse than not sending the message.

Across All Three Channels: Monitoring Before Problems Become Incidents

The practices that separate well run multi channel delivery programs from reactive ones come down to monitoring cadence. Adobe Campaign provides delivery logs, tracking logs and built in reporting that surface delivery performance in near real time. Using those tools actively rather than checking them when something feels off is the operational habit that keeps delivery programs healthy.

Soft bounce rates trending upward on email are a signal worth investigating before they become hard bounces at scale. Push delivery rates dropping on a specific device OS version may indicate an SDK issue or a token management gap. SMS delivery receipts showing elevated carrier rejection rates on a particular sending route are worth escalating to the connector provider before they become a sustained delivery problem.

The programs that maintain strong delivery performance across email, push and SMS over time are not the ones that got lucky with their initial configuration. They are the ones where someone is paying close enough attention to catch problems when they are still small.