How to move from Google-Analytics to Firebase-Analytics?

Lots of questions bundled together so I'll try to briefly answer most of them:

1. Google Analytics reports on tracker-ids, Firebase Analytics reports on applications. There is only one id in the application defined in your google-services.json. The ID is translated to a string resource by google services plugin under "google_app_id" name. All events from the app are reported to this single id.
2. Firebase Analytics reports AdId automatically. You don't need to enable it.
3. There is no dryRun feature. You can either use separate google-services.json during development, filter out development version using the app version or add user-property to mark the app instances used for development.

4. You can report screens with

   Bundle params = new Bundle();params.putString(FirebaseAnalytics.Param.ITEM_CATEGORY, "screen");params.putString(FirebaseAnalytics.Param.ITEM_NAME, "screen name");firebaseAnalytics.logEvent(FirebaseAnalytics.Event.VIEW_ITEM, params);

5. You can log custom event with the same params

   Bundle params = new Bundle();params.putString("category", category);params.putString("action", action);params.putString("label", label);params.putLong("value", value);firebaseAnalytics.logEvent("xyz_event", params);

   The "ga_" prefix is reserved and your analytics will fail if you use it. Instead, use "xyz_" where xyz is your company's initials, for example.

   Do not use the category as event name unless you have very few categories you want to track. Firebase Analytics supports up to 500 event names. Logging more than that will cause some of your data to be ignored.

6. There is a list of reserved event names in the beginning of the FirebaseAnalytics.Event class. It roughly represents the automatic events reported.

7. Firebase Analytics has debug logging disabled by default. It only logs errors and warnings. If you don't enable debug logging and your app is correctly configured there are only 2 lines that are being logged when the app starts with instructions on how to enable debug logging. There is nothing to disable in production and there is no equivalent to setLogLevel(ERROR) from Google Analytics. WARN is the default logging level. You can only enable logging on individual device by running the adb command on the device). That helps you avoid shipping app in production with debug logging enabled.

8. Google Analytics SDK for Android and iOS is not deprecated and will be supported and updated for foreseeable future. You don't need to move away from it if you already invested using it in your app and it is meeting your needs.

Google Analytics is a freemium web analytics service offered by Google that tracks and reports website traffic.1 Google launched the service in November 2005 after acquiring Urchin.Firebase is a cloud services provider and backend as a service company based in San Francisco, California. The company makes a number of products for software developers building mobile or web applications.

How to move from google analytics to firebase analytics?

Google Analytics (GA) and Firebase Analytics (FA), despite their common name, are widely different in many aspects. While GA is a general-purpose (and more web oriented) analytics tool, Firebase was built keeping mobile in mind: therefore, the feature set is different between the two, with some things that were added in FA and things that are missing from GA.

More specifically, these are some noteworthy points when considering Firebase Analytics:

• Real-time view is missing
• Events are available after a 4-6 hours period
• Behavior Flow (from GA) is missing
• The Audiences feature a big advantage of FA and, coupled with Notifications, allows you to engage with a specific group of users
• When using Firebase Crash Reporting, an audience with users who experienced a crash is automatically created
• Funnel analysis makes much more sense than in GA, since FA is based on events and not on screen views
• Free and unlimited, except for the number of types of events (limited to 500); no limits on the volume of events per each type
• Some events are logged automatically (i.e., sessions based on Activity lifecycle)
• Relatively low methods footprint, compared to GA's methods count
• Dead-easy to setup, there is no singleton to initialize, just include the Gradle dependency and start logging events
• All-in-one console, if you plan on using other Firebase services

As to if one should consider switching from one to the other, or if to keep both in parallel, the answer is: it depends.

• If you were using GA extensively before, chances are that you would be missing some of its feature when switching completely to FA.
• However, if this is a fresh start for your project, FA is much more prone to a cross-platform mobile-oriented environment, so you may very well consider it as your own analytics tool.

On a side note, keep in mind that Firebase has just launched and Google has plans on adding more features in the coming weeks (e.g., real-time dashboard).

For tutorial you can find here https://firebase.google.com/docs/analytics/android/start/