Pushwoosh provides several ways to track notification engagement and subsequent user behavior:
-
Notification Opens and Deliveries:
- The Pushwoosh SDK automatically tracks when a notification is opened by a user.
- It also tracks delivery events (when the message reaches the device). This works out-of-the-box on Android, while iOS requires additional integration steps.
- This data is available in your Pushwoosh dashboard and via the Message Statistics API for raw data access.
-
Differentiating App Launch Sources:
- By default, an "app open" event is triggered whenever the app is opened.
- To distinguish between app launches initiated by a push notification tap versus organic (direct) app launches, you can implement Custom Events.
-
Session Attribution:
- "Push open" events (when a user taps a notification) and "app open" events (when the app is launched) are logged as distinct events, allowing for separate analysis.
-
User Journey and Post-Notification Behavior:
- You can track detailed user actions within your app after a notification interaction by using Custom Events. These events can include attributes to capture specific details about user engagement.
- If you use Customer Journey, you can define Conversion Goals to track journey performance based on user actions.
-
Addressing Common Tracking Concerns:
- Incomplete tracking of opens: The SDK is designed for robust and reliable capture of push open events.
- Delayed notification responses: Pushwoosh updates statistics in real-time, so delayed opens are accurately logged.
For more detailed information and implementation guides, please refer to the Pushwoosh Product Documentation.
Comments
0 comments
Please sign in to leave a comment.