Messaging basics
Learn how messaging works, what kinds of messages Airship supports, and the tools you use to create them.
How messaging works
In order to send messages, you need the following:
An app or website integrated with the Airship software developer kit (SDK) — The SDK enables communication with mobile devices and web browsers. If you are only sending SMS or email notifications, SDK integration is not required. Notifications sent to Open Channels also do not require SDK integration, but your webhook server must be able to process and interpret a JSON payload.
An audience of your app’s or website’s opted-in users — The SDK automatically registers users, adding them to your project audience when they open your app or visit your website. For email, SMS, and Open Channels, you handle channel registration and management through the Channels API.
A container for your messages — In Airship, this container is a project. You create a project in the dashboardThe Airship web interface at go.airship.com or go.airship.eu. for each app or website you want to communicate with. Almost everything you do with Airship, including creating messages, happens inside a project. A project does the following:
- Serves as a record for your app, website, and any other channels you use to communicate with your audience
- Stores your message history, message templates, audience and analytic data, channel configuration, default message configuration settings, and more
- Contains the keys required to talk to various notification services
With the above in place:
You create a message in the dashboard or using the API.
Your app or website interprets the message via the Airship SDK, displaying or delivering it to users. SMS, email, and Apple News notifications are instead interpreted by a native client.
Users see your message. When and where they see the message depends on message type, delivery settings, and automation.
Message types
Message type availability varies per engagement channel:
| Message type | Description | Channels | Send from |
|---|---|---|---|
| Push notification | A push notification is a message that can appear on any screen on a mobile device. Push notifications appear as banners. Learn more | App | Dashboard, API |
| Web push notification | A web push notification is a message that appears in the top or bottom right corner of a web browser or in a notification center. On mobile devices, web push notifications appear similar to push notifications. Learn more | Web | Dashboard, API |
| Message Center | Message Center is both a place in your app where you can display persistent rich messages, including HTML, video, etc., and a message type. Similar to email, Message Center represents both the medium (the in-app inbox) and the message type (the messages you send to the inbox). Learn more | App | Dashboard, API |
| In-app message | An in-app message is a message that appears inside of your app. You can send in-app messages to your entire app audience, not just users who have opted-in to push notifications. The standard format, as opposed to In-App Automation, is a banner that slides downward or upward from the top or bottom of a device screen. Learn more | App | Dashboard, API |
| In-App Automation | In-App Automation refers to messages cached on users’ devices and displayed when users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times. Learn more | App | Dashboard |
| Scene | A Scene is a mobile app or web experience of one or more screens displayed with fully native UI components in real time, providing immediate, contextual responses to user behaviors. Scenes can be presented in full-screen, modal, or embedded format using the default swipe/click mode or as a Story. They can also contain survey questions. Learn more | App, Web | Dashboard |
| Email is an HTML or plain-text message that you send to registered users. Learn more | Dashboard, API | ||
| SMS | An SMS is a message that you can send to an MSISDN (phone number) over the SMMP protocol to devices that have opted in for a specific sender ID (long or short code). SMS messages appear in recipients’ native SMS clients. Generally speaking, SMS is inclusive of MMS and RCS. Learn more | SMS | Dashboard, API |
| Open channel | An Open channel message can be sent to any medium that can accept a JSON payload. Learn more | Open channel | Dashboard, API |
Creating and sending messages
You can create and send messages in three ways: with a composer, in the Journey map, or through the Airship API.
Composers
A composer is a dashboard tool for creating a message in a linear, step-by-step flow.Use a composer for single messages:
1. For the app channel, the Message and Automation composers support push notifications, in-app messages, and Message Center.
Journey map
A Journey is a continuous user experience of connected Sequences, Scenes and/or In-App Automations. The Journey map is a dashboard tool for building those messages, either individually or connected to create a Journey.
Sequences support the same channels and message types as the Message and Automation composers. See Create a Sequence and Journeys.
API
To send messages using the API, see the Airship API reference. The API does not support Sequences, Scenes, In-App Automations, or Apple News. See Message types for API support per message type.
Reporting
After you send, measure performance and engagement. See About reports.
You can also set up integrations with Airship partners and use Real-Time Data StreamingA service that delivers user-level events in real time to your backend or third-party systems using the Data Streaming API. to send your Airship events to an outside system.