The Airship SDK stores batches of events and will upload them periodically
in the background. We’ve taken great care to ensure that the database
won’t grow beyond a small fixed size, so extended periods of lost connectivity
are nothing to worry about. The event upload thread is woken up when new events
are triggered and goes to sleep when there are no more events to process, so the
impact on battery life is negligible.
Custom events let you track user activities and key conversions in your application,
and tie them back to corresponding push messaging campaigns. Custom events require analytics
to be enabled. If disabled, any event that is added to analytics will be ignored. For a more
detailed explanation on custom events and possible use cases, see the Custom Events
Custom identifiers will be visible in Real-Time Data Streaming. We recommend adding
any IDs that you may want to be visible in your event stream. You can assign up to 20 custom identifiers to
a device. Unlike the other identifiers (e.g., tags), you cannot use custom identifiers to target your users.
The Airship SDK gives you the ability to track which screens a user views within
the application, how long a user stayed on each screen, and also includes the user’s previous screen.
These events then come through Airship Real-Time Data Streaming, allowing you
to see the path that a user took through the application, or trigger actions based
on a user visiting a particular area of the application.