Mobile Marketing: Channels, Permissions and Measurement

Mobile marketing is marketing designed for people using mobile devices. It runs through channels such as SMS and other messaging, app push notifications, in-app messages, web push, mobile websites, mobile search and mobile ads. What makes an activity mobile marketing is intent: it has a marketing purpose and was deliberately shaped for the phone context. A desktop newsletter that someone happens to open on a phone does not qualify just because of the screen it landed on.

That makes the term an umbrella, not a single channel. Each mobile channel depends on something different, whether that is a phone number, an installed app, an operating system permission, a browser subscription or content that works on a small screen. Most planning mistakes start when those dependencies get treated as one thing.

Where the boundary of mobile marketing sits

In the abstract of their 2009 paper Mobile Marketing: A Synthesis and Prognosis, Shankar and Balasubramanian treat mobile marketing as an exchange between a company and its customers, running in two or more directions, in which an offer is communicated and promoted through mobile media, devices or technology. That view puts the offer and the exchange at the center rather than any one technology. It is an attributed academic framing, though, not a universal standard that every practitioner uses.

A two-part test

A simple test helps in practice. First, is there a marketing purpose, such as promoting an offer, bringing a customer back or encouraging a purchase? Second, was the activity designed for the mobile context, with small screens, touch input, notification behavior or on-the-go use in mind? When both answers are yes, you are looking at mobile marketing.

Several things are often mistaken for requirements. An installed brand app is optional. So are exact GPS location, tracking permission on iOS, wearable devices, real-time proximity triggers and heavy personalization. Some programs use all of them. Many use none.

What does not count on its own

Some activities sit next to mobile marketing without being it:

• Purely transactional notices. An order confirmation or delivery update with no marketing purpose is a service message, not necessarily marketing.
• Incidental phone viewing. A desktop campaign opened on a phone was never designed for the mobile context.
• Responsive design by itself. A mobile-friendly site makes marketing usable on phones, but a layout is not a campaign.
• A single channel. SMS is one mobile channel. It is not the whole discipline.

It also helps to separate mobile marketing from app marketing. App marketing focuses on promoting and growing an app. Mobile marketing can happen with no app at all.

The main mobile marketing channels

Each channel reaches people by a different route, and each route has its own prerequisites.

SMS and messaging

SMS reaches a phone number without requiring an installed brand app. Other messaging channels have their own access requirements. Whether a business may send a marketing text is a separate question that depends on the purpose of the message, who receives it and the jurisdiction involved. Those rules differ between countries, and this entry does not cover them.

Native push notifications and in-app messages

Native push notifications need an installed app, and the delivery path has several stages. In the Firebase Cloud Messaging architecture, for example, an app instance registers and receives a token, a server or backend builds the message, the FCM backend accepts it, a platform-level transport layer routes it, and the SDK on the device handles it. In FCM, a successful send means that a stage in that chain accepted the request. It does not prove that anyone saw the notification.

In-app messages work differently. They appear inside the app experience, so they depend on people actually opening and using the app. They reach nobody who has not installed it.

Web push

Web push brings notifications to people without a native app. MDN's Push API documentation explains that a web app needs an active service worker and subscribes through the PushManager interface, and that subscription is what lets a server send messages later. Browser support and behavior differ, so a web push plan needs testing in the browsers your audience actually uses.

Mobile web, mobile search and mobile ads

Google states in its mobile-first indexing guidance that it uses the mobile version of a site's content for indexing, which is why content parity between mobile and desktop versions matters. A responsive layout still carries no ranking guarantee.

Mobile ads appear inside apps and in mobile browsers. Paid placements inside apps fall under the narrower term in-app advertising. Mobile ads can be targeted and shown without using a person's exact GPS position.

These are examples, not universal reporting guarantees. Check each system's event definitions and instrumentation; none alone establishes attention or incremental effect.

Four controls that work independently

Teams often talk about "permission" as if it were one switch. On mobile there are at least four separate layers. Passing one tells you nothing about the others.

Marketing eligibility

Marketing eligibility is the question of whether a business may send a marketing message to a person at all. It depends on the purpose of the message, the type of recipient and the jurisdiction. It is a legal and policy matter, not a phone setting, and the specifics belong with qualified advice for each market.

Operating system notification permission

Notification permission is controlled by the phone's operating system. On Android, the notification runtime permission introduced with Android 13 covers non-exempt notifications. Apps newly installed on Android 13 or higher must ask before they can post those notifications. Some apps that were already installed before a device upgrade can receive the permission automatically if they meet the documented eligibility conditions, and certain notification types are exempt.

Apple uses a different model. Its guidance on asking permission to use notifications describes requesting authorization for alerts, sounds and badges, and it also describes provisional authorization, which delivers notifications quietly without an upfront prompt. There is no single universal prompt that every mobile user sees.

App Tracking Transparency

App Tracking Transparency, usually shortened to ATT, is Apple's framework for one specific question. Apple's User Privacy and Data Use page explains that, starting with iOS 14.5, apps must ask through ATT before tracking people across apps and websites owned by other companies or accessing the device's advertising identifier. ATT does not grant permission to send text messages. It is not notification permission either. A person can allow notifications and decline tracking, or the reverse.

Location permission

Location is optional for mobile marketing, and Android treats it as layered. The Android location permissions guide separates foreground from background access and approximate from precise location, and it notes that geofencing relies on background location access. Those are user-facing controls, not promises about how accurate a reading will be.

Geo-fencing is one location-trigger mechanism, not a requirement of the discipline. Request location only when a use case genuinely depends on it, because every extra permission request is another chance to hear no.

