Which channels does OneSignal offer?
OneSignal connects businesses with customers through mobile and web push, in-app messages, and email. It also offers SMS, RCS, and Live Activities, each with its own setup and availability requirements.
Start with the situation in which a customer receives the message. Separate return-to-app reminders from guidance inside the app, and set priorities and intervals to avoid repeating the same content across channels.
Push: a reason to return
Push connects a short message to a next action. Plan the destination screen and login behavior alongside the notification copy.
Mobile push
Platform credentials such as APNs or FCM and notification permission are required. SDK integration commonly connects subscriptions, login, and click handling; API-based configurations are also possible.
Web push
An HTTPS website, a service worker, a supported browser, and user permission are required. Each browser and device has a subscription, so account identity mapping matters.
Web push on iPhone
On iOS and iPadOS 16.4 or later, users can subscribe through a web app added to the Home Screen. A regular browser visit does not provide the same permission flow.
Ask for permission when customers understand the value of the notifications. Delivery and presentation depend on device, browser, and operating-system conditions.
In-app: help in the current task
In-app messages display guidance, feature introductions, or surveys during an active mobile app session. They require the OneSignal SDK and do not support websites. Normal in-app display does not require push permission.
Set the audience and display conditions, then create the message. Check timing and dismissal so guidance does not obstruct a task, and connect its button to the feature it describes.
After SDK integration, messages can be created in the dashboard. Application-specific triggers or click behavior may require additional development.
Email: details customers can revisit
Email fits usage guidance, content recommendations, and detailed follow-up. Define the sending domain and sender. A domain administrator must review authentication such as SPF, DKIM, and DMARC; include account verification in the launch plan.
Before changing DNS, check existing sending systems. Manage consent, unsubscribes, bounces, and sender reputation together, and check delivery with a limited audience before expanding.
Connect Korean SMS and Alimtalk to customer journeys
Connect your existing SMS or Alimtalk provider’s API to OneSignal Journey webhooks to send messages based on customer behavior. Kakao Alimtalk is available through this separate integration.
IXC supports provider API integration, any middleware development needed, delivery tracking, duplicate prevention and operations. We determine the connection method from the provider’s authentication and message format requirements and your access to Journey webhooks.
Native OneSignal SMS, RCS and Live Activities
Native OneSignal SMS needs a provider, sender configuration, supported destination countries and consent. RCS also has sender approval and country, carrier and device requirements. SMS fallback needs its own setup.
Live Activities displays application progress on supported system surfaces. Its implementation scope differs from push and in-app messages and requires an application SDK and platform-specific work.
Design example
Introduce a new booking feature across channels
A design example for a mobile app adding reservations. Returning to the app and learning the feature serve different purposes.
Push brings customers back
Tell interested push subscribers why booking is useful and link to the relevant screen.
In-app supports first use
Explain choices when a customer first uses the booking screen. Exclude those who already completed the task.
Email explains the details
Provide terms and common answers to customers who need them. Coordinate timing with the other channels.
Customers do not necessarily subscribe to every channel. Use the customer identity and channel subscription states to define priorities and stopping conditions.
Implementation with IXC
IXC connects channel setup to the next screen
Dashboard settings and application behavior must work together. As an official OneSignal partner in Korea, IXC supports channel setup, SDK and deep-link development, data integration, and campaign operations.
Channel setup
Review the app, website, and audience, then organize platform credentials, domains, and consent flows.
Development and QA
Implement and test permission requests, notification clicks, post-login navigation, and in-app display on devices.
Delivery operations
Review channel priority, opt-outs, frequency, and message quality, then adapt them to customer behavior.
Design and testing resources
Frequently asked questions
Can OneSignal in-app messages run on a website?
OneSignal in-app messages are for mobile applications. They require an app SDK and an active session and do not support websites. For web re-engagement, assess the browser and permission requirements of web push.
Can users who deny push permission see in-app messages?
Normal in-app messages can display independently of push permission. The SDK, audience, and display conditions must be configured, and the customer needs to be using the app.
Can an iPhone receive web push?
Yes, subject to requirements including iOS or iPadOS 16.4 or later, a web app added to the Home Screen, and user permission. Check HTTPS, the web app manifest, and the service worker, and test the installation and subscription flow on a device.
Do we need every channel at launch?
No. Start with the customer touchpoint and guidance that matter most. Design account identity and subscription state early so additional channels can connect to the same customer later.