Getting your data into Peekbird
One snippet runs A/B tests, session recordings and analytics. Install it once, and it collects what any page shows: the pages people visit and where they came from, their clicks and scrolling, rage and dead clicks, errors and loading speed, plus recordings of the visits you choose to record.
A few lines of code add what only your site knows, and each shows up everywhere it's useful:
| You send | It unlocks |
|---|---|
| Purchases | Revenue, conversion rate and order value per variation; orders in recordings, searchable by order number. |
| Coupons | Codes used and refused in the recording timeline; the sessions where a code was refused. |
| Who the visitor is | Names and emails in recordings; one person across their devices. |
| Other events | Goals like "Signed up" for experiments; entries on the recording timeline, and filters. |
| Errors shown | The error messages visitors saw, in the recording timeline; the sessions that hit one. |
| Visitor attributes | Audiences that aim experiments ("plan is pro"), and filters for recordings. |
Where to start
- Install the snippet on every page, first in the <head>.
- Send purchases: most of what experiments and recordings tell you about revenue depends on them.
- Add the rest as you need it.
- Check your fonts, so replays match what visitors saw on every device.
In your dashboard, Install & data (under your site) has all of this with your own site's snippet filled in, and a live check that shows each kind of data as it arrives.
Running tests
- Experiments: the three kinds, which pages a test runs on, traffic, and what each status allows.
- The visual editor: changing your real page, and what its warnings mean.
- Goals and audiences: what a test measures, and who takes part.
- QA and preview: checking a test, and your install, before visitors see it.
- How results are calculated: the statistics, and what each verdict needs.
- Feature flags: roll a feature out to some visitors, and switch it off in a click.
On your servers
- Server-side SDKs for Node.js, PHP, Python, Ruby and Go: flags and tests decided on your server, the same way the page decides them, and events sent from it.
- Server API: the same over HTTP, for any language.
Reference
- JavaScript API: every command, with the details that trip people up.
- Automatic events: purchases, carts, sign-ups and more, with no code.
- What the numbers mean: Analytics, Heatmaps, Recordings and Live.
- Funnels: how many visits make it through each step, and the recordings of those who left.
- Speed, CSP and single-page apps: flicker, caching and your Content Security Policy.
- Teams and security, plans and usage, limits and how long data is kept.
