TangentDeveloper documentation

Product analytics by Selicatech. One endpoint, eight SDKs, and a wire format small enough to implement in an afternoon.

Browser

JavaScript for web apps and marketing sites. Autocapture, session replay, attribution, consent — each a separate plugin, so you ship only what you use.

Browser SDK

React

One client created at module scope, reachable from any component, immune to StrictMode, Fast Refresh and remounting.

React SDK

Node.js

Batching, retry, byte-bounded POSTs, Express and Koa request trackers, and a shutdown that drains the queue.

Node.js SDK

Python

A client per process. track() never blocks and never raises; a background thread batches, splits and retries.

Python SDK

Java

One SelicaClient built at start-up. A daemon thread does the delivery; errors reach a callback, never your request path.

Java SDK

Go

Pure standard library. Track never blocks and never returns an error — analytics must not be able to fail a request.

Go SDK

Swift

iOS and macOS. One throwing call in the whole SDK — the initialiser, on a malformed key. Everything after it is non-throwing by design.

Swift SDK

Android

Kotlin. One client in your Application, batched POSTs on the SDK's own thread, plugin hooks wrapped so your exceptions never reach your app.

Android SDK

No SDK for your language?

Everything arrives through one authenticated POST of a JSON batch. Implement the wire format directly, or send from a data pipeline or log shipper.

HTTP ingest API

Start here

If you want to…	Go to
See an event arrive in the next ten minutes	Quickstart — install, initialise, track, identify, verify, in all seven languages
Understand the data model before writing code	Ingest overview — events, identity, properties, groups, entities, revenue
Send events without an SDK	HTTP ingest API and Server-side
Know which key goes where	Authentication
Check whether your platform supports a feature	SDK support matrix

How it fits together

Everything Tangent knows about your product arrives through one endpoint: a POST of a JSON batch, authenticated by an API key. The SDKs are conveniences on top of it — they generate and persist an anonymous id, batch, retry, back off, and give you identity, groups, revenue, experiments and a plugin pipeline. None of them can send anything the endpoint would not accept from curl.

Batches are validated per event: one malformed event does not lose the other 999, and the response names each refusal by index with every reason. Delivery is at-least-once with server-side de-duplication on a client-generated messageId, so retrying is always safe.