Package-level declarations
Different types of events that can be tracked with Snowplow.
Types
Base AbstractEvent class which contains common elements that can be added to all events:
Abstract class which contains common elements to all "primitive" events, i.e. events that are not based on a schema, such as Structured events.
Abstract class which contains common elements to all self-describing events, i.e. events that are based on a schema. Examples include SelfDescribing, ScreenView, and Foreground events.
A background transition event.
A consent document event.
A consent granted event.
A consent withdrawn event.
A deep-link received in the app.
An ecommerce event.
An ecommerce item event.
A foreground transition event.
Event tracking the view of an item in a list. If screen engagement tracking is enabled, the list item view events will be aggregated into a screen_summary
entity and won't be sent as separate events to the collector.
Event that represents the reception of a push notification (or a locally generated one).
Trigger that caused the message notification.
A PageView event. This event has been designed for web trackers, and is not suitable for mobile apps.
A ScreenView event.
Event tracked when a scroll view's scroll position changes. If screen engagement tracking is enabled, the scroll changed events will be aggregated into a screen_summary
entity and won't be sent as separate events to the collector.
A SelfDescribing event.
A Structured event.
An error event representing an exception, error or warning message in the app.