H.3 Log Events

Log Events

Events provide insight on what is happening in your app, such as user actions, system events, or errors.

Analytics automatically logs some events for you; you don't need to add any code to receive them. If your app needs to collect additional data, you can log up to 500 different Analytics Event types in your app. There is no limit on the total volume of events your app logs. Note that event names are case-sensitive and that logging two events whose names differ only in case will result in two distinct events.

After you have initialized the FirebaseAnalytics, you can use it to log events with the logEvent() method.

To help you get started, the Analytics SDK defines a number of suggested events that are common among different types of apps, including retail and ecommerce, travel, and gaming apps. To learn more about these events and when to use them, browse the Events and properties articles in the Firebase Help Center.

Note: To get the maximum detail in reports, log the suggested events that make sense for your app and their prescribed parameters. This also ensures that you benefit from the latest Firebase Analytics features as they become available.

You can find implementation details for suggested event types in the following locations:

• Suggested events: see the AnalyticsEvent class reference.
• Prescribed parameters: see the AnalyticsParam class reference.

The following example demonstrates how to log a suggested SELECT_CONTENT Event:

var bundle:AnalyticsParam = new AnalyticsParam();
bundle.addString(AnalyticsParam.ITEM_ID, "yourContentId");
bundle.addString(AnalyticsParam.ITEM_NAME, "yourContentName");
bundle.addString(AnalyticsParam.CONTENT_TYPE, "image");

FirebaseAnalytics.logEvent(AnalyticsEvent.SELECT_CONTENT, bundle);

In addition to the prescribed parameters, you can add the following parameters to any event:

• Custom parameters: Custom parameters are not represented directly in your Analytics reports, but they can be used as filters in audience definitions that can be applied to every report. Custom parameters are also included in data exported to BigQuery if your app is linked to a BigQuery project.

• VALUE parameter: VALUE is a general purpose parameter that is useful for accumulating a key metric that pertains to an event. Examples include revenue, distance, time, and points.

If your application has specific needs not covered by a suggested event type, you can log your own custom events.

Confirm Events

On Android you can enable verbose logging to monitor logging of events by the SDK to help verify that events are being logged properly. This includes both automatically and manually logged events.

You can enable verbose logging with a series of adb commands:

adb shell setprop log.tag.FA VERBOSE
adb shell setprop log.tag.FA-SVC VERBOSE
adb logcat -v time -s FA FA-SVC

This command displays your events in the Android Studio logcat, helping you immediately verify that events are being sent.