![]() ![]() Without delay as well as how many messages were delayed or dropped within theĮvaluating this data can reveal broad trends in message delivery and help youįind effective ways to improve the performance of your send requests. The API provides aggregated data across all dataĬollection-enabled Android devices in a project. Help you understand the outcomes of message requests targeted to AndroidĪpplications. The Firebase Cloud Messaging Data API lets you retrieve information that can Aggregated delivery data via the FCM Data API List of all existing labels and apply them singly or in combination to filter In the Firebase console messaging Reports tab, you can search a Messages with labels added beyond that limit are not reported. You can specify up to 100 unique labels per day Labels can include lower and upper case letters, Is required to display all types of statistics for data messages.Īnalytics labels are text strings in the format ^$. Important: To use this feature, you must include the Analytics SDK Platform-specific AndroidFcmOptions or ApnsFcmOptions fields. The fcmOptions.analyticsLabel field in the Label to any message sent via the HTTP v1 API by setting Labeling messages is very useful for custom analysis, allowing you toįilter delivery statistics by labels or sets of labels. When viewing message reports, you can set a date range for the data displayed, This data is available for all messages with a notification payload Notifications received when the app is in the background. Opens - The user opened the notification message.The display notification has been displayed on the device while the app is Impressions (available only for notification messages on Android devices).When the receiving Android device has FCM SDK 18.0.1 or Notification message has been received by the app. Received (available only on Android devices) - The data message or.Sends - The data message or notification message has been enqueued forĭelivery or has been successfully passed to a third-party service like APNs.Including those sent via the Notifications composer and the FCM APIs: ![]() Tab in the Firebase console, you can view theįollowing data for messages sent to Android or Apple platform FCM SDKs, ![]() Keep in mind that the reporting of many of the statistics on this page,Īre subject to delays up to 24 hours due to batching of analytics data. If Google Analytics is not enabled for your project, The reporting tools described in this page all require Google Analytics If your goal is to troubleshoot ongoing message delivery failures, see Note: the tools in this page are for broad evaluation of messaging success and Comprehensive data export to Google BigQuery. ![]() Aggregated Android SDK delivery metrics from the.Firebase console message delivery reports.JqXHR.done(), jqXHR.fail(), and jqXHR.always() instead.FCM provides three sets of tools to help you get insight into message delivery: then() for implementation details.ĭeprecation Notice: The jqXHR.success(), jqXHR.error(), and plete() callbacks are removed as of jQuery 3.0. fail() methods, allowing (as of jQuery 1.8) the underlying Promise to be manipulated. However, since the implementation of $.Deferreds and more sophisticated callbacks, done is the preferred way to implement success callbacks, as it can be called on any deferred.įor example, done: $.ajax() Success has been the traditional name of the success callback in jQuery, defined as an option in the ajax call. ![]()
0 Comments
Leave a Reply. |