- Why Smartech
As marketeers, your push notification campaign might fail to show results even if you get the messaging and the timing right, simply because your push notifications have failed to deliver. It hurts your campaign success and reduces your marketing ROI.
• Unreliable FCM & APNS gateways
No guarantee of push notification delivery
• Chinese OEMs that are known to be notorious for blocking these messages
They restrict background processes which leads to lower delivery rates
As a result, your average push notification delivery rate may hover around 60-65%, resulting in poor customer engagement and therefore, lower user retention rates.
You can solve this issue by getting Smartech Push Amplification. It can help you boost your delivery rates up to 20%.
Push amplification is technology used to improve/maximise deliverability of Push notifications on the end-user's smartphone. It has been observed that certain OEMs restrict background processes related to certain apps so as to conserve battery life and processor bandwidth. As a result, push notification delivery is greatly hampered or are not delivered at all since the vital link between the push gateway (either GCM or FCM) and the smartphone device is severed. Push Amplification helps solve this problem.
After seamless integration, every elaborate push notification campaign that you run for your app is pushed to your selected audiences from Smartech's servers through either the GCM/FCM & APNS delivery gateways. Assuming you sent out a campaign to 100 tokens, and 60 of them got delivered. The remaining 40 undelivered tokens are stored on Smartech and to these tokens we deliver notifications via our pull-based gateway which directly delivers the notification to the user's smartphone.
As soon as the notification is rendered on the screen of the user's smartphone, the Smartech SDK detects it as delivered, and sends status to Smartech.
This gets handled at the platform level where Smartech will ensure one user receives a particular notification only once.
No, since you have an option to select an expiry time for a particular campaign. That is "TTL - Time To Live" which allows you to set a time limit for a campaign.
Android and iOS both Operating Systems will end up consuming less than 1% of battery life since the pull-based mechanism is needed only at certain time intervals. We have tested this on all major devices and have found that it does not impact more than 1% battery life.
Android: Notifications will get delivered even if the app is not running in the background.
iOS: Notifications will be delivered only when the user launches the app or starts a session.
Our SDK pulls the Notifications stored on the server and directly delivers it to the device of the user.
Android OS: Netcore's Smartech Push Amplification feature will eventually help you boost campaign delivery rates and CTRs by almost 20-25%.
If the app is 'Force Closed' from the 'App Settings', push notification delivery will be stopped as the OS itself kills all the foreground as well as background processes.
Push notifications will not be delivered if the user has disallowed for app notifications from the particular brand.
In case the user restarts the device and all the processes for each and every app get killed, delivery will get cancelled, until the user once again launches the brand's app again. (Holds true for Chinese OEMs)
If the phone is on battery saver mode, the notification will not be delivered.
Simply re-integrate with the upgraded push amp supporting SDK (1.1.2), and toggle it on from the panel.
Integrate the SDK (1.1.2). Github link of our SDK - https://github.com/NetcoreSolutions
Yes, if it's a Native app our SDK can easily coexist and you can send notifications from the same FCM account via 2 partners.
We have seen a 2X increase in the CTR's from Notifications for a leading fashion brand. For a Leading travel brand we have seen a 1.8X increase in the Delivery rates post implementation of Push Amplification.
Original Equipment Manufacturer