Add a source

One middleware, wrapper, or snippet, and every request through your product is attributed to an account. Events land in your warehouse.

App and web

Drop the client SDK into the app your customers use. Route, session, and action context arrives alongside the API traffic.

Identity and auth

Who signed up, who signed in, and who joined which account — usually a webhook you already have somewhere to point.

Services and APIs

One middleware in the request path. Works for incoming calls and for the outgoing ones your service makes.

Gateways and proxies

Instrument at the edge instead of in the application, and cover every service behind it at once.

Serverless and edge

Where there is no long-lived process to hold a middleware, a wrapper does the same job per invocation.

Observability

Already collecting this? Forward what you have and skip the instrumentation step.

Direct ingest

For everything this list does not name. A signed endpoint, a scheduled file, or one POST.