Skip to main content

Uninstall Tracking through Firebase Cloud Messaging

Firebase Cloud Messaging (FCM) uninstall tracking detects app uninstalls by monitoring FCM delivery receipts. This method is ideal for apps that already use push notifications.

How FCM Uninstall Tracking Works​

  • Purpose: Tracks app uninstalls using FCM delivery receipts to assess user engagement and campaign performance
  • Mechanism: Uses FCM to send silent push notifications and monitors delivery receipts for failed deliveries
  • Detection: Uninstall data typically appears in the panel within 24-48 hours
  • Use Case: Measure uninstall rates for campaigns to refine targeting and improve user retention
Alternative Method

For Firebase Analytics-based uninstall tracking, see Through Firebase Analytics.

Prerequisites​

Before implementing FCM uninstall tracking, ensure you have:

  • Firebase project with Cloud Messaging enabled
  • Android app with Firebase SDK integrated
  • Trackier SDK properly initialized
  • Server infrastructure to handle FCM token management

Implementation​

1. Add Dependencies​

Add Firebase Cloud Messaging dependency to your app/build.gradle:

dependencies {
    implementation 'com.google.firebase:firebase-messaging'
    implementation 'com.trackier:android-sdk:1.6.77'
}
Latest Version

Check the Firebase Cloud Messaging SDK for the latest version and setup instructions.

2. Configure AndroidManifest.xml​

Add the Firebase Cloud Messaging service to your AndroidManifest.xml:

<!-- Firebase Cloud Messaging Service -->
<service
    android:name=".MyFirebaseMessagingService"
    android:exported="false">
    <intent-filter>
        <action android:name="com.google.firebase.MESSAGING_EVENT" />
    </intent-filter>
</service>

3. Initialize Trackier SDK with Logging​

Configure the Trackier SDK with logging enabled to see FCM token responses:

// In your Application class or MainActivity
import com.trackier.sdk.TrackierSDK
import com.trackier.sdk.config.TrackierSDKConfig
import java.util.logging.Level

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        
        // Initialize Trackier SDK with logging enabled
        val sdkConfig = TrackierSDKConfig(this, "YOUR_SDK_KEY", "production")
        sdkConfig.setLogLevel(Level.ALL)
        TrackierSDK.initialize(sdkConfig)
    }
}

4. Create Firebase Messaging Service​

Create a Firebase Messaging Service to handle FCM tokens:

Important FCM Token Behavior

FCM tokens are generated only once when the app is first installed or when Firebase generates a new token. If you run the app once and don't see the token in logcat, you won't see it again on subsequent runs. To see the token again, you need to:

  1. Uninstall the app completely
  2. Reinstall the app
  3. Check logcat immediately for the token

This is normal FCM behavior - tokens are not generated on every app launch, only when:

  • App is first installed
  • Firebase generates a new token (rare)
  • App data is cleared
  • App is restored on a new device
package com.trackier.workoutflow

import android.util.Log
import com.google.firebase.messaging.FirebaseMessagingService
import com.trackier.sdk.TrackierSDK

class MyFirebaseMessagingService : FirebaseMessagingService() {

    override fun onNewToken(token: String) {
        super.onNewToken(token)
        Log.d("FCM", "New FCM token: $token")
        
        // Send the FCM token to TrackierSDK
        TrackierSDK.sendFcmToken(token)
    }
}

5. Firebase Console Configuration​

Step 1: Connect Product to Firebase​

If you haven't already connected your product to Firebase:

  1. Go to the Firebase Console
  2. Create a new project or select an existing one
  3. Add your Android app to the project
  4. After setting up the project on console, go to Settings
  5. In the General tab, see the Project ID and copy it

Step 2: Configure in AppTrove Panel​

  1. Go to your AppTrove panel
  2. Navigate to Settings page
  3. Go to Uninstall Tracking tab
  4. Paste the Project ID you copied from Firebase Console
  5. Enable the toggle for uninstall tracking

