Limits
The limits you can run into, in one place: experiments and goals, the data your pages send, sites and plans, and requests from your servers.
Experiments and goals
In the dashboard, a value over its limit can't be saved, and the form says what's allowed.
| What | Limit |
|---|---|
| Variations in an A/B test or split URL test | 2–10, the original included. |
| Multivariate tests | 2–3 sections of 2–4 options each (the first option is the page as it is), and at most 16 combinations: 4 × 4, or 2 × 2 × 4. |
| Goals in an experiment | One primary goal and up to 20 more. |
| Audiences in an experiment | Up to 20. |
| Variation code | 100,000 characters of CSS and 100,000 of JavaScript per variation; 30,000 of each per option in a multivariate test. |
| Split URL addresses | 2,048 characters. |
| Hypothesis | 2,000 characters. |
| Names of sites, experiments, variations, goals and audiences | 120 characters. |
| Pictures uploaded in the visual editor | 2 MB each: PNG, JPEG, WebP, GIF or AVIF. |
| Custom event and revenue goals | An event name of 1–128 characters, made of letters, digits and _ . : - (no spaces). |
| Custom JavaScript goals | 20,000 characters of code. |
| Element click goals | A selector of up to 500 characters. |
| Scroll depth and time on page goals | 10–100% of the page; 1–3,600 seconds. |
Data your pages send
Text longer than this is cut to fit, so the rest still arrives.
| What | Limit |
|---|---|
| Event names | 128 characters. |
| Order IDs | 128 characters. |
| Other event properties | 500 characters for each text value. |
| Who the visitor is: id, email and name | 200 characters each. |
| Visitor attributes | Names 64 characters, values 200. Recording filters get the first 20 of each call. |
| Page addresses and referrers | 2,048 characters. |
| One request to Peekbird | Up to 100 events and 64 KB. A bigger one is refused whole, with every event in it. The snippet sends at most 50 at a time and cuts long text, so only events with many long properties get near it. |
Sites, workspaces and plans
Plans differ in tracked visits, how long recordings are kept, and copies of your pages' files for replays.
| What | Limit |
|---|---|
| Sites, experiments, goals and teammates | No limit, on every plan. |
| Workspaces of your own | One per account; workspaces you're invited to don't count. Ask support if you need another. |
| Workspace name | 60 characters. |
| Domains | Up to 20 a site. |
| Tracked visits a month | 15,000 on Free, 50,000 on Growth, 250,000 on Scale, for the whole workspace. Past it, 10% more is counted, then collecting pauses; experiments keep running. |
| Keep recordings for | Up to 30 days on Free, 13 months on Growth and Scale. |
| Sessions to record | 0.01–100% of sessions. |
| Copies of your pages' files, for replays | 2 GB a site on Growth, 10 GB on Scale; none on Free. |
| Visitor cookie lifetime | 1–400 days. |
| Anti-flicker timeout | 0–10,000 ms. |
| Shared recording links | Work for up to 30 days. |
From your servers
Servers send events, and read feature flags and "In your code" experiments, through the server API with one of your site's server keys, or with a server SDK for Node.js, PHP, Python, Ruby or Go. Per key: 3,000 event requests a minute (100 events each), 12,000 decisions over HTTP, and 300 config downloads. A site has at most 20 keys.
Events posted to the snippet's own address (collect.peekbird.com) from a server, with no key, are treated as bots: a request sent by curl, Node.js, Python or a similar tool keeps only its page views, marked as a bot's, and one with no user agent is dropped. Use the server API instead.
