Skip to main content

Initializing the SDK

Initialize the SDK on the main thread inside onCreate() and not create a worker thread and initialize the SDK on that thread.
Following details of the different data centers you need to set based on the dashboard hosts
Data CenterDashboard host
DataCenter.DATA_CENTER_1dashboard-01.moengage.com
DataCenter.DATA_CENTER_2dashboard-02.moengage.com
DataCenter.DATA_CENTER_3dashboard-03.moengage.com
DataCenter.DATA_CENTER_4dashboard-04.moengage.com
DataCenter.DATA_CENTER_5dashboard-05.moengage.com
Refer to the API reference for more information about the detailed list of possible configurations.
All the configurations are added to the builder before initialization. If you are calling initialize at multiple places, ensure that all the required flags and configurations are set each time you initialize to maintain consistency in behavior.
In case your application does not have an Application class yet navigate to the java source code inside the android platform folder and add the Application class file. Android SDK Initialization1 Make sure your application class is defined in the AndroidManifest.xml file as well.

Register MoEngage’s Plugin

Register the plugin in your Activity class’s onCreate().

Exclude MoEngage Storage File from Auto-Backup

This is a mandatory integration step and is very 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.