Register your iOS app with Blueshift

Provides information how to register your app with Blueshift so that you can run campaigns and send promotional messages to your customers who use your iOS app.

Ensure that your applications are registered with us as a channel on the Blueshift app. To setup a channel, perform the following steps:

  1. Sign in to the Blueshift app.
  2. On the top right corner, click on the settings icon > Channels.

Based on your requirements, follow the steps either under the Single App account or Multi App account.

Single app account

a. Select Blueshift Push under Mobile on the Setup Channels page that appears. The Blueshift Push section opens that lists Android and iOS adapters.

b. To add a new iOS adapter, click +ADD APNS APPLICATION and provide the details.

  • Application Name: Provide the name of the application that you have integrated with Blueshift. The name can be anything but the android and iOS app names need to be unique for that adapter.
  • Bundle Id: Provide the application’s bundle ID that uniquely identifies your app. For more information, see Bundle IDs.
  • Environment: Choose Production or Sandbox based on your application build type. To know more about the Environment selection refer to this section.
  • PEM File: Upload the .pem file. For more information on the .pem file, see Generate a .pem file.
  • PEM File Password: Provide the password that protects the .pem file. If you generated a .pem file from a .p12 file that was created with a password, provide the password here.

c. Click Save and set the adapter as default.

Multi app account

a. Select Blueshift Push under Mobile on the Setup Channels page that appears. The Blueshift Push section opens that lists all the adapters.

If you want to register a new app, click + ADAPTER and provide an Alias Name for this adapter. This is used for identifying the adapter. Or else, click on the name of the existing adapter.
b. Click + ADD APNS APPLICATION on the page to provide the following details:

  • Application Name: Provide the name of the application that you have integrated with Blueshift. The name can be anything but the android and iOS app names need to be unique for that adapter.
  • Bundle Id: Provide the application’s bundle ID that uniquely identifies your app. For more information, see Bundle IDs. You can not create multiple adapters using the same bundle id, but you can use the same bundle id for the Android and iOS apps in the same adapter.
  • Environment: Choose Production or Sandbox based on your application build type. To know more about the Environment selection refer to this section.
  • PEM File: Upload the .pem file. For more information on the .pem file, see Generate a .pem file.
  • PEM File Password: Provide the password that protects the .pem file. If you generated a .pem file from a .p12 file that was created with a password, provide the password here.
    c. Click Save and set the adapter as default. This default adapter will be used for test push sends/campaign sends if no adapter is selected.

If you have an Android version of this app and you want to register it with us so that you can send notifications to your Android app’s users using our platform, click + ADD FCM/GCM APPLICATION and perform the steps described in the fifth section of this document.

If you have multiple applications that you want to register, go back to the Blueshift Push adapters index page, and follow step 4 through the end of the procedure above.

Environment Selection For Push Adapter

Blueshift can have only one APNS configuration per push adapter. You can either set it up for Sandbox or Production environment based on the application build type. This Sandbox or Production environment value will be used to select the associated APNS API endpoint to send push notifications.

The Development build requires the Sandbox environment to be set for the push adaptor, while Test Flight/Ad Hoc/Distribution/App Store builds require the Production environment to be set for push adapter.

In case, you have set Production environment for an adapter and you want to modify it to the Sandbox, you can delete the existing APNS configuration and add it again with the Sandbox environment and supported pem file.


Did this page help you?