The mobile push channel in the Business Messaging API is a solution for Android or iOS developers that want to send push notifications to their apps using phone numbers instead of the standard Firebase or APNS tokens or credentials. Devices without a SIM card (e.g. tablet, iPad) are also supported by using installation identifiers instead of phone numbers.

The push client consists of a library that needs to be included in your iOS and/or Android project. The library allows for receiving incoming push messages and optionally for registering an end-users phone number via an OTP.

There is a version 1 and version 2 of the push client SDK. Version 2 of the SDK supports rich features, the fact sheet below is based on V2.

When sending messages via mobile push using the Business Messaging API, the CM platform will look up the corresponding push token for the given phone number or installation identifier. If a push token is present, the push message will be send out. Our client libraries will allow you to receive them. Sending push messages by phone number also allows for a fallback to SMS.

Fact sheet

The fact sheet below assumes you are using the SDK V2. V1 only supports simple text and data delivery.

FeatureSupportRemarks
encryptionpartlythere is no end-to-end encryption; messages are sent over https to CM and pushed to FCM or APNs using SSL
text messagesyesmessages have a maximum size of ~4Kb
emojis in textyessending an emoji in unicode is possible
urls in textyes/noIn iOS the URLs are clickable after opening a push message. Android will display URLs, but they are not clickable.
rich textno
mediayes*Media name attribute should end in the proper file extension. Only one media file is allowed per message; when sending multiple files, each file will be sent in its own Mobile Push message. When the linked media doesn't exist/can't be found, the message will not be sent at all.
media: imagesyes*Maximum file size for an uploaded image is 10 MB. Sending very large images is not recommended, because it might take the app a while to download them. Supported MIME types are: image/jpeg, image/png.
media: gifsyes*Maximum file size for an uploaded GIF is 10 MB. Sending very large GIFs is not recommended, because it might take the app a while to download them. Supported MIME type: image/gif.
media: videopossible*Maximum file size for an uploaded video is 50 MB. Sending very large videos is not recommended. Supported MIME types: video/mp4. Video is not supported by default in Android but you can intercept the message via the SDK to display it on your own accords within your app.
media: audiopossible*Maximum file size for an uploaded audio is 5 MB. Supported MIME types: audio/mpeg, audio/m4a. Audio is not supported by default in Android but you can intercept the message via the SDK to display it on your own accords within your app.
media: documentpossible*Maximum file size for an uploaded document is 10 MB. Display is up to the client app. All common MIME types supported. For example: application/pdf. Document is not supported by default but you can intercept the message via the SDK to display it on your own accords within your app.
reply suggestionspossible*Maximum label length: 25 characters. OpenUrl supported by default, other suggestions you be intercepted via the SDK to display it on your own accords within your app.

🚧

Note*

Only supported by making use of CMPush V2 SDK, not supported via SMS fallback.

Notifire

Notifire is a publicly available mobile app of CM that you can use for sending push notifications if you don't have the capabilities to build your own mobile app.

If you want to make use of Notifire, you can skip the onboarding steps and go immediately to sending a message.

Onboarding

The user base for the push channel consist of iOS and Android developers. Using the available libraries they can build an app that supports receiving push messages sent via the Business Messaging API to a phone number, with a fallback to SMS if needed.

We need credentials from the Google's FCM and/or Apple's APNs development environments to allow us to push messages to the app that's being developed.

Onboarding is available as early access via our Channels portal. In the portal, you will be presented with an onboarding page in which you have to provide CM.com information about your mobile app such as credentials from the Google's FCM and/or Apple's APNs development environments.

Integrating the libraries into your app

Android

To enable pushing messages to an Android app you need to add Firebase to your app and you have to add the CMPush Android library to your project.

The library itself and a detailed explanation of how to add it to your Android Project is available on the official GitHub repo for the Android library

iOS

To enable pushing messages to your iOS app you need to enable push in your app settings and you have to add the CMPush framework to your project.
The framework and a detailed explanation of how to add it to your iOS Project is available on the official GitHub repo for the iOS library.

Business rules

In other channels, like Twitter or WhatApp, the client applications are produced by 3rd parties. In the case of push, you write your own client. Therefore, there are no 3rd party guidelines or regulations regarding messages. However, we do adhere to the general rules for sending messages using the CM platform found here:
https://www.cm.com/en-gb/app/legal/cm-com/terms-and-conditions/

Considerations

The costs of the OTP calls will be debited on your account at CM.

To prevent abuse, OTP calls are throttled at:

  • 3 attempts per phone number per 5 minutes
  • 3 attempts per installation id per 5 minutes
  • 6 attempts per IP address per 5 minutes

Limitations of CMPush V1

When making use of the CMPush V1 SDK, the following limitations are applicable:

  • Mobile Push works in a single direction, from the Business Messaging API to the end-user's phone (MT, or mobile-terminated). As the end-user has no way to respond to push messages, there is no MO (mobile-originated) traffic.

    An exception are status reports (SRs). These are sent when a message is received by the app on the end user's phone and they will arrive in the status report webhook.

  • While we keep a list of installation identifiers, phone numbers and corresponding push credentials on our platform, this data is only available for reference via events when making use of CMPush V2 SDK. For V1, this means you should implement some functionailty in your own app that notifies you when a device is onboarded successfully, and that stores the installation identifier and phone number in a database you manage.
    You could, for example, develop a webhook somewhere that you can call to pass data of the users that installed your app.

