Mobile Marketing Strategy: 3 Essential Decisions

“Treat yourself: $10 off your next order.” The push arrives while Jill is on a skincare retailer’s app, checking the order page for the third time that day.

The gift set was for her sister’s birthday on Saturday. The carrier logged a delay on Monday, and it’s been on her order record ever since.

While the push was cheery and positive, it was also the worst thing the brand could have sent her at that particular moment.

That’s a mobile strategy failing at the one moment she was sure to be looking. What she should have seen was the delay update with a new date; the discount could have waited until the package arrived.

Our phones have become the place where we do just about everything: shop, bank, track late packages, and every mobile message a brand sends is judged there. This is how to build a mobile marketing strategy: decide when a customer needs to hear from you, which channel that message belongs on, and who rules when two messages compete.

A mobile marketing strategy is the plan a brand uses to turn what it knows about a customer into messages on their phone. It sets out when a customer hears from you, which mobile marketing channel carries each message, which customer data each message is built from, and which commercial result can be attributed to it.

Mobile engagement covers the whole relationship a customer has with a brand through their phone, from push and in-app messages to service and loyalty. This strategy covers one part of it: what you send, and when.

Customers already know what a connected brand feels like, because their favorite brands set the bar. In the Global Engagement Index 2026, a survey of 10,000 consumers, 63% “say their favorite brand delivers seamless, connected experiences across mobile, web, and in-store”.

So a push that goes out with no sight of what just happened on the order page, or at checkout, gets measured against the brand that customer likes most. That’s the bar now.

The easiest way to train a customer to ignore you is to message her every time she blinks.

A CRM manager at a home fragrance brand looks back over one customer’s week in the app and the order system. The list of things the brand could message her about runs to a page: three product views, a cart she left, a delivery, a new loyalty tier, the store she walked past on Wednesday. Message her about all of them and she hears from the brand every few hours.

She’ll mute you by Wednesday.

Most teams already hold the data that produces that list:

• Browsing and app use
• Purchase history and how often she buys
• Lifecycle stage
• Location, where she’s opted in
• Consent, and the channels she’s said yes to

You’ll act on only a few of them.

How do you decide when to message a customer?

Message a customer when an update passes two tests:

• It’s time-sensitive for her. The message is worth less, or does harm, if it arrives tomorrow.
• You hold a current record that makes the message right. If the order, stock or loyalty data behind it has gone a day stale, you send a discount on the coat she bought on Saturday, or push a product that sold out this morning.

Operational moments usually pass both. Order and delivery updates, a product back in stock, a change in loyalty status and a store nearby all come from records the brand already holds, and each of those updates is worth less the longer it waits: a store alert within minutes, a delay update within hours, a new tier by the next time she’s at checkout.

Those two tests are what turn a trigger into the moment that matters. Everything else can wait.

And customers count on those updates. In the Customer Loyalty Index 2026, a survey of 10,002 consumers, 20% name “Real-time order and fulfillment updates” among what they expect in return for their loyalty. For a customer like Jill, a promo push that lands ahead of the delay update breaks the brand’s side of that deal.

With mobile customer engagement in SAP Engagement Cloud, the carrier’s delay on Jill’s order goes out as a push, in-app or inbox update as soon as it lands on her record, automated to send in real time. The fragrance customer who walked past a store on Wednesday can get her alert while she’s still on the street, because you can import your store locations and send alerts, updates or promotions when a customer enters or leaves the area around one.

Jill’s delay sat on her record for three days, and nothing was triggered from it. Most enterprise teams say acting on a record as it changes is still out of reach: 78% of enterprise decision-makers “say they can’t actually practice real-time AI optimization in their day-to-day campaigns”, according to the Global Engagement Index 2026.

So put the time-sensitive moments that pass both tests on real-time triggers first, and bring the weekly campaigns in after them.

AI helps with the next layer of decisions:

• who gets a message at all
• when it sends
• which channel it goes to

SAP Engagement Cloud builds AI segments on predicted lifecycle status, spend and channel engagement, and channel selection can follow each customer’s likelihood to engage there. Your team still decides what the message says and why.

Once you’ve decided she needs to hear from you, the next decision is where the message goes.

Each channel suits a different moment. Start from the moment, then pick the channel:

Mobile wallet is the channel customers use in store. Wallet passes carry loyalty cards, coupons, vouchers, tickets, membership cards and offers, and they identify the customer at the point of sale, bridging online and offline. For a brand without an app, the wallet is its mobile channel: passes go to Apple Wallet and Google Wallet with no app to build.

For customers without the app, SMS carries the urgent updates. Conversational messaging handles anything that needs a reply, once the customer has opted in.

Getting each of those channels to perform is its own job, and our guide to making push, in-app and inbox messages work harder covers it channel by channel.

Back at the skincare retailer, the discount push came from the ecommerce team’s weekly calendar, the delay sat with customer service and the app team ran push. Each team did their jobs properly but Jill still got the wrong message.

A promo calendar is basically someone guessing on a Monday about what customers will want the following Thursday. But in Jill’s case, nobody building the thing could see her package was late.

