Your team wants to "send a mobile message" after every order, delivery or security alert. Fine, but which one: a push notification through MobilePush, or a text message through MobileConnect? In Salesforce Marketing Cloud the two channels look alike on the surface, yet they differ in consent rules, cost, reach, technical limits and the way you trigger them. This guide helps you pick the right channel for each message, then fire it cleanly through the REST API, with code you can adapt to your own account today.
MobilePush and SMS: two channels, two logics
SMS (MobileConnect) reaches any phone, no app required, with open rates close to 100%. It is billed per message, bound by strict opt-in rules and limited in length. Push (MobilePush) requires that the person installed your app and accepted notifications, but it costs next to nothing to send and supports rich content such as images, buttons and deep links.
| Criteria | MobilePush | SMS (MobileConnect) |
|---|---|---|
| Prerequisite | Mobile app with the SDK | Short or long code, opt-in |
| Cost per message | Close to zero | Billed per message |
| Content | Rich, deep links, buttons | Text, 160 characters per segment |
| Reach | App users only | Any mobile phone |
| Best for | Engagement, nudges, product news | Critical alerts, codes, delivery updates |
How to pick the right channel
Ask three questions
Is the message critical? A login code or a delivery delay justifies SMS, because it arrives even without the app or a data connection. Does the recipient have your app? If so, push is almost always cheaper and richer. Finally, what is the message worth? A cart-recovery text costs a few cents, which makes sense on a high-value basket and far less so on a routine newsletter.
Think waterfall, not either/or
The best pattern is not choosing one channel but chaining them. Try push first, wait a short interval in Journey Builder, then fall back to SMS if the notification went unopened. You reserve the paid channel for the cases that deserve it.
Push is your default channel and SMS is your safety net: keep it for messages where being unread has a real cost.
Compliance: the part everyone underestimates
SMS marketing requires explicit consent, a clear opt-out instruction (for example "Reply STOP") and respect for local quiet hours, which vary by country. A strictly transactional message, such as a one-time code or a parcel update, is treated differently, but mixing both types in one flow is a classic mistake. Always keep transactional sender IDs or short codes separate from marketing ones, and store proof of consent in a dedicated Data Extension.
Authentication: getting a token
Both channels are triggered through the REST API once you authenticate with a Server-to-Server API package. Your authentication subdomain is unique to your account.
POST https://YOUR_SUBDOMAIN.auth.marketingcloudapis.com/v2/token
Content-Type: application/json
{
"grant_type": "client_credentials",
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET"
}The response contains an access_token valid for roughly twenty minutes and the base REST URL for your account. Cache it instead of requesting a new one on every call, or you will run into rate limits.
Triggering a transactional SMS
In MobileConnect, first create an API Triggered message and note its ID. The call below sends the text to one or more numbers, creating the contact if needed.
POST https://YOUR_SUBDOMAIN.rest.marketingcloudapis.com/sms/v1/messageContact/MESSAGE_ID/send
Authorization: Bearer ACCESS_TOKEN
Content-Type: application/json
{
"mobileNumbers": ["14155550123"],
"subscribe": true,
"resubscribe": false,
"keyword": "DELIVERY",
"Override": true,
"messageText": "Your parcel arrives tomorrow between 9am and 12pm. Track it: https://example.com/s/ab12"
}Use the international format without the plus sign. Watch the messageText length: past 160 GSM characters the message is split into separately billed segments, and a single special character such as an emoji or a curly quote switches the encoding to 70 characters per segment.
Triggering a push notification
On the MobilePush side the logic is the same: an API Triggered message, then a call targeting contact keys. The contact must have registered a device through the SDK.
POST https://YOUR_SUBDOMAIN.rest.marketingcloudapis.com/push/v1/messageContact/MESSAGE_ID/send
Authorization: Bearer ACCESS_TOKEN
Content-Type: application/json
{
"Override": true,
"MessageText": "Order #4821 has just shipped.",
"ContactKeys": ["CUSTOMER-00042"],
"CustomKeys": { "order_id": "4821" }
}Custom keys are passed back to the app, which can open the order tracking screen directly. Check Salesforce's API reference for the exact fields in your version, since some parameters change between releases.
Personalizing the text with AMPscript
For messages built inside Marketing Cloud rather than your back office, AMPscript pulls data in at send time.
%%[
VAR @firstName, @orderId
SET @firstName = AttributeValue("FirstName")
SET @orderId = Lookup("Recent_Orders", "OrderNumber", "ContactKey", _subscriberkey)
]%%
Hi %%=v(@firstName)=%%, order %%=v(@orderId)=%% is on its way.Keep the copy short: personalization that pushes an SMS past one segment inflates the bill quickly at scale.
Mistakes to avoid
First, never test on real customers: build a test list with your own devices. Second, handle API errors with a retry queue instead of looping blindly, which can double your sends. Third, log every send in a Data Extension (order ID, channel, timestamp) so you can answer a customer who says nothing arrived.
Key takeaways
Push first. It is cheap and rich, so make it the default for people who use your app.
SMS for what matters. Keep it for critical messages and contacts without the app.
Build a waterfall. Chain push then SMS in Journey Builder to control costs.
Consent comes first. Separate transactional and marketing flows and keep proof of opt-in.
Watch the encoding. One special character can double the number of billed segments.
Need help designing mobile journeys in Salesforce Marketing Cloud? Get in touch with the CGC-Agency team.