prerequisites

Before you can implement the push channel in your iOS or Android apps, you should have a developer account and a project set up at Apple and/or Google.

Sending a message

Sending a message works in much the same way as sending an SMS message.

In the onboarding process of your mobile app, we will provide you with a unique sender id called a channel account id to use in the dedicated appkey field.

❗️

Warning

The channel account id is the identifier of your app within CM and should never be incorporated into webpages or open-source software where it can be exposed to 3rd parties.

The to field can either be

  • Recipients phone number
  • Recipients installation id, fallback if user hasn't configured their phone number in your app

The from field is optional where you can specify the sender for a fallback SMS.

If you want to make use of Notifire, you must provide an empty UUID as your channel account id: 00000000-0000-0000-0000-000000000000.

Receiving a message / Inbound flow

Push is a one-way communications channel, but we do send status reports that indicate whether a message arrived in your client app.

To receive these status reports, you will need to configure an inbound flow. You can find more information about how to do this using our status report webhooks in the messaging gateway app.

Message examples

Below you will find an example of a simple push message.

Direct message with plain text

{
  "messages": {
    "authentication": {
      "producttoken": "Your product token"
    },
    "msg": [
      {
        "allowedChannels": ["MobilePush", "SMS"],
        "from": "Your sender",
        "to": [{
            "number": "Recipients phone number/installation identifier"
        }],
        "body": {
          "type": "auto",
          "content": "This is the content of my push message."
        },
        "appkey": "Your channel account"
      }
    ]
  }
}

Direct message with plain text to Notifire

{
  "messages": {
    "authentication": {
      "producttoken": "Your product token"
    },
    "msg": [
      {
        "allowedChannels": ["MobilePush", "SMS"],
        "from": "Your sender",
        "to": [{
            "number": "Recipients phone number/installation identifier"
        }],
        "body": {
          "type": "auto",
          "content": "This is a message towards Notifire."
        },
        "appkey": "00000000-0000-0000-0000-000000000000"
      }
    ]
  }
}

Direct message with text and image

In the example below we send a simple rich content message that contains both text and an image.

Only supported if your app makes use of CMPush V2 SDK.

{
   "messages":{
      "authentication":{
         "producttoken":"Your product token"
      },
      "msg":[
         {
            "allowedChannels":[
               "MobilePush"
            ],
            "from":"Your sender",
            "to":[
               {
                  "number":"Recipients phone number/installation identifier"
               }
            ],
            "body":{
               "type":"auto",
               "content":"Fallback Text"
            },
            "richContent":{
               "conversation":[
                  {
                     "text":"CM.com - Be part of it.",
                     "media":{
                        "mediaName":"cm-tablet.jpg",
                        "mediaUri":"https://www.cm.com/cdn/web/blog/featured/cm-tablet.jpg",
                        "mimeType":"image/jpeg"
                     }
                  }
               ]
            }
         }
      ]
   }
}

Direct message with reply suggestion

In the example below we send a rich content message that contains a text and some reply suggestions.

Only supported if your app makes use of CMPush V2 SDK.

{
   "messages":{
      "authentication":{
         "producttoken":"Your product token"
      },
      "msg":[
         {
            "allowedChannels":[
               "MobilePush"
            ],
            "from":"Your sender",
            "to":[
               {
                  "number":"Recipients phone number/installation identifier"
               }
            ],
            "body":{
               "type":"auto",
               "content":"Fallback Text"
            },
            "richContent":{
               "conversation":[
                  {
                     "text":"CM.com - Be part of it.",
                     "suggestions":[
                        {
                           "action":"Reply",
                           "label":"Call me",
                           "postbackdata":"CALL"
                        },
                        {
                           "action":"Reply",
                           "label":"Email me",
                           "postbackdata":"EMAIL"
                        },
                        {
                           "action":"Reply",
                           "label":"Send me an sms",
                           "postbackdata":"SMS"
                        }
                     ]
                  }
               ]
            }
         }
      ]
   }
}

Direct message rich card content

In the example below we send a rich content message that contains elements that can be displayed as a rich card.

Only supported if your app makes use of CMPush V2 SDK.

{
   "messages":{
      "authentication":{
         "producttoken":"Your product token"
      },
      "msg":[
         {
            "allowedChannels":[
               "MobilePush"
            ],
            "from":"Your sender",
            "to":[
               {
                  "number":"Recipients phone number/installation identifier"
               }
            ],
            "body":{
               "type":"auto",
               "content":"Fallback Text"
            },
            "richContent":{
               "conversation":[
                  {
                     "header":"Contact options",
                     "text":"Hi, what can I do for you?",
                     "media":{
                        "mediaName":"cm-tablet.jpg",
                        "mediaUri":"https://www.cm.com/cdn/web/blog/featured/cm-tablet.jpg",
                        "mimeType":"image/jpeg"
                     },
                     "suggestions":[
                        {
                           "action":"Reply",
                           "label":"Call me",
                           "postbackdata":"call-me"
                        },
                        {
                           "action":"Reply",
                           "label":"Email me",
                           "postbackdata":"email-me"
                        },
                        {
                           "action":"Reply",
                           "label":"Send me an sms",
                           "postbackdata":"send-me-sms"
                        }
                     ]
                  }
               ]
            }
         }
      ]
   }
}

Did this page help you?