Limits
Every limit in ClickClacks, in one place. Most you’ll never meet; the ones worth knowing are the 2 KB of browser event properties and batching server events.
Updated
Browser tracker
| Limit | Value |
|---|---|
| Event name | 1–128 characters, not starting with $ |
| Event properties / identify traits | 2 KB of JSON; over that, sent without them |
| identify ID | 1–128 characters |
| Events per request | 25 |
| Send interval | Every 5 seconds, at 25 waiting events, and when the page is hidden |
| Events kept for retry | 100 |
| Request body | 128 KiB |
| Event time | Browser clock accepted within 10 minutes of the server’s; otherwise the arrival time is used |
| Session timeout | 30 minutes without an event |
| Click text | 40 characters, links and buttons only |
| Click selector | 64 characters; up to 2 class names |
Mobile SDK
| Limit | Value |
|---|---|
| Event and screen names | 1–128 characters; event names not starting with $ |
| Event properties | 2,048 bytes of JSON, including the SDK’s own keys; over that, sent without yours |
| identify ID | 1–512 characters |
| Events per request | 25 |
| Send interval | Every 5 seconds, at 25 waiting events, and when the app leaves the foreground |
| Events kept offline | 100; the oldest are dropped first |
| Event age | 10 minutes; older events are dropped |
| Session timeout | 30 minutes without an event |
Companies and groups
| Limit | Value |
|---|---|
| Group types on one event | 5 |
| Group types per project | 5 |
| Group type | 1–64 characters of a–z 0–9 _ |
| Group ID | 1–255 characters |
| Group traits | 2 KB of JSON from the browser or a mobile app; 8 KiB from the server API |
Server API
| Limit | Value |
|---|---|
| Items per request | 500 |
| Body | 1 MiB uncompressed; gzip accepted |
| Properties per item | 8 KiB, 255 keys, depth 5 |
| Events per project, sustained | 1,000 per second (60,000 a minute) |
| Events per project, burst | 5,000 per second (50,000 in 10 seconds) |
| Requests per key | 100 per second |
| Timestamps accepted as sent | 7 days back to 10 minutes ahead |
| How event limits are counted | In blocks of 100 events per request, rounded up |
| distinct_id | 1–128 characters |
| insert_id | 1–80 characters of A–Z a–z 0–9 _ - |
| $user_agent / $current_url | 1,024 / 2,048 characters |
| $groups | 5 entries |
| Working server keys per source | 2 |
| Key name | 1–64 characters |
Heatmap capture
| Limit | Value |
|---|---|
| Captures | At most one browser per page, device size and day |
| Elements in a page layout | 1,500 |
| Skip selectors per source | 64, each up to 256 characters |
| Captures kept | 30 days |
MCP server
| Limit | Value |
|---|---|
| Requests per key | About 120 a minute |
| Date window | Up to 3,660 days; last 30 days by default |
| Property filters | 20 per call, each with up to 100 values of 512 characters |
| compare_projects | Up to 100 projects |
Exports
| Limit | Value |
|---|---|
| Events CSV | 50,000 rows |
| Organization export | Events for organizations with up to 50,000, and 8 MiB of JSON in all; download open for 24 hours |
Plans
| Limit | Value |
|---|---|
| Monthly events | 250,000 to 20 million on Growth and Pro; 50 million and up on Enterprise |
| Free events | Identify, merge and alias calls, and group trait updates, never count |
| Data history | 12 months on Growth, 24 months on Pro |
| Seats | Unlimited on every plan |
Server API limits are the same on every plan. Hitting one? Debugging and the error catalogue say what each response means.