Nelio A/B Testing is a WordPress service that helps you optimize your site
based on data, not opinions.
|Author:||Nelio Software (profile at wordpress.org)|
|WordPress version required:||4.7|
|WordPress version tested:||5.0.3|
|Added to WordPress repository:||17-09-2013|
|Total downloads:||72 333|
|Active installs:||1 000+|
Click to start download
Welcome Message. After installing the plugin you'll be able to either start a new free trial or configure your Nelio account.
Free Trial Actions. During your Free Trial, you can get more quota by simply completing the actions we offer you. Tell us a little bit more about your and your site, tweet about Nelio, or recommend us to your friends!
Relevant info with a quick glance. Running experiments are visible in Nelio's Dashboard. There, you'll find a summary of all the relevant information you need.
Progress of your Experiment. Whilst an experiment is running (or once it is finished), you can see how it is performing in the Results of the Experiment page.
Data made easy. Additional graphics help you understand what is going on.
Experiment Management. Manage your experiments without leaving WordPress: creation, deletion, and monitoring!
Experiment Creation. Creating new experiments has never been so easy! Just set a name, a description, and the page you want to test!
Alternatives are Regular Pages. For each page to test, you can create alternatives quickly and easily, from scratch or from already-existing pages!
Account details. View your account information and access your directly from the plugin.
Use our plugin in more than one site. You can use our plugin and service on more than one site. Very useful for staging and production environments!
Different types of experiments. Our product lets you test different aspects of your WordPress site; just select what you want to test and create the experiment!
Heatmaps. Our service lets you analyse the hottest areas of any page on your site so that you can understand your customers better.
Why should I use an A/B Testing Solution specifically designed for WordPress?
- Smooth learning curve. There is no need to learn yet another tool.
Everything (from the creation of tests to the visualization of the results) is done from the WordPress dashboard you are familiar with, resulting in a well-known, perfectly integrated user interface.
- Evolve your WordPress site easily. A native WordPress solution automates and simplifies the evolution of your site. Consider, for example, applying the winner alternative in your site as soon as the results are statistically significant. With a native solution, this is as easy as clicking one single button. With a generic tool, on the other hand, you would have to manually modify the page so that it integrates the changes you created in the (winning) alternative.
- Fine-grained testing. The “testing unit” in a generic tool is the web page, since the HTML of the page is the only thing those tools have access to. A native WordPress solution, however, permits you to test any WordPress specific component, such as posts, pages, CSS, themes, child themes, and many more coming!
More questions? Take a look at our site!
We keep an up-to-date Knowledge Base with FAQs, Troubleshooting, compatibility discussions, and more!
4.7.3 (January 31, 2019)
- Bug Fix. Sometimes, WordPress’ autosave feature didn’t work because our plugin was adding a script into AJAX requests. This has now been fixed.
4.7.2 (December 19, 2018)
- Bug Fix. The plugin wasn’t able to properly track conversions in Headline experiments (all variations reported the same results). This has now been fixed. Unfortunately, already-existing experiments will have to be stopped and relaunched.
4.7.1 (December 7, 2018)
- Bug Fix. Some buttons in Gutenberg must be hidden when editing alternative content. Version 4.7.0, however, hides them always. This should not happen and this version makes sure the buttons are only hidden when editing alternative content.
4.7.0 (December 6, 2018)
- Improvement. Following the release of WordPress 5.0, this version of Nelio A/B Testing adds basic support to Gutenberg.
4.6.23 (November 5, 2018)
- Bug Fix. There was a bug when trimming UTF8 strings. This has now been fixed by using
4.6.22 (October 9, 2018)
- Improvement. Search posts, pages, and custom post types using their ID.
4.6.21 (September 27, 2018)
- Bug Fix. There was an error when exporting the results of the experiment in CSV format. This has now been fixed.
4.6.20 (September 3, 2018)
- Bug Fix. Some heatmap experiments couldn’t be started because, apparently, “the tested element wasn’t published” even though this statament didn’t make any sense for that element (e.g. your latest posts). This has now been fixed.
- Bug Fix. Order completed tracking didn’t work as expected. This has now been fixed.
4.6.19 (July 23, 2018)
- Improvement. Added a new filter
nelio_ab_testing_heatmap_url. Using this filter, you can change the URL of the page on which a heatmap will be printed. Especially useful when cross-site origin errors appear (when WordPress is behind multiple domains with redirections).
- Bug Fix. Sometimes, when viewing a heatmap, the plugin triggered a redirection to a URL such as
https://https//. This has now been fixed.
4.6.18 (May 24, 2018)
- Bug Fix. Loading feeds from Nelio’s blog properly.
4.6.17 (May 23, 2018)
- Update. Modified our welcome screen to make it comply to EU’s GDPR.
- Update. Updated links to our website.
- Update. Added PHP required version.
4.6.16 (May 9, 2018)
- Bug Fix. The product under test in a WooCommerce Product Summary Experiments wasn’t properly stored and, therefore, said product couldn’t be actually tested. This has now been fixed.
- Bug Fix. There was a PHP warning due to an object not being properly initialized. This has now been fixed.
- Bug Fix. Alternative widgets weren’t properly loaded in the front-end. This has now been fixed.
- Bug Fix. Some form submission events weren’t tracked. This has now been fixed.
- Improvement. Product image preview wasn’t properly shown whilst creating WooCommerce Product Summary Alternatives. This has now been fixed.
4.6.15 (April 12, 2018)
- Bug Fix. You can now edit alternative menus in a menu experiment.
- Bug Fix. In page/post/custom post type experiments, the checkbox for hiding the original discussion (if any) works as expected.
- Bug Fix. When using the Salient theme, users couldn’t successfully create Menu experiments. This has now been fixed.
- Bug Fix. Duplicating widgets in a widget experiments didn’t work. This has now been fixed.
4.6.14 (March 23, 2018)
- Bug Fix. Free trial tasks couldn’t be completed, because Name and E-Mail couldn’t be shared. This has now been fixed.
4.6.11 (March 21, 2018)
- Bug Fix. Goal selector in experiment progress screen didn’t work. This has now been fixed.
- Bug Fix. Loading a class that was missing in experiments manager.
- Bug Fix. An HTML text in the account page was (incorrectly) escaped and its links couldn’t be clicked. This has now been fixed.
- Bug Fix. Loading post status for alternative content properly.
4.6.10 (March 8, 2018)
- Bug Fix. In the screen for creating menu experiments, the button New Alternative Menu (based on an existing one) didn’t work. This has now been fixed.
4.6.9 (March 3, 2018)
- Improvement. Using WordPress’ HTTP API instead of cURL in
iesupport.php(which was a workaround for old IE browsers).
- Improvement. Removed welcome page, because it sometimes failed due to object caches not clearing transients.
- Improvement. Sanitazing and escaping all data to improve plugin’s overall security.
4.6.8 (February 27, 2018)
- Bug fix. Added support to CoAuthors Plus, to prevent a notice thrown in the frontend.
4.6.7 (January 31, 2018)
- Bug fix. Infinite loop under some weird circumstances in a
get_post_metadatafilter. This has now been fixed.
4.6.6 (January 17, 2018)
- Improvement. New filter for disabling widget experiments (
- Bug fix. Tracking multiple click events properly.
4.6.5 (November 16, 2017)
- New Feature. Export the results of an experiment in CSV.
- Improvement. Click actions now can be triggered from any page (instead of tested pages only).
- Improvement. Cache alternative posts to improve overall speed.
- Improvement. Detect click events properly, even if the clicked element was removed from the DOM.
- Improvement. Using original publication and modified date, so that alternative content doesn’t seem “newer”.
- Bug fix. Match text in click events properly.
- Bug fix. Added safe guard in our tracking script so that, when checking if we’re inside an iframe, it doesn’t throw an Exception.
- Bug fix. Sometimes, the “start date” in the experiments result page wasn’t correct. This has now been fixed.
- Bug fix. When testing the home page, alternative versions should also include the class
4.6.4 (May 11, 2017)
- Bug Fix. HTML tags in experiment names are now properly escaped.
- Bug Fix. CSRF in experiment creation/edition forms has now been fixed.
4.6.3 (April 25, 2017)
- Bug Fix. Sometimes, widgets couldn’t be saved. This has now been fixed.
- Bug Fix. Sometimes, the plugin generated a PHP Fatal Error (file
visitor.phpline 274). This has now been fixed.
- Bug Fix. Disqus threads use the appropriate URL. In the previous version, they were split into multiple threads.
4.6.2 (March 13, 2017)
- Bug Fix. Fixed meta duplication.
4.6.1 (February 9, 2017)
- Bug Fix. Changed jQuery functions
4.6.0 (February 8, 2017)
- Improvements. Post conversion actions now searches among custom post types too.
- Test. Tested with WordPress 4.7.
4.5.11 (December 29, 2016)
- Improvements. The plugin is now compatible with domain mapper.
- Bug Fix. SSRF vulnerability located in
ajax/iesupport.phphas been fixed.
4.5.10 (December 4, 2016)
- Bug Fix. Form submissions are now properly tracked.
4.5.9 (December 1, 2016)
- Bug Fix. URLs including an empty page fragment (just the symbol
#) can now be properly tested.
- Bug Fix. Some click events stopped heatmap tracking unnecessarily.
- Bug Fix. SSRF vulnerability located in
ajax/iesupport.phphas been fixed.
4.5.8 (October 5, 2016)
- Improved Results. Results are now cached more frequently in your WordPress server, so that they’re available right when you need them.
- Bug Fix. There were some issues synchronizing your running experiments with Nelio’s cloud. This has been fixed in this version by adding some extra checks in the synchronization process.
4.5.7 (September 21, 2016)
- Bug Fix. Invalid argument in a
visitor.php) is now fixed.
4.5.6 (August 16, 2016)
- Bug Fix. WooCommerce order complete actions weren’t properly tracked, because of invalid experiment IDs were used. This has now been fixed.
4.5.5 (July 22, 2016)
- Bug Fix. Form submissions were not properly synched. Now they are.
4.5.4 (July 14, 2016)
- Compat Improvement. Some themes weren’t compatible with Nelio because some filters were triggered before the
setup_themeaction. This has now been fixed.
- Bug Fix. Some click events (for instance, when tracking an element whose ID includes a
- i18n Fix. Updated internationalization strings, so that the plugin can be translated in translate.wordpress.org.
4.5.3 (June 7, 2016)
- Bug Fix. AJAX error because of invalid formatted value has now been fixed.
- Bug Fix. WooCommerce product testing broke short description’s format. This has now been fixed too.
4.5.2 (May 20, 2016)
nabforcenow overwrites both the alternative version the user is supposed to see and the user’s participation in the experiment.
- Bug fix. Renamed AJAX parameter from
classfiso that security plugins (such as Wordfence) do not block Nelio’s requests.
4.5.1 (April 29, 2016)
- Bug fix. Invalid
continuestatement changed to
- Bug fix. Some query args were not properly encoded, resulting in an invalid query string. This has been fixed.
4.5.0 (April 8, 2016)
- Security Fix. This new version fixes a couple of security issues we detected. In particular, we improved input sanitization and we limited file access to those within the plugin’s path.
- Bug Fix. In the Results page of a post/page experiment, there are two options for previewing an alternative: clicking on a button or on a preview image. The former works, the latter doesn’t. This has been fixed.
- Minor improvements.
The full change log can be found in