Frequently Asked Questions
How can I troubleshoot abnormal iOS delivery statistics?
If the delivery rate is abnormally low (below 20%) and the click-through rate is greater than 100%, first check whether the app has integrated the Notification Service Extension feature. If it has not been integrated, you need to integrate this feature first to improve the delivery rate.
For details, see: iOS SDK Integration Guide
Why is the FCM delivery rate reported by EngageLab inconsistent with the delivery rate shown in the FCM console?
- Deep-sleeping apps and apps stopped by the system will definitely cause FCM messages to fail to be delivered.
- If the app process is killed by swiping up in the task manager, FCM messages can still be delivered, but this will prevent the MTPush SDK from monitoring delivery.
- Whether the app is in the foreground or background, as long as the process exists, the MTPush SDK can monitor delivery.
- FCM does not provide a delivery receipt service, so the MTPush SDK cannot accurately monitor the delivery rate.
Therefore, in the absence of FCM callbacks, the FCM channel delivery statistics counted by EngageLab are actually based on the number of messages successfully sent to the FCM server, while the number displayed by FCM is closer to the number of messages delivered to end devices as counted by FCM. In summary, the FCM delivery rate counted by EngageLab is, in most cases, higher than the delivery rate shown in the FCM console.
If, due to certain restrictions, the app cannot be listed on app stores in mainland China, but some target users are located within mainland China, how should channel settings be configured to reach these users? Are there any precautions to note?
Please read Push Instructions for Overseas Mobile Manufacturer Channels to check the reachability of users in China and overseas for each mobile manufacturer channel.
