Steps to obtain Server Key of FCM

d) Click on the “gear” icon on top left and access “project settings”.

e) Go to the “Cloud Messaging Section” and you will have access to the sender ID and the Server Key.

f) In your Singular account, navigate to Apps > Edit for the application for which you want to track uninstalls. Under the Uninstall Tracking section, add the Project Number (Sender ID on Firebase) and Server Key.

Steps to configure FCM in your App

1. Create a Firebase project on the Firebase Console.

2. After creating the project, It will take you on dashboard from where select the option “Add firebase to your Android App”.

buildscript {dependencies {// Add this line or latest version classpath 'com.google.gms:google-services:3.1.0'}}

7. In App-level build.gradle (<project>/<app-module>/build.gradle)

// Add to the bottom of the fileapply plugin: 'com.google.gms.google-services'

8. sync the project

9. create a service in android code (class which will inherit FirebaseInstanceIdService)

public class FCMService extends FirebaseInstanceIdService {

@Override

public void onTokenRefresh() {

super.onTokenRefresh();

//now we will have the token

String token = FirebaseInstanceId.getInstance().getToken();

}

}

In onTokenRefresh method we will get fcm token that we have to store on our server to send Notifications

10. Add this service to Android Manifest file

<service

android:name=".FCMService">

<intent-filter>

<action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>

</intent-filter>

</service>

11. You can test the notification using console by providing FCM token

Singular will now begin to track uninstalls for users using the updated version of your application.

How does it work

Singular has integrated with Google's services to track uninstalls for your applications, as a proxy measure for the quality of traffic you drive through your paid campaigns. This integration uses a different methodology compared to Google - who reports uninstalls directly from the operating system resident on the device.

A few important points to keep in mind:

Singular and Google use different methodologies to report uninstalls, which results in a variation in numbers. Use the Singular and Google reports separately for their respective purposes.

Uninstalls are tracked as events in Singular and as a result do not remove the attribution link from the originating Install or Re-engagement source. This may result in uninstall rates of higher than 100%, since a user may uninstall an app multiple times in their lifetime.