Wiki source code of Учёт доступности push-уведомлений для клиента в Loymax Smart Communications
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="lead" %)Push notifications are delivered to customers via specialized push services. | ||
| 2 | |||
| 3 | Loymax Smart Communications allows for sending push notifications through the [[Google Firebase Cloud Messaging Service>>https://firebase.google.com/]]. | ||
| 4 | |||
| 5 | Due to various reasons, including customer actions, the status of a mobile device identifier, push token, and push notification availability may change. | ||
| 6 | |||
| 7 | On the side of Loymax Smart Communications, an active push token is determined as follows: | ||
| 8 | |||
| 9 | When sending a mailing to multiple push tokens, Smart Communications analyzes the response received from the **FCM service**. If an [[error>>https://firebase.google.com/docs/cloud-messaging/send-message?hl=en#rest-error]] is received, the push token is marked as invalid in the Smart Communications database if the ##status## or ##errorCode## parameter has one of the following values: | ||
| 10 | |||
| 11 | * ##INVALID_ARGUMENT## | ||
| 12 | * ##UNREGISTERED## | ||
| 13 | |||
| 14 | **Examples of responses from the FCM service**: | ||
| 15 | |||
| 16 | * HTTP error code = 400: | ||
| 17 | |||
| 18 | (% class="box" %) | ||
| 19 | ((( | ||
| 20 | ## "error": { | ||
| 21 | "code": 400, | ||
| 22 | "message": "The registration token is not a valid FCM registration token", | ||
| 23 | "status": "INVALID_ARGUMENT", | ||
| 24 | "details": [ | ||
| 25 | { | ||
| 26 | "@type": "type.googleapis.com/google.firebase.fcm.v1.FcmError", | ||
| 27 | "errorCode": "INVALID_ARGUMENT" | ||
| 28 | } | ||
| 29 | ] | ||
| 30 | }## | ||
| 31 | ))) | ||
| 32 | |||
| 33 | * HTTP error code = 404: | ||
| 34 | |||
| 35 | (% class="box" %) | ||
| 36 | ((( | ||
| 37 | ## "error": { | ||
| 38 | "code": 404, | ||
| 39 | "message": "Requested entity was not found.", | ||
| 40 | "status": "UNREGISTERED", | ||
| 41 | "details": [ | ||
| 42 | { | ||
| 43 | "@type": "type.googleapis.com/google.firebase.fcm.v1.FcmError", | ||
| 44 | "errorCode": "UNREGISTERED" | ||
| 45 | } | ||
| 46 | ] | ||
| 47 | }## | ||
| 48 | ))) | ||
| 49 | |||
| 50 | (% class="box infomessage" %) | ||
| 51 | ((( | ||
| 52 | The FCM service does not provide a detailed explanation of why a token became invalid. Therefore, it is not possible to determine the exact reason for such a response in each individual case. | ||
| 53 | ))) | ||
| 54 | |||
| 55 | === Selecting customer devices for messaging === | ||
| 56 | |||
| 57 | |(% style="border-color:white; width:912px" %)In the Loymax Smart Communications interface, you can configure whether to send messages to all existing push tokens associated with a customer or only to the token most recently added to the database. Other devices will be ignored in the latter case. By default, the setting is **To all devices**. For more information on push messaging settings, please refer the [[article>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="04"]].|(% style="border-color:white; width:531px" %)[[image:Push_setting.png]] | ||
| 58 | |||
| 59 | (% class="box" %) | ||
| 60 | ((( | ||
| 61 | **Note:** | ||
| 62 | Loymax Smart Communications does not perform delivery confirmation for push notifications. | ||
| 63 | ))) | ||
| 64 | |||
| 65 | (% class="box" %) | ||
| 66 | ((( | ||
| 67 | **Read also:** | ||
| 68 | |||
| 69 | * [[General settings in Smart Communications>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome]] | ||
| 70 | * [[Push tokens>>doc:Main.Using.Mobile_application.Push_token.WebHome]] in the Loymax system | ||
| 71 | * [[Tracking push notification availability for customers in Loymax Loyalty>>doc:Main.Using.Mobile_application.Typical_processes.mobile_app_installation.Push_availability.WebHome]] | ||
| 72 | ))) |