EXP Events
EXP Events provide detailed tracking and insights into user interactions within the nwExp environment from Nw SDK. By leveraging these events, developers can gain valuable analytics and enhance their application’s functionality.
These events cover a range of actions, including playback controls, camera and audio switches, synchronization processes, and menu interactions. With this data, developers can:
- Monitor User Behavior: Track which features users interact with most frequently, such as specific cameras or audio options.
- Analyze Event Outcomes: Assess the success or failure of actions like camera switches or seeks to fine-tune the application's performance and reliability.
- Integrate with Analytics Tools: Feed this event data into analytics platforms to generate reports, identify trends, and make data-driven decisions.
These events are part of our experimental features and are subject to change. The naming conventions and functionalities may be updated in future releases.
This comprehensive event tracking allows for a deeper understanding of user engagement, enabling improvements and customization based on real usage patterns.
Android: Intigrate Exp Events
iOS: Intigrate Exp Events
Web: TBA
Description: This event signals that the nwExp is ready to watch. It includes information about available cameras and global audio options.
JSON Example:
Payload Explanation:
- cameras: A list of available cameras.
- id: The unique identifier for the camera.
- name: The display name of the camera. It can be null.
- global_audios: A list of available global audio options. It can be null if there is no global audio in the manifest.
- id: The unique identifier for the global audio.
- name: The display name of the global audio. It can be null.
Description: This event is triggered when the visibility of an overlay changes.
JSON Example:
Payload Explanation:
- value: A boolean indicating whether the overlay is visible (true) or not (false).
Description: These events relate to synchronization processes in the application, indicating a request for sync, a failed sync attempt, or a successful sync.
JSON Example:
Payload Explanation:
These events do not require any additional details in the payload, and it can be an empty object.
Description: These events are triggered by playback controls such as play, pause, and replay.
JSON Example:
Payload Explanation:
Similar to the sync events, these playback events do not require any additional details in the payload, and it can be an empty object.
Description: These events are triggered when a camera is switched, and they indicate whether the switch was successful or failed.
JSON Example:
Payload Explanation:
selected_id: The ID of the camera that was selected.
Description: These events are triggered when an audio (global audio) source is switched, and they indicate whether the switch was successful or failed.
JSON Example:
Payload Explanation:
selected_id: The ID of the audio source that was selected.
Description: These events are triggered when a seek action is performed on the playback display timeline, and they indicate whether the seek was successful or failed.
JSON Example:
Payload Explanation:
position: The position on the playback timeline (in seconds or timestamp) to which the user has sought.
Description: These events are triggered when a jump action is performed in the media playback (e.g., skipping forward or backward), and they indicate whether the jump was successful or failed.
JSON Example:
Payload Explanation:
value: The number of seconds to jump forward (positive value) or backward (negative value).
Description: This event is triggered when an item from the menu is selected.
JSON Example for Main Menu:
JSON Example for Sub Menu:
Payload Explanation:
selected_id: The ID of the selected menu item.
name: The name of the selected menu item.
parent: Indicates whether the main menu of that sub-menu. If it’s the main menu, parent will be null.
Description: This event is triggered when a specific moment (play-by-play or Match Events), such as a highlight or key event, is selected.
JSON Example:
Payload Explanation:
position: The position on the playback timeline (in seconds or timestamp) to which the user has sought.
name: The name of the selected moment.
Description: This event signals that the user has exited the nwExp.
JSON Example:
Payload Explanation:
This event does not require any additional details in the payload, and it can be an empty object.