When nobody owns the rules, whatever was already scheduled goes out anyway.

Who should own mobile message frequency?

One person should own suppression, priority and frequency for all mobile messages, with frequency counted across push, SMS and wallet together. If those rules are split between teams, nobody can stop a promotion landing on top of a delay update.

That owner also holds the record the rules run on:

• The one customer record every mobile message draws on: app behavior plus orders, deliveries, stock, loyalty status and store visits, held as connected customer data.
• The suppression and priority rules for which message goes first when two would fire.
• Frequency caps that count push, SMS and wallet messages together.

Run Jill’s delay through those rules. The owner sets one: while an order is flagged as delayed, promotional pushes to that customer wait, and the delay update goes first. The discount goes out once the carrier confirms delivery.

That’s one rule protecting the moment that matters.

The same rules connect mobile with email, web, ecommerce, paid media, loyalty, service and stores, so a purchase in one place changes what every other channel sends next. For the build itself, see how to connect mobile to the omnichannel journey.

The challenge: adidas Running app needed to personalize messages for its app community across channels, countries and languages, and keep the experience consistent.

The solution: The team built campaigns on real-time triggers from app activity, with customer insights and messaging in SAP Engagement Cloud.

The results:

• +300% increase in campaign efficiency
• +8M app opens from campaign content
• +200 data points measured for content optimization

For the app-side view of the same program, see how the team built an app marketing strategy to strengthen customer retention.

Build the plan in this order, and revisit it whenever a new trigger or channel arrives:

1. Set the objective in commercial terms. Name the result you’ll judge mobile on – repeat purchase, retention or lifetime value – so every later choice has a yardstick.
2. Connect the record. Every mobile message should draw on app behavior plus orders, deliveries, stock, loyalty status and store visits.
3. Keep only the moments that pass both tests. List the triggers your data can produce, then keep the triggers that are time-sensitive for the customer and backed by a record that makes the message right.
4. Give each moment its channel. Start from the moment, then pick push, in-app, inbox, wallet, SMS or conversational messaging.
5. Name one owner for the rules. One person owns suppression, priority and frequency across push, SMS and wallet.
6. Set consent and data-use rules. Write down which opt-ins each channel needs and which data each trigger may use, before the triggers go live. Loyalty depends on it: in the Customer Loyalty Index 2026, a survey of 10,002 consumers, 30% name “Irresponsible data use” as something that breaks their loyalty.
7. Audit the experience each message lands on. A delay update that opens a slow order page, or an offer that ends in a checkout form built for desktop, wastes the moment you chose, so check speed, checkout, forms and landing pages on the journeys your messages start. Our guide to mobile optimization strategies covers the fixes.
8. Decide how you’ll prove it. Hold a group back from mobile messages and compare repeat purchase, retention or mobile revenue per customer, with opt-out and uninstall rates as the cost. Our guide to measuring what mobile engagement is worth walks through the method.

A CRM manager at a beauty retailer sends a back-in-stock push to a customer who has bought the same cleanser four times and they buy. What the report doesn’t show is that the customer herself never read it. Her AI assistant did, matched the product to a standing instruction to reorder when the price drops, and bought.

Younger customers are already willing to hand that over: 44% of Gen Z “would trust an AI assistant to purchase an item for them”, according to the Customer Loyalty Index 2026, a survey of 10,002 consumers. An assistant that buys has to read first, which puts it between the brand and the customer on every message that follows the order.

1. We’ll write for the AI assistant as well as the customer

A delivery update, a price drop or a points-expiry message may now be parsed by AI before it’s read by a human. An assistant will work from what it can extract: the order number, the new date, the status, the price. The moment test will still hold, and the record behind the message will matter more, because an assistant acting on a delay will need that delay to be in the data rather than implied by the copy. Sadly, your clever subject line will be wasted on an AI assistant that only reads the order number.

2. Service and marketing will share the same thread

Using conversational channels means service replies and promotions are happening in one conversation, on the same screen. A customer who has just asked where her order is could potentially see the next promotion as an answer to that question. So your suppression rules now have to cover an open service conversation, not just a recent send. With that customer experience in mind, decide which team should own the rules.

3. Consent sets the ceiling

The data your customer agrees to share determines what kind of messages you’re able to send. For example, without an opt-in, their location isn’t a signal you can act on. This makes consent a planning constraint rather than a compliance step: it decides how many of the moments you identified are actually available to you, and it’s worth knowing that number before you build the plan around them.

Circling all the way back to Jill’s gift set, let’s say the rules are now in place. Come Monday, she gets a push with the new delivery date, and the $10 offer arrives after the package does. Without them, she got the discount on the order page on Thursday, two days before her sister’s birthday.

That’s how a brand ends up upselling a customer it’s already letting down.

Your customers already check their phones for everything that matters to them, so the strategy is choosing which of those moments you bring something useful to. In SAP Engagement Cloud, automated workflows activate on real-time business events such as orders, inventory, service tickets and loyalty milestones, so push, in-app, inbox, mobile wallet and conversational messages all draw on the record that held Jill’s delay.