Organisations and projects
An organisation is your company's account: it has the subscription, the members and their roles. Inside it, a project holds the data of one product or website: its events, users, groups, pageviews, charts, dashboards and alerts. Projects are unlimited on every plan; the monthly event allowance is shared by the organisation.
Each project has a timezone. Days, weeks and months in charts follow it, so "today" is your team's today.
Members and roles
| Role | Can |
|---|---|
| Owner | Everything, including billing, deleting the organisation and transferring ownership |
| Admin | Manage projects, channels, API keys, destinations and members |
| Member | Create and edit charts, dashboards, segments and alerts |
| Viewer | See everything, change nothing |
Invite people from Organisation → Members. An invitation expires after 7 days and can only be accepted by the invited email address, once verified.
API keys
Keys are created per project under Project settings → API keys and shown once. LogZuno stores only a hash.
| Scope | Use it for |
|---|---|
| Ingest | Sending events, users, groups, insights and pageviews. Safe in front-end code: it can't read data |
| Server traffic (AI visibility) | Sending your server's requests to /v1/hits. Keep it on the server: it vouches for visitors' IP addresses |
| Read | Reading data through the REST API |
| Admin | Reading and changing data through the REST API |
An ingest key also has two switches, New channels and New groups. Turn them off and the key may only name channels and groups that already exist, which stops a leaked front-end key from filling your project with junk channels.
Channels
Every event belongs to a channel, such as signups, billing or errors. A channel is created the first time an event names it (if the key may create channels). Channel names are stored in slug form, so Billing and billing are one channel. An admin can mute a channel: muted channels send no push notifications to anyone.
Events, users and groups
- An event is something that happened: a name, a channel, and optionally a user, a group, a description, an icon and up to 200 properties.
- A user is anyone your events name with
user_id. Identify adds properties such as name, email or plan. - A group is an account or company. Events and users can belong to one, so you can analyse accounts as well as people. See groups.
Limits
| Limit | Value |
|---|---|
| Event and channel name | 200 characters |
user_id, group_id, anonymous_id | 255 characters |
| Description | 4,096 characters |
| Icon | 16 characters (one emoji) |
| Properties per event | 200, flat (no nested objects or arrays) |
| Property key | 128 characters: letters, digits, - and _ |
| String property value | 8,192 characters |
| Events per batch | 100 |
| Request body | 1 MB |
| Timestamp | Unix seconds, not in the future and not older than 90 days |
Ingestion requests are limited to 5 a minute per project on every plan. A batch of up to 100 events counts as one request, so batching sends up to 500 events a minute. Over the limit, LogZuno answers 429 with a Retry-After header. See the ingestion API reference.