Skip to end of metadata
Go to start of metadata

Last Updated: Wednesday, December 9, 2020

You can integrate your iOS or Android app with the Vibes Mobile Engagement Platform to send push messages to the Vibes SDK.

Key Integration Steps

  • Implement basic device and push registration to simple push notifications using the Vibes SDK
  • Enable association of push to device API or SDK call.  This will make a user "known" and allow for platform targeting and segmentation. 
  • Add advanced push options:  rich push, notification sounds, deep linking, etc (Optional)
  • Add app inbox support (Optional)

Note:  Platform accounts are available via the platform for development and UAT testing. 

Topics in this Section

Technical Integration Overview

  1. Request an app_id from Vibes. The app_id uniquely identifies the application and will be needed to configure the SDK. The app_id will be the same for the Android and iOS apps.
    • Developers will need a test app_id for development release, and a production app_id for the production release. Vibes uses production to test the integration to ensure no environmental difference. Different IDs will allow the apps and their data to be used and tracked separately.  
  2. Retrieve the SDK from the Android and iOS repositories. 
  3. Add the SDK to your apps. Examples of how to add the SDK to your app can be referenced in our Android and iOS example apps in the Github repository

  4. To enable push notifications in the background for your iOS application, do the following:

    1. Click your project, for example, the ios-sdk-example-app.

    2. Click the Capabilities tab.

    3. Turn Background Modes On, then click the Remote notifications check box.

  5. Set up push notification keys for your app on Apple and Google developer portals so that the app will be able to receive push notifications. 
    • Apple will provide an APNS certificate and private key, typically in the form of a .p12 file.
    • Google will provide a server key.
  6. Transfer those Apple and Google push notification keys and bundle IDs to Vibes.
  7. Configure a server-to-server call to Associate Person to Device.

  8. Complete development and UAT testing for the app release using a platform test account.   
  9. Release the app with the Vibes Push SDK.


While testing, it is typical to have one Vibes app_id for your test app, and a separate app_id for your production app. We recommend using different bundle IDs (iOS) and application IDs (Android) for each environment, as using the same value for different environments can cause unexpected behavior.

However, if you find that you can't use separate values for bundle ID / application ID for each Vibes app_id, then make sure you clear the application data when switching between apps for each environment.

  • No labels