New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A/B testing, Split tests #459
Comments
Other services: |
WebSite Optimizer is being folded into GA. |
I think it was reasonnable for us to recommend using Website Optimizer, but now that they are forcing users to use GA for split testing, we should consider implementing similar functionality in Piwik :) |
It would be fantastic to have A/B testing feature built in Piwik, as a plugin. If you are interested and could help us make it happen, please email at hello@piwik.org! |
my two cents in case you consider implementing A/B testing support (which would be awesome): An extremely powerful way to realize the A/B testing capabilities but also much more would be to add a generic ability to compare segments. The new segment editor is awesome and could be leveraged even more. A/B variant tags would then just be custom variables (typically visit-scope) like any other. A feature like Google Analytics' capability to actively control which users get which variant from inside the analytics system is just for convenience, but not a core requirement IMHO. One can do the actual traffic split on the website server (or loadbalancer) or in the webisteJavascript as well. |
Facebook has released their A/B testing tool: http://facebook.github.io/planout/ https://github.com/facebook/planout - it's written in python. Maybe we could get some inspiration from them. |
I'm in agreement with nkuehn about it being unnecessary to have the ability to control variants from inside the analytics system. I also don't think that the analytics platform is the best place to be running these tests. I'd think that the purpose of the analytics would be to track the test results - and not actually be the medium for defining or conducting the test at all. I've been tracking split-test campaigns in GA for a while now using Events. Earlier today Piwik also introduced Event tracking (http://piwik.org/docs/event-tracking/) which I was then able to integrate with my exiting split testing framework (based on this javascript library on github: https://github.com/jamesyu/cohorts/). Using almost exactly the same code as I use for GA tracking I am now able to track split-test campaigns with Piwik through with the Javascript API and Events. I'm using the following code which reports the same data to both GA and Piwik. First line is passing data to GA, second to Piwik.
That code is called onInitialization of the test (consistency is handled by cookies before test initialization) to track how many times each test runs and then it's allso called a second time onClick passing a different label so that you can segment views from clicks. |
Kissmetrics A/B testing product is interesting also: http://blog.kissmetrics.com/kissmetrics-ab-test-report/ |
It is not the "best place" if you are already using a A/B testing tool, but many people are only using Piwik on their website as "third party javascript" and would enjoy basic A/B tests feature in Piwik. Maybe we could make it possible to use Piwik to measure A/B testing results from another tool? Users could use their favorite A/B testing tool to define and manage tests and variants, and send the data directly to Piwik (or Piwik fetch it from their API). Our vision is to empower users with the toolset to measure and make changes on their website. Running A/B tests (create variants, serve them, measure performance, report results) is a key part of this vision |
Hey Matt, At least we agree that the 'best place' isn't directly within the Piwik platform, but it obviously wouldn't be a breaking change for me if it did include some functions for implementing tests. I have seen the roadmap showing that A/B testing is to be implemented into the core - which is how I found this ticket - and I don't necessarily think it's a bad idea. My primary reason for stating objections is not to prevent it being added (because it would be a greatly welcomed featured for a lot of users) but rather to note that some users would rather make use of a platform independent testing model that does not tie you directly to any one anayltics platform or the other. As such it would mean that the testing would need to be turned on/off at the provider end to prevent bloat in the tracking code for users who don't want it. I get that having to use an external provider is not ideal but self-hosted libraries are also an option to negate the requirement of an external provider. I guess what I'm really saying is that platform independence is important FOR ME but I get that it's not as important for others. As I stated I already run tests and track them with Piwik using Events and I'd actually love to be able to help shape the integration of A/B testing to the core - which is why I commented on this ticket in the hope that someone from the core team would see it and I'd be able to make suggestions and push for my choice of perfect match features in they system ;) |
Good we're having this discussion, it's useful!
Other notes & ideas about A/B plugin:
Keep feedback coming! (edited) |
Interesting also: http://bentilly.blogspot.co.nz/2012/10/ab-testing-scale-cheat-sheet.html Most Winning A/B Test Results are Illusory On the importance of running the power calculation: What is sample size needed? Indicate how long will the test likely take before reaching sample size. |
Hi erveryone, great to see that there's a lot of interest. What do you think about splitting the ticket into two:
The "only" thing that both definitely need is a conceptual decision on how the A/B comparison is realized in the piwik core (e.g. visual segment comparison vs. a specialized feature with own database structures vs. ... ). Probably the hard part... @williampatton: I personally think that custom session-scope variables are more suitable to tag the visitors into A/A2/B/etc than events (conversion is the typical success aspect and conversion is usually session-scope, which events aren't). Unfortunately their number is limited as far as I understand the Piwik API. |
Interesting article: What you should know about the Optimizely vulnerability which discusses the privacy implications of A/B testing implementations, and how, we should aim to avoid 'leaking' A/B tests details in the javascript of A/B testing users. |
I agree that having a full AB Testing feature would be having too much inside Piwik. In my opinion would be enough having an super easy way of integrating Piwik's Events feature, or Piwik's Custom Variables into a third parties A/B Testing tool, just like a pluggable component linking directly Piwik's APIs filling in the data will be measured. |
current experiment picked by A/B testing logic will be stored in a cookie and in a custom variable in piwik visit and page rows, and we may also use it to segment the report data for each experiment. edit: interesting template: http://www.bloggerchica.com/test-design-the-official-doc/ |
Hi what is the status? How could A/B Testing be used? |
FYI: I have a new Job and therefore can' participate with ideas and testing based on real world data any more. The comparison dashboard looks very nice as far as the screeshot can tell. Hopefully you get the funding campaign completed! |
20 lines of code that will beat A/B testing every time What’s Happening In The A/B Testing Market? Seeking Edge, Websites Turn to Experiments ; Optimization technology is reshaping publishers’ decision-making process—and the Web itself. "On 1 June 2012, Google announced that GWO as a separate product would be retired as of 1 August, and some of its functionality would be integrated into Google Analytics as Google Analytics Content Experiments. Google Website Optimizer allowed webmasters to test an alternative version of an entire page, known as A/B testing — or test multiple combinations of page elements such as headings, images, or body copy; known as Multivariate testing. This tool was part of Google Analytics, though accessed through a different user interface. As it was part of Google Analytics, it used the Google analytics scripts." |
ticket opened 2008, added to major 2014, |
@mattab just do it. why not finished? |
This is a PHP based implementation of Facebook PlanOut. https://github.com/vimeo/ABLincoln |
the scientist project looks also possibly interesting https://github.com/daylerees/scientist |
since 2012.. no further insights into this thread? This is an interesting topic. |
Today Google re-launched their A/B testing tool as Google Optimize EditorExample of Google Optimize Report |
It's quite big amount of informations but in my opinion is missing of page loading time. |
Is there a simple way we can testA/B with piwik now ? |
We have released a plugin that works on top of Piwik to run A/B Tests, Split Tests, Experiments see http://www.ab-tests.net/ . A full list of features is mentioned on the Marketplace at https://plugins.piwik.org/AbTesting . It lets you easily run experiments on websites, servers, apps and in campaigns and has lots of features to customize your experiment and to define your success and your expectations for an experiment to increases your sales, revenue, conversions, pageviews, and more. More docs are available at: User Guides, FAQ, Developer docs |
That plugin is proprietary, which is quite disappointing given Piwik's emphasis on the importance of software freedom. Can you reopen this issue until there's a libre/open source A/B testing plugin for Piwik? It's still on the Piwik.org roadmap. |
I 2nd the notion that this issue should remain open until there is an open source alternative available. |
We hope that although not open source, many will enjoy the new A/B testing product. Researching, building A/B testing, documenting, testing, took months of work. By purchasing a license, you get a fully working product, with free updates for duration of license, and you stay in full control of your data. And on top of this, you help the Piwik core platform engineers to grow and keep innovate. That's because a % of all non-open plugin license sales earnings directly go to funding Piwik engineering. In particular what plugins sales fund are:
Next week we'll publish a blog post on the Piwik blog, with a bit more information. ok to reopen the issue as suggested. |
Glad this is reopened and hopeful to see some kind of a core implementation for split testing some time in the future. Also +1 for the licencencing fees contributing to core development. I've suggested to a client that this plugin is worth considering for them and am excited to get the chance to trial it in production. |
Thanks @pattonwebz for advocating the plugin to clients, we do appreciate your support a lot |
I think the plugin idea is great! Hope to see development on this front On Thu, Oct 27, 2016 at 4:50 PM, Matthieu Aubry notifications@github.com
Mayan N. |
Which of our landing pages are the most successful and convert our visitors better?
How often did we wonder if we have the right words and images on our landing page (the page where visitors arrive from your advertising)?[What if changing just one image on the page could increase the visitor conversion rate several times?[[BR]([BR]])] We will never know this without testing.
The good news is that there is a technology that can help us quickly determine the best version of our landing page. It is called Split-Testing and it should be implemented in Piwik.
Piwik should randomly show different versions of the same landing page to our visitors. It should make sure that each version of the page is displayed the same number of times overall and it should even display the same version of the page to the same visitor (to make their experience with our site consistent).
With split-tests we should be able to quickly see which version of the page has a good conversion rate and which one is just a waste of the advertising money. Get rid of the unsuccessful version, keep the good one and our overall conversion will increase.
The text was updated successfully, but these errors were encountered: