Oracle Push Cloud Service is the only provider that goes beyond telling you if your users are opening your app via push notifications.
With engagement metrics, you can connect the dots between a notification and actual user behavior. Do you want to see if a push notification is trying social activity? What about premium content or in-app purchases? By understanding your push conversion, you can improve your messaging strategy and even re-target users based on user behavior.
Launch and Active Engagements are handled automatically with use of the
PushIOActivityLauncher. If your app is handling the notification in a custom way, then it needs to respond to the broadcasts, as described in the Optional - Customize Incoming Push Messages and Notification Taps section of the Step-by-step Guide topic. Otherwise, Oracle Push Cloud Service creates a duplicate notification.
If you decide to not use
PushIOActivityLauncher for your custom notification's
PendingIntent items, you must report the engagements, for example:
If you want to track other metrics like In-App Purchases, Premium Content (Video Views), Social Media Hits, or other generic activities, you must call
trackEngagement, passing one of the
PUSHIO_ENGAGEMENT_METRIC constants found in the
PushIOManager, as follows:
PushIOManager pushIOManager = PushIOManager.getInstance(); pushIOManager.trackEngagement(PushIOManager.PUSHIO_ENGAGEMENT_METRIC_PREMIUM_CONTENT);
Here's a list of the
PUSHIO_ENGAGEMENT_METRIC constants handled by the
IMPORTANT: You must clear the
EngagementId when the app goes into the background due to any user action (such as the user closing the app) or any system action (such as a phone call). To clear the
EngagementId, call it once in the
onStop method of your app:
PushIOManager pushIOManager = PushIOManager.getInstance(this); pushIOManager.resetEID();