Why am I not seeing results in my A/B test?
Our analytics provide real-time results, so when you start an A/B test, you should see data instantly. However, in some cases, no results appear. This guide helps you troubleshoot the issue. Here are a few common reasons you might not see data yet.
Your A/B test was started and published but not deployed
If staging is enabled on your project, you still need to deploy the latest version to make all variants visible to your site’s visitors.
You haven’t had any visitors yet
The tested page might not receive much traffic. To confirm the A/B test is working, open the page on several devices and ensure the conversion event is triggered.
Your site is behind a reverse proxy
A/B tests use the Server-Timing header to dynamically assign variants across your site, regardless of the page initially requested. Misconfigured proxies—such as those that cache responses or modify headers—can interfere with this process, causing incorrect or missing assignments.
Key guidelines for proxy configuration
Disable caching: Do not cache site responses. A/B test assignments are dynamic, and caching may serve stale or incorrect data.
Preserve the Server-Timing header: Ensure your proxy passes the Server-Timing header without modification. If you add custom metrics, append them without overwriting existing values.
Test your setup: Use browser developer tools to verify that the Server-Timing header is present and that A/B tests function correctly. Look for entries like:
Server-Timing: abtests;dur=1;desc="zyMcCog_M=augiA20Il"
If problems continue, check your proxy logs, confirm caching is disabled, or contact support