App platform

PushEngage for Android

Add push notifications and in-app messages to a native Android app with the PushEngage Android SDK for Java and Kotlin. It delivers through Firebase Cloud Messaging and adds segmentation, campaign tools, and analytics that your team runs from the PushEngage dashboard.

What you can do with Android

Permission handling for Android 13 and later

One SDK call shows the system permission dialog and subscribes the user when they allow notifications. On Android 12 and earlier, permission is granted automatically.

Works with Jetpack Compose

The SDK takes a ComponentActivity, so Compose apps need no adapters or wrappers. A dedicated guide covers permissions, subscriber management, and deep links in Compose.

Rich notifications, groups, and channels

Send images, action buttons, and deep links, and use Android notification groups and channels to control how each type of notification looks, sounds, and behaves.

Segments, attributes, and triggered campaigns

Add subscribers to static or dynamic segments, set custom attributes, and send trigger events, goals, and price drop or inventory alerts from your app code.

In-app messages

Show banners, modals, and full-screen messages designed on the dashboard. There is no extra setup once the SDK is initialized with your App ID.

Keep your existing subscribers

If you configure PushEngage with the Firebase Sender ID your app already uses, existing device tokens stay valid and users are not asked for permission again.

How to set it up

  1. Add the JitPack repository, the PushEngage SDK dependency, and the Google Services plugin to your Gradle files.
  2. In the Firebase console, add your Android app to a project, place google-services.json in your app module, generate a Service Account JSON key, and copy the Sender ID.
  3. In PushEngage, open Site Settings > Installation > Android SDK. Enter the Sender ID, upload the Service Account JSON, click Update, and copy the App ID.
  4. Initialize the SDK with the App ID in your Application class, and register that class in AndroidManifest.xml.
  5. On Android 13 and later, request notification permission from your main Activity with the SDK's permission method.
  6. Run the app on a physical device and send a test from Campaign > Push Broadcasts.

Full guide: Android quickstart

Good to know

  • App push and this SDK are listed on every PushEngage plan, including the free plan. Goal tracking, custom triggered campaigns, and in-app messages need a paid plan.
  • The SDK supports minSdkVersion 16 (Android 4.1) or higher. The quickstart recommends API 21 or later.
  • You need a Firebase project. Notifications are delivered through Firebase Cloud Messaging, and PushEngage needs your Sender ID and a Service Account JSON.
  • The permission request has to be called from an Activity that extends ComponentActivity, such as AppCompatActivity.
  • If a user denies permission on Android 13 or later, the system blocks further prompts. Link them to the app's notification settings instead.
  • Test on a physical device. The quickstart notes that push does not work in the emulator.

About this connection

  • PushEngage builds and maintains this SDK. It is not a partnership with Google; delivery runs through Firebase Cloud Messaging using your own Firebase project.
  • The source is public on GitHub in the awesomemotive/pushengage-android-sdk repository under the MIT license.
  • The SDK is distributed through JitPack. It is not published on Maven Central.
  • PushEngage also publishes open-source Agent Skills, so an AI coding agent such as Claude Code or Cursor can run the integration and diagnose a broken setup.

PushEngage Partner Directory

Ready to add push to your Android app? Start with the setup guide.

PushEngage has a free plan, so you can install it and send your first campaign before you pay anything.