Skip to content

Analytics for apps and games

Know how your app is used. Not who is using it.

Users, sessions, retention and funnels for your app or game. No cookies, no stored IP addresses.

SDKs for iOS, Android, Flutter, Unity, web and .NET.

Orbit Drift

  • Sample data

Users per day3 Nov 2026 to 16 Nov 2026

  • Last 14 days
  • Previous 14 days
  • Today, partial
Show as table
Users per day
DayUsersPrevious period
3 Nov 202616,63416,159
4 Nov 202617,81114,822
5 Nov 202618,25116,598
6 Nov 202617,25818,462
7 Nov 202621,51920,582
8 Nov 202621,52620,220
9 Nov 202618,33116,530
10 Nov 202614,96216,874
11 Nov 202616,33117,126
12 Nov 202616,71715,754
13 Nov 202619,19117,713
14 Nov 202623,39722,349
15 Nov 202619,91122,030
16 Nov 2026 (partial)12,01816,249

What you see

Numbers first, each with its source

Sample data from a demo game, shown with the same charts you get in the app.

Signals by type
SignalSignalsShare
level_start2,046,095
level_complete1,495,223
ad_impression1,337,831
session_start1,101,743
level_fail865,655
tutorial_step629,568

Also in the app

  • Live view of signals as they arrive
  • Retention cohorts and funnels
  • An insight builder that needs no query language
  • The timeline of a single session
  • CSV export on every plan

What it costs

Start free. Pay when you grow.

Every feature is on every plan, including Free. Bigger plans add signals, longer raw history and support priority.

  • Free

    100K signals

    Free

    no card, no time limit

  • Starter

    1M signals

    EUR 6.67

    per month, billed yearly

  • Plus

    2.5M signals

    EUR 15.83

    per month, billed yearly

  • Growth

    5M signals

    EUR 29.17

    per month, billed yearly

  • Pro

    10M signals

    EUR 57.50

    per month, billed yearly

  • Scale

    20M signals

    EUR 99.17

    per month, billed yearly

  • Max

    50M signals

    EUR 182.50

    per month, billed yearly

Plan values as of 16 Nov 2026, 16:32 UTC.

At the monthly limit

  • Collection pauses until the month resets. We tell you when it paused and when it resumes.
  • Your charts, settings and export stay available the whole time.
  • Nothing upgrades by itself and nothing is charged by itself.

Comparing options? See how Pulse compares

Where it runs

Two lines, then the first signal

Six SDKs: Swift, Kotlin, Flutter, Unity, JavaScript and .NET, and plain HTTP for everything else. Every SDK sends signals in batches and keeps a bounded queue while the device is offline.

Swift

import MightySPulse

Pulse.initialize(appKey: "APP_KEY")
Pulse.track("level.complete")

Kotlin

import dev.mightys.pulse.Pulse

Pulse.initialize(this, "APP_KEY")
Pulse.track("level.complete")

Flutter

import 'package:mightys_pulse/mightys_pulse.dart';

await Pulse.initialize('APP_KEY');
Pulse.track('level.complete');

Unity (C#)

using Mightys.Pulse;

Pulse.Initialize("APP_KEY");
Pulse.Track("level.complete");

.NET

using Mightys.Pulse;

Pulse.Initialize("APP_KEY");
Pulse.Track("level.complete");

JavaScript

import { Pulse } from "@mightys-dev/pulse/web";

Pulse.init("APP_KEY", { appVersion: "1.0.0" });
Pulse.track("level.complete", { props: { level: 3 } });

HTTP

curl -X POST https://in.mightys.dev/api/v1/signals \
  -H "X-App-Key: APP_KEY" \
  -H "Content-Type: application/json" \
  -d '[{"timestamp":"2026-11-13T08:00:00Z","type":"level.complete"}]'
Platforms and SDKs
PlatformHow
iOS, iPadOS, macOS, tvOS, watchOSPulse SDK for Swift
AndroidPulse SDK for Kotlin and Java
FlutterPulse SDK for Flutter (Dart)
UnityPulse SDK for Unity (C#)
Web and NodePulse SDK for JavaScript and TypeScript
.NET apps and serversPulse SDK for .NET (C#)
Anything else that can send HTTPOne POST to the ingest endpoint

Packages: Swift package on GitHub, Android library on Maven Central, mightys_pulse on pub.dev, Unity package on GitHub, @mightys-dev/pulse on npm, Mightys.Pulse on NuGet

No SDK for your engine yet? Send over plain HTTP, or keep the SDK you already have (next section).

SDK docs

Set up with your AI coding agent

Switching

Coming from another SDK

Already shipping another analytics SDK? The ingest endpoint also accepts two other widely used request formats. Keep the SDK and the signal calls you have, change the address it sends to, and use the compatibility key from your app settings.

Privacy

What we keep, and what we do not

No cookies
The SDKs set none and the ingest endpoint accepts none.
No stored IP addresses
The address is used once, when a signal arrives, to derive a country. Then it is discarded. It is never stored.
No personal fields
A signal has no name, no email address and no advertising ID.
Hashed identifiers
A user ID is optional. It is hashed on the device and never leaves it in readable form.
Your data
CSV export is on every plan, including Free.

All trust facts

Signals by platformsample data

iOS. 4,564,365 signals, 58.0%Android. 3,305,230 signals, 42.0%
  • iOS
  • Android

What we receive

One signal, in full

This is the whole request body an SDK sends for one signal.

JSON
[
  {
    "timestamp": "2026-11-13T08:00:00.000Z",
    "sessionId": "random-session-id",
    "userHash": "optional-client-side-hash",
    "type": "level.complete",
    "value": 1.5,
    "debug": false,
    "system": {
      "platform": "mobile",
      "osName": "iOS",
      "osVersion": "18.0",
      "appVersion": "1.2.3",
      "appBuildNumber": "42",
      "deviceModel": "iPhone16,1",
      "locale": "sr-RS",
      "sdkName": "pulse-swift",
      "sdkVersion": "0.9.5"
    },
    "props": { "level": 3 }
  }
]
timestamp
When it happened.
sessionId
A random ID made on the device. It is not tied to a person.
userHash
Native SDKs send it with no setup: the hash of a random install id, or of your own user id if you set one. In a normal browser it is sent only if you set a user. It is hashed on the device, then hashed again on the server with a salt that belongs to your app. The original value is never stored.
type, value, props
What you chose to send. Keep personal data out of props.
system
Platform, OS name and version, app version and build, device model, locale, SDK version.

Hosting, retention and sub-processors are on the Trust page