Skip to main content
The Android Push editor is a form with title, message, image, action URL, and buttons — with a live device preview on the right. Content is personalised with Handlebars variables ({{variable_name}}).

​
Android Push fields

Title — single-line heading. Keep under 40 characters — Android truncates to one line. Supports Handlebars variables. Small Icon — icon in the status bar and notification header. Defaults to the SuprSend bell icon. See custom icon setup to use your app icon. Large Icon — appears left of the text on Android 4.0–6.0, right on Android 7.0+. Defaults to your organisation logo (set in Organisation Settings). Message — multi-line body text. Front-load key info in the first 2 lines (expanded view shows ~6 lines). Supports Handlebars variables. Subtext — optional. Appears next to your brand name at the top of the notification. Banner Image — optional. Supported formats: PNG, JPG, JPEG. Recommended: 2:1 aspect ratio, under 700 KB. Static uploads are auto-scaled and optimised by SuprSend. Action URL — URL opened on notification tap. Supports deep links and Handlebars variables. Action Buttons — optional. Up to 3 buttons with label + URL. Use 1-2 buttons with concise labels (2-3 words): “Track Order”, “View Details”. Supports Handlebars in both fields. Button colour is set in Organisation Settings.

​
Adding dynamic content in Android Push

There will always be the case where you would be required to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending push. To send actual values to replace variables at the time of communication trigger, use one of our frontend or backend SDKs. Here is a step-by-step guide:
1

Add variables in the Variables panel

Add sample data in the Variables panel (Input Payload section) on the left side of the editor. If you have declared the variables and added sample data, they will come as auto-suggestions when you type a curly bracket {. This removes the chances of error like variable mismatch at the time of template rendering. To see how to declare variables, refer to this section in the Templates documentation.
2

Use variables in the template

We support handlebars to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable_name}}Note that you will be able to enter a variable name even when you have not declared it in the Variables panel. To manually enter the variable name, follow the handlebars guide here.Below are some examples:
{
  "array": [
    {
      "product_name": "Aldo Sling Bag",
      "product_price": "3,950.00"
    },
    {
      "product_name": "Clarles & Keith Women Slipper, Biege, 38UK",
      "product_price": "2,549.00"
    },
    {
      "product_name": "RayBan Sunglasses",
      "product_price": "7,899.00"
    }
  ],
  "event": {
    "location": {
      "city": "Bangalore",
      "state": "KA"
    },
    "order_id": "11200123",
    "first_name": "Nikita"
  },
  "product_page": "https://www.suprsend.com"
}
  • To enter a nested variable: {{event.location.city}}
  • To refer to an array element: {{array.[0].product_name}}
  • If you have a space in the variable name: {{event.[first name]}}
You will be able to see the sample values in the Preview section. If a variable isn’t rendering, check:
  1. The variable is defined in the Variables panel.
  2. The variable name matches the Handlebars syntax exactly.
At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user.Please note that the rest of the templates will be sent. E.g. if there is an error in rendering Android Push template, but email template is successfully rendered, Android Push notification will not be triggered, but email notification will be triggered by SuprSend.

​
Advanced configurations

FieldTypeDescription
SilentBooleanUsers won’t see this message. Triggers background activities using the notification payload. Useful for data sync, content pre-fetching, or breaking news alerts.
TimeoutNumericAuto-dismiss after N seconds if the user hasn’t interacted. Combine with Sticky for urgent time-limited alerts (e.g., 2FA prompts).
Sticky NotificationsBooleanPrevents swipe-dismiss. Removed only when the user taps the notification.
Notification GroupTextGroup name to stack related notifications (e.g., chat messages from the same conversation) to avoid flooding the tray.
App Icon (Small Icon)TextIcon name without extension. See custom icon setup in the FAQ below.
SoundTextSound file name. See custom sound setup in the FAQ below.
Custom Key-Value PairsKey-valueSend custom data to the app. Both key and value are strings. Combine with silent notifications for background data updates.
SDK version requirements:
  • App icon: Android native and React Native SDK version 0.1.8+
  • Custom sound: Android native and React Native SDK version 2.2.0+

​
Preview and test

The right panel shows a live Android device preview, updated in real time as you edit. Variables render using data from the Variables panel. Click Test in the top-right corner to send a real push notification to a real device. This uses the live version — commit your changes before testing. See Testing a Template for the full guide.

​
Commit

Click Commit in the top bar to publish the current draft as a new live version. Add an optional description for versioning. Once committed, all notifications triggered after this point use the new content.

​
Common scenarios

FieldValue
TitleOrder #{{order_id}} shipped
MessageYour package is on the way! Expected delivery: {{delivery_date}}
Banner Image{{product_image_url}}
Action URLhttps://yourapp.com/track/{{order_id}}
FieldValue
TitleFlash sale ends tonight
MessageUp to 50% off on your favourites. Don't miss out!
Banner Image(static promotional banner)
Button 1Shop Now → https://yourapp.com/sale
Button 2View Wishlist → yourapp://wishlist
FieldValue
SilentON
Custom Key-Value Pairssync_type = catalog_update, version = {{catalog_version}}
Use silent notifications to trigger background data fetches — e.g., pre-loading content so it’s ready when the user opens the app.

​
Frequently asked questions

Add a small icon named ic_suprsend_app_icon in the drawable folders of your app. Android only uses the alpha channel — the icon displays as monochrome in the status bar. You can use a vector drawable (androidApp/src/main/res/drawable/) or PNG icons at each density:
DensitySize
MDPI24x24
HDPI36x36
XHDPI48x48
XXHDPI72x72
XXXHDPI96x96
Use Android Asset Studio for quick icon generation. If you see the default bell icon, ensure all density sizes are present. If you see a solid square, the image lacks alpha transparency.SDK requirement: Android native and React Native SDK version 0.1.8+.
Add the sound file to projectroot/app/res/raw (lowercase filename, underscores instead of spaces, e.g. notification_music.mp3).Important: On Android 8.0+ (~95% of users), sound is set at the notification channel level when the category is first created. Changing the sound in the template only takes effect for:
  • a new notification category
  • a user installing the app for the first time
  • a user who uninstalled and reinstalled the app
SDK requirement: Android native and React Native SDK version 2.2.0+.
For static images uploaded in the Banner Image field, SuprSend applies two optimisations:
  • Screen width — large images are resized to fit the user’s mobile screen width.
  • Network-aware — image quality is adjusted based on the user’s connection (WiFi, 4G, 3G, 2G) to improve delivery speed on slow networks.
Silent notifications deliver a payload to the app without displaying anything to the user. Use them for background data sync, content pre-fetching, or triggering app-level logic. Combine with Custom Key-Value Pairs to pass structured data.
SuprSend discards the Android Push notification for that user. Other channels in the same template group (email, SMS, etc.) are still sent if they render successfully.