> ## Documentation Index
> Fetch the complete documentation index at: https://docs.manalens.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Events overview

> The event types that ManaLens accepts, where they come from, and the envelope that they share.

Every report reads one table of events. Each event has a type, a few IDs, a `context` object and a `properties` object.

## Event types

| Event type | Description |
| - | - |
| [Page](https://docs.manalens.dev/data/events/page.md) | A page view on a website |
| [Track](https://docs.manalens.dev/data/events/track.md) | A named custom event, such as `signup_completed` or `level_complete` |
| [Identify](https://docs.manalens.dev/data/events/identify.md) | Links a visitor to a known user and sets traits |
| [Game events](https://docs.manalens.dev/data/events/game.md) | Reserved `track` events from games: `game_open`, `session_start`, `session_end`, `error`, `app_unclean_exit` |

Billing providers add their own event types, such as paid invoices and refunds. See [Revenue](https://docs.manalens.dev/features/revenue.md).

## Sources

| Source | Endpoint | `channel` | Types |
| - | - | - | - |
| [Web SDK](https://docs.manalens.dev/sdks/web.md) | `POST /v0/events` | `web` | `page`, `track`, `identify` |
| [Game or app build](https://docs.manalens.dev/sdks/app-events.md) | `POST /v0/events` | `app` | `track`, `identify` |
| [Backend](https://docs.manalens.dev/sdks/server.md) | `POST /v0/events` with the Secret key | `server` | `track`, `identify` |
| [Billing provider](https://docs.manalens.dev/features/revenue.md) | Signed webhook | `stripe`, `paddle` | Provider event types |
| Profile edit in the dashboard | | `dashboard` | `identify` |

`channel` is the event origin. It is not the acquisition channel (`channel_type`), such as Paid Search. See [common fields](https://docs.manalens.dev/data/events/common.md).

## Example

```json theme={null}
{
  "type": "track",
  "event": "signup_completed",
  "message_id": "0f4b0c39-4a77-4f3c-a5e2-6f5c1f2b7d10",
  "channel": "web",
  "version": "0.1.0",
  "original_timestamp": "2026-11-09T10:00:00.000Z",
  "anonymous_id": "3f0c5c1e-8a8e-4c1b-9d7e-2b1f4e6a9c10",
  "session_id": "1762682400000",
  "user_id": "user_123",
  "context": {
    "page": { "path": "/signup", "title": "Sign up", "url": "https://example.com/signup" },
    "referrer": "",
    "locale": "en-US",
    "utm_source": "newsletter"
  },
  "properties": { "plan": "pro" }
}
```

The SDKs fill in the envelope for you. The collector then adds the derived fields: country, device, OS, browser and `channel_type`. See [common fields](https://docs.manalens.dev/data/events/common.md).

## Rules for all events

* A batch has 1 to 50 web or app events, or 1 to 100 server events. A batch cannot mix `server` events with web or app events.
* `message_id` is a UUID. Reports count each `message_id` once. See [idempotency](https://docs.manalens.dev/api/idempotency.md).
* `properties` is a flat object. Values are strings (at most 1024 characters), numbers, booleans or `null`. Nested objects and arrays are refused.
* Unknown top-level fields are refused.
* Event names have at most 128 characters. Use snake\_case names, such as `signup_completed`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.