Skip to main content
The MoEngage Android SDK runs inside your Kotlin or Java app. It tracks events and user attributes, registers push tokens with Firebase Cloud Messaging, and renders in-app messages and cards. Install it from Maven Central using the MoEngage Bill of Materials. Start with Integrating the Android SDK to add and initialize the SDK, then add the channels you need.

Sections in This Guide

SDK Integration

Configure build settings, install the SDK with the BOM, initialize it with your Workspace ID and data center, and add JWT authentication, proxy domains, and on-device encryption.

Data Tracking

Track events, user attributes, unique IDs, installs and updates, locale, and device identifiers, and configure tracking opt-outs.

Push

Set up FCM authentication, push token registration, runtime permissions, rich templates, amplified delivery, and location triggers.

In-App Messages

Display contextual in-app messages with the In-App NATIV SDK.

Personalize

Fetch and track personalized experience and offering campaigns natively through the SDK.

Recommendations

Fetch items from a MoEngage recommendation, configure the cache duration, and handle failures.

Cards

Deliver card campaigns with the MoEngage card UI, a Jetpack Compose feed, or your own card views.

Compliance

Complete Google Play’s Data Safety disclosure and manage user tracking consent.

Migration

Upgrade across major SDK versions and move to Maven Central, code-based integration, and the Firebase Installation ID.

OS Updates

Review Android release behavior changes that affect push notifications and deep links.

Performance

Review initialization time, memory, battery, and app size benchmarks for the SDK.

Troubleshooting and FAQs

Use the SDK logger and work through push, image, in-app, token, and exception problems.

Reference Pages

These pages sit outside the sections above:
Review the SDK Deprecation Policy for supported versions and deprecation timelines.