Core concepts
You only need five terms to use Anosys.
Workspace
Your company's space in Anosys. Everyone you invite under Settings → Users sees the same endpoints, dashboards and evaluations.
Endpoint
An endpoint is where data arrives. You create endpoints under Collecting → Endpoints (or during onboarding). Each endpoint has its own URL and its own activity graph, so you can see at a glance whether data is flowing. Older screens and snippets call it a pixel or ingestion channel; it is the same thing.
Use one endpoint per source, for example one for your marketing site, one for your app, and one for your team's Claude Code usage. That keeps dashboards clean.
Endpoint type
When you create an endpoint you pick a type. The type tells Anosys how to label the fields it receives.
| Type | Use it for |
|---|---|
| Website / Advertising Tracker | Website and product analytics with the tracker script |
| Claude Code & Codex CLI | Claude Code, Codex CLI and Antigravity hooks |
| OpenTelemetry / AI Agents | The Anosys SDKs for OpenAI, Anthropic and the Claude Agent SDK, and any OpenTelemetry source |
| Generic / Custom HTTP | Your own events over REST or webhooks |
| Custom Variables | Events that only use your own custom fields |
| Networking & Monitoring | Network and infrastructure signals |
| Industrial / Scientific | Sensor and device data |
Coding-tool hooks need the right type
The Claude Code, Codex and Antigravity installers check your key and reject keys from other endpoint types. If an install fails with a key error, create a Claude Code & Codex CLI endpoint and use its key.
API key
Most SDKs and hooks authenticate with an API key. Create one in Collecting → Integration Options, select your endpoint, open the API tab and click Create New API Key.
Endpoints accept data in two modes, which you choose on the same screen:
| Mode | How it works | Use it for |
|---|---|---|
| Unauthorized | The endpoint URL itself identifies your workspace. No header needed. | Browser trackers, image pixels, quick tests |
| Authorized (API Key) | Send to the shared ingestion URL with an anosys-apikey header. |
Servers, SDKs, anything where you can keep a secret |
Never put an API key in browser code
Anything shipped to a browser is public. In web pages use the tracker script, which doesn't need a key. Keep API keys on your server or in environment variables.
Custom fields
Every endpoint accepts your own fields alongside the ones Anosys fills in automatically. Name them by type and number, in URLs (GET) and JSON bodies (POST) alike:
| Type | Field names | Example |
|---|---|---|
| Text | cvs1, cvs2, … |
cvs1=pro_plan |
| Number | cvn1, cvn2, … |
cvn1=42.5 |
| True/false | cvb1, cvb2, … |
cvb1=true |
The highest-numbered text fields are reserved for Anosys; the console marks them as Reserved in Field Mapping.
Field mapping
Numbered fields are hard to read in a dashboard. Collecting → Field Mapping lets you give each field a friendly name (for example cvs1 → customer_tier) so it is readable in the console. Two shortcuts help: AI Assisted Naming suggests names from a description or code you paste, and Clone friendly names from other pixel copies the names from an endpoint you already set up.
Next step
Go back to Get started and pick your goal.
