Enable Airship mobile push in SmarterSends using the credentials from your existing Airship Email integration. The push connection does not require a second set of Airship credentials.
SmarterSends targets the iOS and Android channels in your Airship project. Airship and the receiving devices determine which eligible channels receive and display a notification.
Before you begin
Confirm that:
- Airship is connected under Integrations → Email in SmarterSends.
- Your mobile apps have the Airship SDK and their platform push configuration in place.
- The Airship project contains the segments you will use for live campaigns and registered mobile channels eligible to receive push.
- Test devices are associated with the intended Named User ID in Airship.
- An Admin is available to configure the integration.
A Named User ID is an identifier your app or integration assigns to a person and associates with their channels. It is not automatically the same as their email address. See Airship's Named User guide.
Enable mobile push
- Sign in as an Admin and open Integrations.
- Select the Mobile Push/In-App card.
- In Mobile Push/In-App Integration, choose Airship under Push Provider.
- No additional push credentials or platform IDs are required in this form.
- If Test API Access appears, select it to validate the form and reveal Save.
- Select Save and confirm Push Settings Updated.
The form's check does not deliver a push to a device. Complete a device test before sending to an audience.
The In-App Messages toggle enables the separate Airship in-app banner workflow. It is not required to send ordinary push notifications. Push and in-app messaging share this integration configuration.
Give your team the right access
| Task | SmarterSends access |
|---|---|
| Configure the connection | Admin |
| Create and edit push templates | Manage Templates |
| Create push campaigns | Create Push |
| Send directly within the account's rules | Send Push, subject to approval settings, template rules and scheduling restrictions |
Create Push does not grant template-management access. A template manager must prepare and publish a push template for the intended groups.
Prepare a template and campaign
- Open Manage → Templates and choose Create Push Template from the Create Template menu.
- Complete the template details and group assignments, then configure its content and the platform options your app supports.
- Add Content Areas for the values campaign creators should change. Save and test the template, then publish it for the assigned groups.
- In the intended group, open Campaigns → Create Campaign, select a published Push template and complete the editable fields.
- Test the message on your registered device before selecting the live audience and completing the send workflow.
See Templates Overview for publication, group assignments and editable content.
Test with a Named User ID
Current test-field limitation: The push editor labels its field Test Email Address... and validates an email-formatted value. The Airship send request uses that exact value as the Named User ID; it does not look up a Named User ID from an email address.
- Confirm the test device's exact Named User ID in Airship.
- If that ID is itself email-formatted, enter it in Test Email Address....
- Select Send Test. This saves the campaign and sends to the mobile channels associated with that Named User ID.
- Check the notification on the device, including its content, images where configured and tap action. Check each mobile platform you support.
If your Named User ID is not email-formatted, contact SmarterSends support about the current test-field limitation. Do not enter a person's email unless it is also their exact Named User ID.
An Airship test request can target multiple mobile channels associated with the same Named User ID. Test requests also bypass Airship frequency limits, so a successful test does not establish that a live campaign will pass the same delivery restrictions.
Send to a live audience
Live push campaigns use the selected Airship segments, with applicable SmarterSends group restrictions and exclusions. They target both iOS and Android; selecting a segment does not guarantee it contains eligible mobile channels.
Review the audience, content and send time, then submit for approval or use the available Send Campaign or Schedule Campaign action. Delivery still depends on the registered channels, push opt-in state, platform configuration and provider rules.
Troubleshooting
| What you see | What to check |
|---|---|
| Airship is not offered as Push Provider | Confirm Airship is the connected Email provider. |
| No option to create push templates | Check that Mobile Push/In-App is connected and the user has Manage Templates. |
| No push campaign or template available | Check Create Push, template publication, group assignments and template filters. |
| Named User ID is rejected by the test field | The current form requires an email-formatted ID. Contact support for other ID formats. |
| Test is accepted but nothing arrives | Check the exact Named User ID, associated iOS/Android channels, opt-in state and app configuration. |
| A live campaign has no eligible recipients | Confirm the segments contain mobile channels and review group restrictions, exclusions and Airship delivery rules. |
| Credentials need updating | Update the main Airship connection under Integrations → Email, then test the push workflow. |
Comments
0 comments
Article is closed for comments.