Oomph supports standard high level analytics - app users (new and active), downloads, user interaction metrics, user location (when available), ad tracking and engagement, most read stories, session times and session usage. In addition, every interaction with both the application and its content is tracked. These include: issue downloads and purchasing, help usage, content interaction, article and ad reads (including time spent), reads, widget interaction (e.g. slideshow usage, flipbook taps etc).
A full list of events logged is available here.
If you already have an analytics account for your other properties, Oomph supports the following iOS analytics providers:
These can be used independently or in conjunction with one another (though this isn't recommended).
Oomph supports tracking downloads in two ways:
- Via iOS analytics
- Via Publish
Oomph tracks a number of events related to downloads including the type (e.g. Newsstand, subscription, single issue, etc.), as well as conditions around retires & errors. For tracking completed downloads, there is a single event called "Content Download", this tracks the successful completion of a download on a device.
- Tracks only successful downloads, not retries, etc.
- Downloads are tracked from a device, not from the API/backend.
- Does not include data from offline devices, downloads will only be available when a device comes online.
- Does not take into account purchases/downloads that have started but may not have fully completed for legitimate reasons, e.g. lack of network access.
- Some analytics providers (e.g. Flurry) do not allow this data to be "unrolled" and made unique without downloading the raw events & analysing them yourself.
Publish includes analytics screens which show you the number of downloads that an issue has had. A download is considered to be made when a client requests a URL to an app's content, i.e. it tracks the start of a download not the completion.
- Downloads numbers are available immediately, there is no need to wait for data to be uploaded to a server, devices to come online, etc.
- Downloads are unique & do not need further analysis to determine a unique number.
- Tracks download start, rather than completion, so could include devices that do not complete a download (e.g. loose network access).
- The total count (not the unique value) includes legitimate retries, resumptions, etc. that may occur because of user multitasking.