What is A/B testing and why does it matter for conversion rate optimization?
A/B testing (also called split testing) shows two or more versions of a page to different visitors and measures which one converts better. It's the core method behind conversion rate optimization (CRO): instead of guessing which headline, layout, or offer performs best, you let real traffic decide, and you don't ship a change to everyone until the data backs it.
How is Kitchen Lab different from a heatmap tool or a survey tool?
Most heatmap and session-recording tools stop at "here's what people did." Kitchen Lab starts there too (click heatmaps, rage clicks, dead clicks, and scroll depth are built in) but it also runs the actual split test, tracks conversions and Stripe-verified revenue per variant, and tells you when a result is statistically significant. It's the testing and the diagnosis in one place.
What counts as revenue in Kitchen Lab? Is it self-reported?
You can log conversions with a simple event call, but if a project connects Stripe, Kitchen Lab matches each conversion to the closest real Stripe charge in the same window and reports that as verified revenue per variant, so the number behind a "B won" call is an actual payment, not just a click on a button.
How do I know when an A/B test result is statistically significant?
Kitchen Lab checks statistical significance on every running test and shows a built-in sample-size calculator, so before you start you can see how many visitors per variant you need to reliably detect a given lift at 95% confidence and 80% power, and roughly how many days that'll take at your current traffic.
Can I run A/B tests for multiple clients without their data mixing?
Yes. Every site or client lives in its own project, with its own tests, ideas, Search Console connection, and Stripe account. Nothing from one project ever shows up in another, which is the main reason agencies pick Kitchen Lab over a single-site CRO tool.
Does Kitchen Lab track Core Web Vitals and Search Console performance too?
Yes. Each project's Search & Speed tab pulls real Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) from Google's Chrome UX Report, and organic clicks, impressions, CTR, and average position straight from Google Search Console, so page speed and search performance sit next to your test results instead of in a separate tool.