Engage helps businesses deliver personalized customer messaging and marketing automation through email, SMS and in-app messaging. This Android SDK makes it easy to identify customers, sync customer data (attributes, events and device tokens) to the Engage dashboard and send in-app messages to customers.

• Track device token
• Identify users
• Update user attributes
• Track user events

• Create an Engage account and set up an account to get your public API key.
• Learn about connecting customer data to Engage.

The SDK is published through JitPack. Add it to your root build.gradle.

allprojects {
  repositories {
    ...
    maven { url 'https://jitpack.io' }
  }
}

Next, add the dependency.

dependencies {
  implementation 'com.github.engage-so:engage-android:v1.0.0'
}

Ensure your app includes INTERNET permission as it is needed to sync data.

<uses-permission android:name="android.permission.INTERNET"/>

Import so.engage.android.sdk.Engage and initialize the SDK.

// ...
import so.engage.android.sdk.Engage;

public class MainActivity extends AppCompatActivity {
  // ...
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    Engage.init("public-api-key");

Engage uses your user's unique identifier (this is mostly the ID field of the users' table) for data tracking. Identify lets you link this ID to the user. With identify, you are able to supply more details about the user.

private void updateUiWithUser(LoggedInUserView model) {
  // ...
  // model.getDisplayId() is the user's unique id
  HashMap<String, Object> attributes = new HashMap<String, Object>();
  attributes.put("first_name", model.getDisplayName());
  attributes.put("last_login", new Date());
  Engage.identify(model.getDisplayId(), attributes);

Engage supports the following standard attributes: first_name, last_name, email, number (customer's phone number) but you can use identify to add any customer attribute you want. last_login in the example above is an example.

When new users are identified, Engage assumes their signup date to be the current timestamp. You can change this by adding a created_at attribute.

HashMap<String, Object> attributes = new HashMap<String, Object>();
attributes.put("first_name", "Adeyinka");
attributes.put("last_login", new Date());
attributes.put("created_at", "2021-01-04");
Engage.identify(userId, attributes);

To add more attributes to the user's profile, use the addAttributes method.

HashMap<String, Object> attributes = new HashMap<String, Object>();
attributes.put("plan", "Pro");
attributes.put("age", 14);
Engage.addAttributes(userId, attributes);

Engage integrates with FCM to let you send push notifications to your users, either through broadcast or automation. However, to do this, you need to send the user's FCM registration token to Engage. The device registration token is a unique identifier that allows the device receive messages.

@Override
public void onTokenRefresh() {
  String token = FirebaseInstanceId.getInstance().getToken();
  Engage.setDeviceToken(userId, token)
}

Track an event:

Engage.trackEvents(userId, "Login");

Track an event with a value:

Engage.trackEvents(userId, "Clicked", "Login button");

Track an event with properties:

HashMap<String, Object> properties = new HashMap<String, Object>();
properties.put("type", "button");
properties.put("counter", counter);
Engage.trackEvents(userId, "Clicked", properties);

Engage sets the event date to the current timestamp but if you would like to set a different date, you can add a date as the last argument of the trackEvents method.

Date lastWk = new Date(System.currentTimeMillis() - 7 * 24 * 60 * 60 * 1000);
Engage.trackEvents(userId, "Clicked", "Login button", lastWk);