Google Analytics helps you measure the app metrics that matter to your business, and helps you strategize your growth. Here's how you can acquire Firebase Analytics for your app!
The Firebase plugin is available from Growth plan onwards.
Step 1: Head over to the Plugins section of the Vajro admin dashboard, and click on View Collection
Step 2: Look for Firebase Analytics under the Analytics category and click on it
Step 3: Click on Enable Now in the dialog box that appears on your screen
Once the Firebase analytics is enabled for the app, both android and iOS app will be rolled out and once it is live the analytics will be enabled.
Features that are supported by Vajro :
System events AKA Automatically collected events like, android app removal, app update and first time app open and first purchase are tracked by Vajro.
Supported events like, add to cart, wishlist and shipping info, Apple Pay, payment info, decrease and cart increase quantity are tracked by Vajro.
These events data can be viewed on Firebase dashboard.
Limitations in Firebase dashboard:
All the standard events that are listed on this page (check online sales section) of Firebase documentation can accept the ITEMS array so for example, if you are not considering then do consider passing data for ITEMS for events like remove_from_cart or view_cart, etc.
As much as possible, please use the standard event_parameters as well, these have special purpose and use cases built into Firebase such as predictive models which don’t work when you use custom parameters. For example with view_item_list you have mentioned passing “title” but instead consider using “item_list_name”
It would make sense to just trigger ‘login’ event when user logs in and you can pass method as parameter (SMS, email, etc) but triggering an additional event “OTP_LOGIN” is not best practice
It would make sense to trigger an event like “payment_method_changed” in which you can pass the parameters such as method_to and method_from instead of triggering “apple_pay” as a separate event. It will capture a wider use case.
Instead of cart_increase_quantity or cart_decrease_quantity you can probably consider consolidate these two events into one like ‘cart_quantity_updated’ and you can pass a parameter like ‘qty_update_action’ and pass ‘increase’ or ‘decrease’. This way the reporting become more actionable when this data is taken outside Firebase such as to platforms like Google Data Studio.