Last modified August 3, 2017 by Shelly Wolfe

Push Campaign Prerequisites

This article details the steps your development team must take before you can create push notification campaigns in Swrve. It also explains how to configure custom alert sounds or iOS action categories for your push notifications.


Technical Prerequisites

Depending on the app platform, your development team must complete the following tasks:

All Platforms

  • Update your app with the latest SDK – To make use of all of the features included in Swrve push notifications (for example, rich media, silent notifications, audience targeting), update your app with the latest Swrve SDK. For more information about integrating the SDK, see the platform-specific Integration Guide.
  • Time the push permission request – When a user first installs a push-enabled app, they are typically asked for permission to accept push notifications from the app. Swrve enables your development team to change this timing. For example, you can set the timing to request permission at the start of the session or when a user triggers one of a list of events. For more information, see the platform-specific Integration Guide.
  • Rich push notifications – to include rich content in your push notifications, such as media or custom buttons, upgrade your app to Swrve SDK version 4.11 or higher. For iOS, there are a few extra steps required to add the rich push service extension. For more information, see the iOS Integration Guide.
  • Test push notifications in the Swrve service – Before creating your first push notification campaign, your development team should test the push notification integration on QA devices. For more information, see QA Testing Push Notifications.
  • Configure launch screen – Optionally, enable your app to launch on a custom screen when opened from a push notification. For more information, see How Do I Configure the Launch Screen from a Push Notification?

iOS

  • Enable remote notification background mode for silent notifications – If you want to send background app updates, you must configure your app to process silent notifications in the background. For more information, see the iOS Integration Guide.
  • Create a push certificate and upload it to Swrve – If you’re not already using push notifications, your development team must create a push certificate, upload it to Swrve and test it. The certificate is used to authorize your app to receive push notifications and authorize Swrve to send push notifications to your app. For more information, see How Do I Manage iOS Push Certificates for Push Notifications?
  • Submit your updated app to Apple for review – After your development team has integrated the latest SDK, your iTunes Connect administrator must submit the app for review and inclusion in the App Store. As soon as it is available, your existing users are prompted to update the app while new users automatically get the latest version. This new app version then invokes the push permission request, logging device tokens back to Swrve, which you can then use to target those users by means of push notifications.

Android


Custom Alert Sounds

Swrve enables you to include a custom sound that is played when a user receives your push notification. To make a custom sound available to select in the push campaign workflow, you must first add add it to your app Push Notification Settings.

To add a custom sound:

Step 1: On the Campaigns menu, click Push Notifications.

Step 2: On the Push Notifications screen, click Settings.

Step 3: In the Custom Notification Alert Sounds section, click Add Sound.

Step 4: In the Add Sound dialog box, in the Friendly name field, enter a user-friendly name for your sound file.

Step 5: In the File name field, enter the actual name of your file, without the extension. For example, enter custom_sound for the filename custom_sound.wav.

Step 6: Click Create Sound.

You can now select the custom sound from the Alert Sound list on the Add Content screen of the push notification workflow.

For guidelines on using sounds with push notifications, see Push Notification Best Practices.


Custom iOS Action Categories

Swrve enables you to include custom action categories (for example, Yes/No, Ignore/Respond) when creating interactive push notifications on devices running iOS 8 or later. Before you can add or use custom categories in a push notification, you must provide any custom action categories when initializing the SDK and then add it to your app Push Notification Settings. For more information, see the iOS Integration Guide.

To add a custom action category:

Step 1: On the Campaigns menu, click Push Notifications.

Step 2: On the Push Notifications screen, click Settings.

Step 3: In the Custom Action Categories (iOS 8+) section, click Add Category.

Step 3: In the Add Custom Action Category (iOS 8+) dialog box, in the Friendly name field, enter a user-friendly name for the category (for example, Yes/No, Invite, Reminder).

Step 4: In the Identifier field, enter the identifier used in your app to identify this category (for example, INVITE_CATEGORY).

Step 5: Click Create Push category.

You can now select the custom action category from the iOS Category list on the Add Content screen of the push notification workflow.


Push Token Update Period

Swrve performs several batch jobs throughout the day to find users with push device tokens registered and then loads any new device tokens into the push notification system. Therefore, it can take up to six hours to add non-QA users to the system, depending on factors such as when the batch job is run and your company’s time zone. The number of devices registered on the Push Notifications screen for your app is updated regularly to include new users, but they may not be immediately available to send push notifications to, depending on the timing of the batch run (this does not apply to testing push notifications on QA devices).


Next Steps