Blueshift provides native push and in app notification services for both Android and iOS devices. You can integrate Blueshift SDKs in your mobile apps to start sending rich push and in-app notifications from Blueshift’s campaign journey. Blueshift’s push and in-app notification service is fast, reliable, and can scale to millions of messages.
Blueshift’s push and in-app studio allows you to build best-in-class notification templates with ease and manage them easily by tagging.
For more information about Blueshift's SDKs, visit our Developer Portal.
Prerequisites
Before you can set up integration with Blueshift, you must get the Authorization Key from your Firebase project. The Firebase/Google Cloud app Server Key is required to set up integration with Blueshift.
To get the Server Key, complete the following steps:
Go to https://console.firebase.google.com/ and select your Firebase project.
Go to Project Settings by clicking the gear icon next to Project Overview.
Go to the Cloud Messaging tab and to the Cloud Messaging API (Legacy) section.
If the Cloud Messaging API (Legacy) section shows as disabled, complete the following steps:
Click the three dots for the section to open the Google Cloud Console.
Click ENABLE to enable Cloud Messaging API (Legacy).
Refresh the Cloud Messaging tab.
Copy the server key provided in the Cloud Messaging API (Legacy) section. Use this key as the Authorization Key for the adapter in Blueshift.
Set up integration
To set up integration, complete the following steps:
Sign in to the Blueshift app, and click App Hub in the left navigation menu.
Go to All Apps, search for, and select Blueshift Push.
You can also go to Mobile Marketing Apps and select Blueshift Push.
Click Configure to view the default adapter.
Click Edit Adapter to edit the adapter settings.
Provide the following details for your Android app:
Provide the following details for your iOS app:
Click Create to add the adapter.
Android app
Field | Description |
Application Name | This is the name of your application. |
Authorization Key | This is the FCM Server key for your Firebase project. |
iOS app
Field | Description |
Application Name | This is the name of your application. |
Bundle Id | Provide the application's bundle ID that uniquely identifies your app. For more information, see Bundle IDs. |
Environment | Select Production or Sandbox based on your application build type. For more information, see Environment selection. |
Select Authentication Method | Choose Token-based authentication (recommended) or Certificate-based authentication. |
APNS Token | Upload the .p8 authentication key. For more information, see Generate a .p8 authentication key. |
Key ID | Provide the Key ID associated with your .p8 authentication key. |
Team ID | Provide your Apple Developer Team ID. |
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. |
Next steps
Create a Push template or an In-app template for your messages.
In your campaign journey, add a Push trigger or In-app trigger. On the Push or In-app tab of the trigger, go to Send Settings and specify Blueshift Push as the App, then select the adapter you just created.