You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ The official Push Notification adapter for Parse Server. See [Parse Server Push
25
25
-[Migration to FCM HTTP v1 API (June 2024)](#migration-to-fcm-http-v1-api-june-2024)
26
26
-[HTTP/1.1 Legacy Option](#http11-legacy-option)
27
27
-[Firebase Client Error](#firebase-client-error)
28
+
-[FCM Analytics Label](#fcm-analytics-label)
28
29
-[Expo Push Options](#expo-push-options)
29
30
-[Bundled with Parse Server](#bundled-with-parse-server)
30
31
-[Logging](#logging)
@@ -189,6 +190,22 @@ Occasionally, errors within the Firebase Cloud Messaging (FCM) client may not be
189
190
190
191
In both cases, detailed error logs are recorded in the Parse Server logs for debugging purposes.
191
192
193
+
#### FCM Analytics Label
194
+
195
+
To tag Firebase delivery metrics for a push notification, include `analytics_label` in the push data. The adapter validates the label and maps it to `fcmOptions.analyticsLabel` in the FCM payload.
196
+
197
+
```js
198
+
awaitParse.Push.send({
199
+
channels: ['global'],
200
+
data: {
201
+
alert:'Feature update',
202
+
analytics_label:'feature_update_v1'
203
+
}
204
+
}, { useMasterKey:true });
205
+
```
206
+
207
+
The analytics label can contain 1 to 50 letters, numbers, or `-_.~%` characters.
0 commit comments