Sessions & Active Devices

Downloads are a start.
Usage tells the story.

See how many devices actually use your app, how often they return and how long sessions last. Understand the audience behind every release, without advertising identifiers.

iOS, tvOS & Android · PRO & ENTERPRISE · Hosted in Switzerland

A clearer picture of your active audience

A spike in sessions can mean more devices, more frequent visits, or both. Know which story your numbers are telling.

DAU · WAU · MAU

Separate reach from repeat visits

Track distinct active devices over a day, a trailing week and a trailing month. One device opening the app ten times is not ten new devices.

DAU / MAU

See whether usage becomes a habit

Stickiness shows the share of your monthly active devices that are active on a given day. Follow the trend, not just a growing download count.

App & OS adoption

Know what is actually being used

See which app and OS versions account for reported sessions. Compare device models and languages to put release and support decisions in context.

For release adoption plus a confidence-based crash-health verdict, explore release rollout health.

Measure time in the app, not in the background

An average can hide a lot of brief visits. See the spread of session lengths before deciding what changed.

  • Foreground time only. Background launches and background time do not inflate session-duration metrics.
  • Go beyond the average. Compare median and P10–P90 trends, a duration histogram and clear duration ranges.
  • Find the affected audience. Filter by app version, OS, device model or language to see where session patterns differ.

Usage tells you what changed. Crash reporting and non-fatal errors help you investigate whether failures are part of the story. To time a specific operation rather than a whole session, explore performance traces.

Useful analytics. Deliberate collection.

Enable session monitoring in the SDK you already use. No custom event taxonomy to design before you can understand basic app usage.

Swift · iOS & tvOS
AppeliumFeedback.start(
    apiKey: "YOUR_API_KEY",
    sessionMonitoring: .enabled
)
Kotlin · Android
AppeliumFeedback.start(
    apiKey = "YOUR_API_KEY",
    application = this,
    sessionMonitoring =
        SessionMonitoringConfiguration.Enabled()
)
Off by default. No advertising identifiers.

Devices are counted using a randomly generated SDK identifier. Your data is hosted and processed in Zürich, Switzerland. You choose which features to enable.

Integration guides: iOS, tvOS and Android.

Frequently asked questions

What do DAU, WAU and MAU mean in Appelium?

They count distinct active devices, not logged-in users. DAU covers a UTC day; WAU and MAU cover trailing windows of 7 and 30 UTC days. A device active on several days is counted once within each window, rather than adding up the daily totals. Counts are approximate distinct-device estimates.

What does stickiness tell me?

Daily stickiness is DAU divided by MAU: the share of the monthly active device base that is active that day. The Dashboard summary averages those daily ratios over the completed days in the selected range. It helps reveal habitual use, but is not a cohort-retention measurement.

Does background time count toward session duration?

No. Session monitoring measures foreground time. Background launches and time spent in the background do not contribute to session-duration metrics. Explore the average, median, P10–P90 trends, a duration histogram and fixed duration ranges to understand the distribution.

How are devices identified, and which plans include this?

The SDK uses a randomly generated, stored device identifier, not an advertising identifier. These are device counts, not a way to identify people or deduplicate one person across devices. Collection is off until you enable it. Sessions and active-device analytics are available on PRO and ENTERPRISE for iOS, tvOS and Android.

Understand the audience behind every release

Active devices, everyday habits and meaningful session trends. In one place.

Trusted by

TWINT

From Our Engineering Articles

XPCService

  • A strongly typed, bidirectional and low-latency channel between the app and XCUITest, with round-trips of about 3 ms.


    More about XPCService

Screen Flow Pattern in UI tests

  • A robust, scalable pattern for structuring UI tests: reusable screen verification, readable test cases, and statically typed flows and interactions.


    More about the Screen Flow Pattern

SnapshotQuery™

  • How SnapshotQuery in AppeliumTests makes XCUITest element queries about 1,000 times faster while making tests more stable.


    More about SnapshotQuery

Early access and news

Be the first one to know about all the exciting engineering posts and product announcements.