Can Stealth Analytics Track Backend, Mobile, and Non-Browser Events?

Yes. Stealth Analytics accepts telemetry from anything that can make a POST request, not just browsers. You can send events from a website, a background worker, a payment funnel, a server process, or a hardware project, either through the small frontend script or by hitting the edge endpoint directly with a JSON payload. The only requirement stated on the site is that the source can issue a POST request.

What "non-browser" tracking actually means here

Most analytics platforms assume a browser is the source of every event. Stealth Analytics separates ingestion from the browser entirely. Its stated position is: "If it can make a POST request, we can track it."

That opens up three categories the site explicitly calls out:

• Backend system events — send strict event payloads from your server to track database processes and custom conversions.
• Payment funnel events — fire events at points in a checkout or conversion flow that never render a page.
• Non-web projects — the site names "that robotics project in your garage" as a valid source.

How to send an event without a browser

The site describes two ingestion paths.

1. Frontend script (for web traffic)

Drop the script in your HTML <head>. This is the standard path for pageviews and browser-side activity.

2. REST API / edge workers (for everything else)

Bypass the browser completely and hit the edge endpoint directly. No SDK or software kit is required — format a standard JSON payload and send it from any language or framework.

The example the site provides:

await fetch('https://api.stealth...', {
  method: 'POST',
  body: JSON.stringify({ name: 'sale' })
});

The site frames the whole setup as "two minutes to first event": script in the head for web traffic, API for everything else.

Checking non-browser events from a phone

The dashboard is described as engineered to feel like a native app and fully responsive. The stated use cases are checking active web traffic on a commute or verifying a server cron job from the gym — so mobile viewing is treated as a first-class scenario, not an afterthought.

What this means for your setup

Custom events are capped per plan: 2 per project on Free, 10 on Indie Hackers, 50 on Pro. If your backend tracking depends on many distinct event names, that per-project limit is the constraint to check before choosing a tier.

Where to look next

If you are deciding between plans based on event volume and site count, the usage buckets cover your whole portfolio rather than charging per domain — one site or fifty count toward the same limit. If you want to compare the script's footprint against other tools, the site lists GA4 at ~45.0 KB, Simple Analytics at ~3.0 KB, Plausible at ~1.2 KB, and Stealth Analytics at 0.7 KB.