Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Nofliq Server-Side A/B Testing

开发者 victoriavegab
更新时间 2026年8月18日 11:09
PHP版本: 8.1 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

a/b testing split testing experiments server-side flagship

下载

1.9.2 1.9.1

详情介绍:

Server-side A/B testing for WordPress that eliminates flicker. Most A/B testing tools decide which variant to show in the browser, using JavaScript that runs after the page loads. This causes the "flash of original content" (FOOC): the visitor briefly sees the original version before the variant replaces it. It looks broken and it skews results. This plugin takes a different approach. It decides the variant in PHP, on the server, before the HTML is sent to the browser, and exposes the decision to your theme so the correct variant is rendered from the first byte. The visitor only ever sees the assigned variant, with no flash and no layout shift. Two decision engines The plugin has two modes, chosen in the settings: Flagship is the default because it adds targeting, segmentation and centralized reporting that a local engine cannot provide. Local mode is fully functional on its own. How rendering works This plugin decides and exposes the variant; your theme renders it. The decision is made available to the page as window.abTestData, and your theme (or a small snippet) reads it to render the assigned variant server-side via the abtf_runner() helper. This is the standard server-side pattern used by tools like LaunchDarkly, Optimizely and Split: the plugin decides, your code applies. A minimal integration example is provided in the FAQ. Key features

安装:

  1. Upload the plugin files to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugins screen.
  2. Activate the plugin through the "Plugins" screen in WordPress.
  3. Go to AB Tests - Settings and choose a Decision Engine. For Local mode, no further configuration is required. For Flagship mode, enter your AB Tasty Flagship Environment ID and API Key.
  4. Create an experiment under AB Tests - Experiments. New experiments start paused.
  5. Review the configuration, then click Resume to activate the experiment.

屏幕截图:

  • Experiments list showing active and paused tests, each with its flag key, CSS selector, tracked event and target URLs.
  • Decision Engine selector: run experiments locally with no external service, or use AB Tasty Flagship for remote targeting and segmentation.
  • Creating an experiment: define the flag key, CSS selector, tracked event, target URLs and the control and challenger variants.
  • Visitor ID Provider options: fingerprint, Heap analytics, or a custom JavaScript variable.

常见问题:

Do I need an AB Tasty Flagship account?

No. In Local mode the plugin decides variants on your own server and needs no third-party account. You only need a Flagship account if you choose Flagship mode, which adds remote targeting, segmentation and the Flagship dashboard.

Does it require Redis?

Redis is not strictly required, but it is recommended at scale. The plugin uses Redis to cache variant assignments and to store conversion counters for fast reporting. Without Redis the plugin still works: variant assignments fall back to the database, and in Local mode conversions are recorded in the database as well.

Why do new experiments start paused?

Starting paused lets you verify the configuration (selector, URLs, flag key, variants) before the experiment serves any variant. Only active experiments are applied, so a paused start prevents assignments from being cached before you are ready.

How does it avoid flicker?

The variant is decided in PHP before the HTML is generated, so your theme can render the correct variant from the first byte. There is no JavaScript swap after load, which is what causes flicker in client-side tools.

Does the plugin change my page content automatically?

No. The plugin decides and exposes the variant; your theme renders it. This keeps the plugin theme-agnostic and avoids the flicker that DOM-manipulation approaches cause. See the next question for a minimal integration example.

How do I render the variant in my theme?

The plugin exposes the decided variant through the abtf_runner() helper. Call it in your theme where you want to render the variant, before output. For example: `<?php $runner = abtf_runner(); $result = $runner->run( 'your_flag_key' ); $variant = $result['variant']; if ( $variant === 'control' ) { // render the control version } else { // render the variant version } ?>` The decision is made in PHP before the HTML is sent, so there is no flicker. The same variant is also available in JavaScript as window.abTestData for client-side needs.

更新日志:

1.9.2 1.9.1 1.9.0 1.8.0