Step 3: Enable Cloud Messaging API​

  1. Go to the Cloud Messaging tab
  2. Check if Firebase Cloud Messaging API (V1) is enabled

If not enabled:

  1. Go to Service accounts tab

  1. Go to Library
  2. Search for Firebase Cloud Messaging API
  3. Click Enable

Step 4: Create Custom Role for Apptrove​

  1. In the side menu, select Roles
  2. Click +Create role

  1. Complete the form as follows:
    • Title: Enter AppTrove Uninstall
    • ID: Enter at_uninstalls
    • Role launch stage: Select General availability
  2. Click Add permissions

  1. In the Filter field, search for: cloudmessaging.messages.create
  2. Select the permission and click Add
  3. Click Create
Verify Role Creation

After creating the role, check and verify that the AppTrove Uninstall role has been added successfully with the cloudmessaging.messages.create permission.

Step 5: Assign AppTrove the FCM Uninstall Role​

  1. In the side menu, select IAM
  2. Click Grant Access

  1. In Add Principals → New principals, enter: at-uninstalls-tracking-tra-430@trackier-mmp.iam.gserviceaccount.com
  2. In Assign roles → Role select Custom and choose AppTrove Uninstall (the role we created earlier)
  3. Click Save
Service Account Email

Use this exact email address: at-uninstalls-tracking-tra-430@trackier-mmp.iam.gserviceaccount.com

Step 6: Verify Permissions​

  1. Go to IAM & Admin → IAM
  2. Search for the service account you just added
  3. Verify that the AppTrove Uninstall role is assigned

Verification and Testing​

1. Test FCM Token Registration​

When your app starts, check the logs to verify the FCM token is being sent to Trackier:

  1. Enable Logging: Make sure you have configured the Trackier SDK with setLogLevel(Level.ALL) as shown in the code above
  2. Filter Logs: In Android Studio Logcat, set the filter to trackiersdk to see only Trackier-related logs
  3. Check Token Response: Look for the log message Fcm token Api response saved successfully

Expected Log Output:

D/trackiersdk: Fcm token Api response saved successfully

2. Test Uninstall Detection​

  1. Install your app and register FCM token
  2. Uninstall the app
  3. Wait 24-48 hours for the uninstall data to be processed
  4. Check AppTrove dashboard for uninstall event

3. Monitor AppTrove Dashboard​

  1. Log in to your AppTrove dashboard
  2. Navigate to uninstall logs
  3. Confirm the uninstall event was received (typically within 24-48 hours)
Uninstall Data Processing Time

Uninstall events are not detected immediately. It typically takes 24-48 hours for uninstall data to appear in the AppTrove panel after an app is uninstalled. This is normal behavior for FCM-based uninstall tracking.

Important Notes​

FCM Token Behavior
  • Token Generation: FCM tokens are generated when the app is first installed or when the token is refreshed
  • Token Refresh: Tokens can change when:
    • App is restored on a new device
    • App data is cleared
    • App is uninstalled and reinstalled
    • Token expires (rare)
  • One-Time Call: onNewToken() is called only when a new token is generated, not on every app launch
Silent Notifications Only

AppTrove uses silent push notifications solely to measure uninstalls or identify inactive users and does not use them for any other purposes. These notifications are invisible to users and don't affect app performance.

Troubleshooting​

Common Issues​

  • FCM token not received: Ensure Firebase is properly configured and google-services.json is in the correct location
  • Uninstall not detected: Check server logs for FCM delivery failures and verify token registration
  • Rate limiting: Implement proper delays between FCM sends to avoid Google's rate limits
  • Token expiration: Handle token refresh in your app and update server records

Best Practices​

  • Silent notifications: Use silent push notifications to avoid user disruption
  • Rate limiting: Implement proper delays to avoid FCM rate limits
  • Token management: Handle FCM token refresh and updates properly
  • Error handling: Implement comprehensive error handling for FCM failures
  • Security: Store FCM tokens securely on your server

Choose the method that best fits your infrastructure and requirements.