Search

Why am I not seeing results in my A/B test?

Learn why your A/B test may not be showing results and how to troubleshoot common causes.

When you start an A/B test, analytics update in real time, so you should see results almost immediately. If no data appears, one of the issues below is usually the cause.

Your A/B test is published but not deployed

If staging is enabled on your project, publishing the test is not enough. You also need to deploy the latest version of your site so visitors can be assigned to each variant. Make sure you deploy after starting or updating an A/B test.

Your page hasn’t received any visitors yet

If the tested page has low traffic, results may not appear right away.

To confirm the test is working:

Open the tested page on multiple devices or browsers.
Trigger the conversion event manually.
Check whether visits and conversions begin to appear in analytics.

Your site is behind a reverse proxy

Framer A/B tests rely on the Server-Timing header to assign variants consistently across your site, even when visitors enter through different pages.

If your site uses a reverse proxy, misconfiguration can prevent assignments from working correctly. This often happens when responses are cached or headers are modified.

Proxy configuration guidelines

Follow these guidelines to ensure A/B tests work correctly behind a proxy.

Disable caching: Do not cache site responses. A/B test assignments are dynamic, and caching can cause stale or incorrect variant data.
Preserve the Server-Timing header: Your proxy must pass the Server-Timing header without modification. If you add custom metrics, append them instead of overwriting existing values.
Test your setup: Use your browser’s developer tools to confirm the Server-Timing header is present and unchanged. You should see entries similar to:
Server-Timing: abtests;dur=1;desc="zyMcCog_M=augiA20Il"

If results still don’t appear, review your proxy logs, double-check that caching is disabled, or reach out to support for help.

If you still have issues with your A/B test, reach out to us through our contact page and we’ll help you out.

When you start an A/B test, analytics update in real time, so you should see results almost immediately. If no data appears, one of the issues below is usually the cause.

Your A/B test is published but not deployed

Your page hasn’t received any visitors yet

If the tested page has low traffic, results may not appear right away.

To confirm the test is working:

Open the tested page on multiple devices or browsers.
Trigger the conversion event manually.
Check whether visits and conversions begin to appear in analytics.

Your site is behind a reverse proxy

Framer A/B tests rely on the Server-Timing header to assign variants consistently across your site, even when visitors enter through different pages.

If your site uses a reverse proxy, misconfiguration can prevent assignments from working correctly. This often happens when responses are cached or headers are modified.

Proxy configuration guidelines

Follow these guidelines to ensure A/B tests work correctly behind a proxy.

Disable caching: Do not cache site responses. A/B test assignments are dynamic, and caching can cause stale or incorrect variant data.
Preserve the Server-Timing header: Your proxy must pass the Server-Timing header without modification. If you add custom metrics, append them instead of overwriting existing values.
Test your setup: Use your browser’s developer tools to confirm the Server-Timing header is present and unchanged. You should see entries similar to:
Server-Timing: abtests;dur=1;desc="zyMcCog_M=augiA20Il"

If results still don’t appear, review your proxy logs, double-check that caching is disabled, or reach out to support for help.

If you still have issues with your A/B test, reach out to us through our contact page and we’ll help you out.

When you start an A/B test, analytics update in real time, so you should see results almost immediately. If no data appears, one of the issues below is usually the cause.

Your A/B test is published but not deployed

Your page hasn’t received any visitors yet

If the tested page has low traffic, results may not appear right away.

To confirm the test is working:

Open the tested page on multiple devices or browsers.
Trigger the conversion event manually.
Check whether visits and conversions begin to appear in analytics.

Your site is behind a reverse proxy

Framer A/B tests rely on the Server-Timing header to assign variants consistently across your site, even when visitors enter through different pages.

If your site uses a reverse proxy, misconfiguration can prevent assignments from working correctly. This often happens when responses are cached or headers are modified.

Proxy configuration guidelines

Follow these guidelines to ensure A/B tests work correctly behind a proxy.

Disable caching: Do not cache site responses. A/B test assignments are dynamic, and caching can cause stale or incorrect variant data.
Preserve the Server-Timing header: Your proxy must pass the Server-Timing header without modification. If you add custom metrics, append them instead of overwriting existing values.
Test your setup: Use your browser’s developer tools to confirm the Server-Timing header is present and unchanged. You should see entries similar to:
Server-Timing: abtests;dur=1;desc="zyMcCog_M=augiA20Il"

If results still don’t appear, review your proxy logs, double-check that caching is disabled, or reach out to support for help.

If you still have issues with your A/B test, reach out to us through our contact page and we’ll help you out.

FAQ

Why am I not seeing results in my A/B test after starting and publishing it?

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.

How can I confirm that my A/B test is working if I 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.

What should I check if my site is behind a reverse proxy and A/B tests aren't working correctly?

A/B tests use the Server-Timing header to dynamically assign variants across your site. Misconfigured proxies—such as those that cache responses or modify headers—can interfere with this process. Make sure to disable caching, preserve the Server-Timing header, and use browser developer tools to verify that the Server-Timing header is present and that A/B tests function correctly.

Updated

June 15, 2026

Why aren't the effects in my project functioning

Why can’t I set an element to position Fixed?

Why is my Framer canvas appearing blank

Why is my site not filling the screen on the Phone breakpoint?

Why isn’t my website’s accordion content getting indexed?