Hi, Mike! Sorry for the delay.
Our plugin is compatible with cache plugins. As stated in the linked article, our plugin basically adds a couple of scripts on your tested pages, which are then used to load alternative content (if needed) by performing a JavaScript redirection to an “alternative URL.” This URL contains query argument (?nab) that tells WordPress the current request belong to an A/B test and content should be switch to the appropriate variant.
In general, this works pretty well. However, there’s a few things you need to keep in mind:
- After starting/stopping a test, you may need to purge your cache. This way, you’ll make sure your tested pages contain the scripts I mentioned earlier. BTW, our plugin already contains a few hooks to do that automatically with common cache plugins… but I’d recommend doing it anyway.
- Some cache plugins and optimizer plugins “optimize” your site by delaying, deferring, minifying, and/or combining JavaScript assets. While this, in general, works as expected, it can break our testing scripts. So please make sure that, if you use this, you exclude nelio-ab-testing scripts from any optimization process.
And that’s it! Hope this helps 😀
Thanks, David! So far, I’ve never encountered any problems. I just wanted to double-check on it to make sure that I don’t miss anything.
Cool! I’m glad to know everything worked smoothly so far.
If you ever encounter any issues, you know where to find us 😀