Designing for small screens

Mobile marketing must accommodate small screens, touch input and varied usage contexts. That makes usability, accessibility and restraint important.

Touch targets and accessibility

Landing pages and in-app screens need controls that people can tap reliably. The W3C explanation of WCAG 2.2 Success Criterion 2.5.8, Target Size (Minimum) discusses a minimum target size of 24 by 24 CSS pixels, subject to five exceptions, including adequate spacing around smaller targets and links that sit inside a sentence. The Understanding page is informative guidance, so teams should read the criterion itself when they need the formal requirement.

Timing, frequency and privacy

Some notifications appear on a lock screen alongside personal messages; others are delivered quietly or shown elsewhere. Plan timing and frequency for the channel and the recipient's settings. Privacy works the same way. Ask only for the permissions a feature needs, explain the benefit before the system prompt appears, and avoid collecting location or tracking data you have no plan to use.

Measuring mobile marketing without overclaiming

Mobile channels produce plenty of data. Most of it records system events, not human attention or business impact.

What send, delivery, click and attribution data can show

These labels depend on the channel and reporting system. A send record may indicate request acceptance; a delivery record may indicate transport or receipt at a documented endpoint; and an impression record follows the platform's counting rules. Check what each system actually records. None of these records alone establishes human attention or incremental effect.

A click shows an action, and an attributed conversion shows that a reporting model assigned credit. Neither proves cause, because attribution is a crediting rule. Someone who was already going to buy can tap a message on the way to a purchase they would have made anyway.

Estimating incremental effect

To estimate what a campaign actually changed, you need a comparison with people who did not receive it. Google's Conversion Lift is one product-specific example, comparing outcomes between a group that was shown ads and a control group that was not. Availability depends on the product and its requirements, so it is not a universal option. For owned channels such as SMS or push, the same logic applies when a random group is held back from a send and the two groups are compared.

Two company examples of mobile features

Starbucks app in the US

The Starbucks app page presents ordering ahead, finding stores and the Starbucks Rewards program as core features. It pairs a convenience job with a loyalty program that gives people a reason to return.

IKEA app in the US

The IKEA US app page describes inspiration and offers, product scanning, saved shopping lists and 3D visualization of products. It shows mobile marketing tied to planning and shopping rather than to messages alone.

Both pages are company self-descriptions of US versions, and neither reports campaign results. Feature sets can change. Treat them as illustrations, not evidence of what those features achieved.

Planning a mobile marketing program

Start from the customer job

Begin with what the customer is trying to do on the phone: check an order, find a store, compare a product, redeem an offer. The channel follows from that job. A timely reminder suits SMS or push. A browsing need suits mobile web and search.

Match permissions to the use case

List the controls each channel requires before launch: marketing eligibility, notification permission, tracking permission on iOS where it applies, and location only if a feature needs it. If paid placements are part of the plan, whether they run in house or through social media ads services, the same discipline applies to tracking and audience data.

Decide how success will be judged

Agree on the measure before the first send, and remember that questions about impact need a control group. Mobile web, search and paid channels often touch the same customer journey, so some businesses plan mobile work as part of wider internet marketing services instead of running it as a separate project.

Frequently Asked Questions

What does mobile marketing mean?

Mobile marketing is marketing designed for people on mobile devices, using channels such as SMS and messaging, app push notifications, in-app messages, web push, mobile web, mobile search and mobile ads. It needs a marketing purpose and deliberate adaptation to the mobile context. A desktop campaign that happens to be opened on a phone does not qualify by itself.

Does mobile marketing require a mobile app?

No. Native push notifications and in-app messages need an installed app, but SMS, web push, mobile websites, mobile search and many mobile ads work without one. App marketing, which promotes and grows an app itself, is a narrower activity.

How is SMS different from a push notification?

SMS goes to a phone number and does not need an installed brand app. A native push notification goes to an installed app through a messaging service and the operating system. Notification controls vary by platform and version: Android 13 and higher requires a runtime permission for non-exempt notifications, with exceptions for exempt types and eligible apps installed before an upgrade, and Apple offers provisional authorization that delivers quietly without a prompt. Web push relies on a browser subscription instead of an app.

Is notification permission the same as consent for marketing or tracking?

No. Marketing eligibility depends on the purpose of the message, the recipient and the jurisdiction. Notification permission is an operating system control, such as the Android 13 runtime permission or Apple's alert and provisional authorization. App Tracking Transparency, from iOS 14.5, covers cross-company tracking and access to the advertising identifier. Each control is separate.

Does mobile marketing need precise location data?

No. Location is an optional input. Android separates approximate from precise location and foreground from background access, and geofencing relies on background access. Many messages and mobile ads work without exact GPS, so a campaign should request location only when its use case depends on it.

How can you tell whether mobile marketing actually worked?

Send, delivery and impression records mean different things across channels and reporting systems, so check what each one records. None of them, nor a click or an attributed conversion, establishes on its own human attention or incremental effect. That estimate needs a comparison with a control group, such as a holdout or a lift test where the platform offers one.

Is a mobile-friendly website the same as mobile marketing?

Not on its own. Responsive design makes a site usable on phones, and Google uses the mobile version of a site's content for indexing, but design alone is not a campaign and does not guarantee rankings. It becomes part of mobile marketing when it supports a defined marketing purpose.

Related Terms

• In-app Advertising: paid ad placements inside mobile apps, one subset of mobile marketing.
• Geo-fencing: an optional location-trigger mechanism that some mobile campaigns use.
• Cross Channel Marketing: coordination of messages across channels, a scope wider than mobile.