Create App Push

When you want to create an App Push you first choose the module (Campaign or Journey) for your send out and hit Create new (or if in Journey, add a Push message step).

First you need to decide which platform you want to send the notification to. Symplify supports iOS, Firebase (Android), Windows and QQ.
Note that this doesn’t necessary mean that you support all applications and/or have implemented Symplify for each of these platforms.


Then you select the project and template you want to use and hit Create.

The editor will open and you enter your settings like the internal name of your message and the certification type (iOS).

Select which app you want to use for your Push (you can connect several apps to Symplify but you need to select one of them when sending a notification).
Then select the list and, if any, segment you want to send to.


And then you also need to edit the push notification data.


But, before we continue…

When you create a push notification it’s important to know how you have implemented your application with Symplify. This is important since the integration affects what settings and content you might need to edit in your draft in Symplify.
The developers on your end are free to implement the Push functionality in different ways.

The main question for you is:

“What happens when a recipient clicks on a push notification?”

If you don’t know the answer of that question you should turn your application developers. This is why:

Depending on how the implementation is made, there are different options here:

  1. Symplify rich content will open. Symplify offers a unique opportunity for you to create personalized landing pages that will open when the notification is clicked on. From here you can link to your app or to other destinations.
  2. Your app will open. If you want to redirect to a specific place in your app you can add meta data containing specific key values that will tell your app the destination of the recipients.
  3. Nothing will happen. Only the notification will be showed. You can add tracking to find out if it has been read.

There could also be a combined solution of 1 and 2 where your app first checks if there are any key values with a destination, if yes, the app will open the given destination and if no, Symplify rich content will open.




On the Data tab, you edit the notification and, if any, meta data. Meta data could be the information you send to your actual application and you’re free to add as many extra key and values as you want. Default key and value pairs:

  • Alert – the first row in your notification
  • Info – the second row in your notification (mandatory for iOS)
  • Category – tag your notification
  • Badge – the number showing next to your app on the recipient device
  • Sound – the sound that will be played when a notification is received (if you have this built in your application).

In the example below we’ve added the custom key “app_destination” which in our example will tell our app to redirect to a specific place within the app when the recipients clicks the notification, the key value forecast will tell the app that specific place (method 2 above).


As mentioned above, you can also add custom key/value pairs depending on what data you want to provide your application with.


Symplify rich content

On Content you can create a specific landing page which will open when opening the notification (method 1 above) edit your message the way you want it and add content segments. Here you have the chance to create a personalized message and link to your application.


Character limitations

The maximum character count for push notifications to Android is 65 for the title and 240 for the message (info) and 178 for iOS (info).

However, the ideal number of characters on Android is around 39 characters for the title and 150 characters for the message. This limit ensures a full display of push notification and applies to most devices, browsers, and operating systems.


Message size limitations

The full message (the notification along with optional custom data) can not be bigger than 4KB (4096 bytes). This will be refused by the receiving service and the tokens will get invalidated.





Was this article helpful?
0 out of 0 found this helpful