Initialise MoEngage SDK

Get APP ID from the Settings Page Dashboard --> Settings --> App --> General and initialize the MoEngage SDK in the Application class's onCreate()


It is recommended that you initialize the SDK on the main thread inside onCreate() and not create a worker thread and initialize the SDK on the worker thread.

val moEngage = MoEngage.Builder(applicationInstance, "Your App Id")
MoEInitializer.initializeDefaultInstance(applicationContext, moEngage)

Refer to the API reference doc for a detailed list of possible configurations.

Configure MoEngage Logs

import { MoEngageLogger, MoEngageLogLevel } from "react-native-segment-plugin-moengage";
MoEngageLogger.configureLogs(logLevel, isLogEnabledForReleaseBuild);

To configure the Android Native log, you need to configure the log in the MoEngage.Builder during Initialising the SDK using configureLogs(config).

Exclude MoEngage Storage File from Auto-Backup

This is a mandatory integration step and is essential to prevent your data from getting corrupted. Android's auto back-up service periodically backs up Shared Preference files, Database files, etc, more details here. This backup results in MoEngage SDK's identifiers being backed up and restored after re-install.This restoration of the identifier results in your data being corrupted and users not being reachable via push notifications.

To ensure data is not corrupted after a backup is restored, opt out of MoEngage SDK's storage files. Refer to Exclude MoEngage Storage File from the Auto-Backup section of the documentation to learn more about which files to exclude.

Data Redirection

In case your app wants to redirect data to a specific zone due to any data regulation policy please configure the zone in the MoEngage initializer object.  Refer to the Data Center documentation for more information.



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

How can we improve this article?