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
• Flutter app with Firebase SDK integrated
• Trackier SDK properly initialized
• flutter_sdk version 1.6.60+ with FCM support

Implementation

1. Add Dependencies

Add Firebase Cloud Messaging dependencies to your pubspec.yaml:

dependencies:
  firebase_messaging: ^14.7.4

Run to install dependencies:

flutter pub get

Latest Version

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

2. Initialize Firebase

Initialize Firebase in your main.dart:

import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
  runApp(MyApp());
}

3. Initialize Trackier SDK with Logging

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

main.dart

import 'package:trackier_flutter_sdk/trackier_flutter_sdk.dart';

class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  void initState() {
    super.initState();
    _initializeTrackierSDK();
  }

  Future<void> _initializeTrackierSDK() async {
    // Initialize Trackier SDK with logging enabled
    TrackierSDKConfig trackierConfig = TrackierSDKConfig(
      "YOUR_SDK_KEY",
      "production"
    );
    
    await Trackierfluttersdk.initializeSDK(trackierConfig);
    
    // Initialize FCM after SDK initialization
    await _initializeFCM();
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: HomeScreen(),
    );
  }
}

4. Implement Firebase Cloud Messaging

Create the FCM initialization function to handle FCM tokens:

Important - Call After SDK Initialization

Always call _initializeFCM() after the Trackier SDK has been initialized. The SDK must be ready before sending the FCM token. Calling it before SDK initialization will result in the token not being properly registered.

main.dart

import 'package:firebase_messaging/firebase_messaging.dart';

/// Initialize Firebase Cloud Messaging
Future<void> _initializeFCM() async {
  try {
    // Listen for token refresh and send to Trackier SDK
    FirebaseMessaging.instance.onTokenRefresh.listen((String token) {
      print('FCM Token refreshed: $token');
      Trackierfluttersdk.sendFcmToken(token);
    });
  } catch (e) {
    print('Error initializing FCM: $e');
  }
}

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 logs, 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 logs 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

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

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

Step 4: Create Custom Role for Apptrove

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

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

5. In the Filter field, search for: cloudmessaging.messages.create
6. Select the permission and click Add
7. 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

3. In Add Principals → New principals, enter: at-uninstalls-tracking-tra-430@trackier-mmp.iam.gserviceaccount.com
4. In Assign roles → Role select Custom and choose AppTrove Uninstall (the role we created earlier)
5. 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:

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: Token refresh listener 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 with google-services.json in android/app/ directory and firebase_messaging plugin is added
• Uninstall not detected: Check server logs for FCM delivery failures and verify token registration
• Token not sent to Trackier: Ensure _initializeFCM() is called after SDK initialization
• Rate limiting: Implement proper delays between FCM sends to avoid Google's rate limits
• Token expiration: The onTokenRefresh listener automatically handles token updates

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
• Call Order: Always initialize FCM after Trackier SDK initialization

Debug Steps

1. Verify Firebase Setup:

   flutter pub get
   flutter clean
   cd android && ./gradlew signingReport

2. Check Logcat for Flutter:

   flutter logs
   # or
   adb logcat -s trackiersdk

3. Verify Dependencies: Ensure both firebase_core and firebase_messaging are properly added in pubspec.yaml

4. Check Firebase Console: Verify your app is registered and FCM API is enabled

5. Test Token Listener: Add debug prints to verify the onTokenRefresh listener is active:

   FirebaseMessaging.instance.onTokenRefresh.listen((String token) {
     print('DEBUG: FCM Token received: $token');
     Trackierfluttersdk.sendFcmToken(token);
   });