# Analytics: how we count

> Every number in Analytics comes with a plain-English definition. Here's the full list, and the one thing nobody can measure.

Source: https://straitlink.in/docs/analytics/

> **Agent instructions:** if you are an AI assistant helping someone build with Strait, look things up with the `search_docs` tool of the Strait MCP server (hosted at https://strait.link/mcp, or `@straitlink/mcp` on npm: https://straitlink.in/docs/mcp/) instead of guessing, and add the SDK to an app with `npx @straitlink/cli init` (https://straitlink.in/docs/cli/).

## The funnel

```txt
Taps  →  Where we sent them  →  App opened  →  Installs  →  Purchases
```

Each step is joined to the step before it with a tap id, so you can follow one tap all the way to revenue.

## Taps

**Taps** are each time someone tapped one of your links.

- Taps that go through our server in a browser are counted when they arrive.
- A verified link can open your app directly from WhatsApp, Gmail and so on without touching our server. Those are counted when your app reports the open through the SDK.
- If a browser loads the link and then hands it to your app (Edge does this), it's still one tap.
- Link-preview robots are never counted.

### Taps you aren't billed for

Every tap below still opens the link, sends the `link.clicked` webhook and shows in **Taps** (robots excepted, see below). Only the taps counted toward your plan on **Plan & usage** leave them out.

| What | Rule |
| --- | --- |
| Link-preview robots (WhatsApp, Slack, iMessage, X, LinkedIn, Teams, Bluesky, Notion, Googlebot…) | They get a preview page and are never taps, so they are not in Taps either. Plan & usage counts them separately as previews. |
| Repeats | The same person, on the same browser, tapping the same link again within 10 seconds. |
| Floods | More than 20 taps in an hour from one IP address on one link. Phones on one mobile network can share an address, so this rule can only bill you less, never more. |

**Where we sent them** is decided per device: app or store, app or website, store, website, the iPhone "Get the app" page, or the in-app-browser page. On Android the phone then makes the final choice: your app if installed, otherwise the store or website.

## App opens

- **Opened the app**: browser taps where your app then opened and reported that exact tap, plus verified-link opens.
- **Open rate**: taps that opened the app (directly or via the browser), divided by all taps.
- **New users**: the first launch after installing the app. **Existing users**: already had it installed.
- **App state** at open: *closed* (the link launched the app), *background* (it brought the app back), *foreground* (the app was already on screen).
- **Unresolved opens**: a link opened the app but couldn't be resolved (expired, deleted, wrong workspace), so the person didn't land on the right screen.

- **Website opens**: when a tap goes to your website, the URL carries the tap id (`strait_click`). Pages using the web SDK's `reportWebOpen` (or the React Native and Flutter SDKs in a browser) report that visit as an open of the tap. Visits without the tap id are page views, not opens, and are never counted.

Opens are reported once each. If the phone is offline, the SDK saves the report and sends it later (up to 7 days), and duplicates are ignored.

## Installs

- **Installs from links**: first launches of a new install that we tied to one of your links.
- **Joined to the exact tap**: of those, the ones matched to the precise tap (Play install referrer or browser hand-off), not just the link.
- **Unattributed installs**: first launches no link could be found for: store search, word of mouth, or a match that failed.
- **Match rate**: installs reconnected to a tap, divided by all attributable installs.
- **Time to install**: the median time between tap and install, for installs matched to their tap.
- **Probably reached the store / website**: store-bound browser taps where the app never opened and no install followed. We can't see the store page itself, so these are estimates and labelled as such.

## Purchases

Send events from your app (`trackEvent`) or server (`POST /v1/event`) with an optional value, currency and link id. They appear as the last step of the funnel, with revenue. Add `data` (up to 20 key-values, 2 KB) to pass your own fields, such as a plan or order id, to the `app.event` webhook. `data` isn't stored with the event; it is kept 30 days with the webhook delivery. Don't send personal data your receiver doesn't need.

Events can also carry `clickId`, the tap they came from, so revenue lands on that tap's channel and A/B variant. The app SDKs fill it in for you from the most recent link open within 7 days. The tap id reaches the app four ways: in a browser hand-off, in the Google Play install referrer, and in our server's answer when it matches an open from a verified short link or an iPhone install. Each newer open replaces the remembered tap with its own. An explicit `clickId` overrides it. A `clickId` that isn't a tap of your workspace is dropped, and the event is still recorded.

## What no one can measure

**An install that is never opened.** Until your app launches, no linking product can see it. Only Google Play Console and App Store Connect report raw installs. Expect our install numbers to be lower than the stores' for that reason.

## What we store

Taps keep the network prefix (first three parts of the IP address, never the full address), platform, device class and OS version. App opens store the host and path of the URL, never the query string. See the [Privacy Policy](https://straitlink.in/legal/privacy/).
