Analytics Providers

These can be used independently or in conjunction with one another (though this isn't recommended).

Download Analytics

Oomph supports tracking downloads in two ways:

Via iOS analytics

Via Publish

Each of these methods has its own pros and cons, and bear in mind that they may report slightly different numbers due to different processing methods and times. Note that each of the methods below do not show how the user initiated the download, e.g. via a background Newsstand push, single issue purchase, authenticator-based, etc. In the case of iOS analytics, the source of a download is available via other events in their parameter list.

iOS Analytics

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.

Pros

Tracks only successful downloads, not retries, etc.

Downloads are tracked from a device, not from the API/backend.

Cons

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 Analytics

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.

Pros

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.

Cons

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.