-
Notifications
You must be signed in to change notification settings - Fork 44
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
add A/B testing capability #173
Comments
Hi @ghwood what kinds of things would you want to test? ie, with A/B testing often it's about measuring some outcome in order to evaluate success of A or B. What are we measuring? |
Hi @holloway
|
@ghwood thanks, and so you'd want to A/B test UI differences (eg button colours) and how they affect completion of registrations, etc? |
Yes. CTAs, copy, colors, etc. |
@AndrewCalderSpringload 's recommendation for AB testing is CC: @holloway |
Out of the box, More useful would be to track clicks on links and buttons within the website, which may navigate the user to another website, and for the conversion goals above, it's reasonably straightforward. @ghwood, if the list is up-to-date and complete, I can implement them. Tracking conversion goals on a different website, e.g. meeting registrations, is another matter: it requires cooperation from the other website and seems out of scope for this project. |
Yes, this list is generally current for conversions that are clicking on links to another website:
|
It would be helpful to be able to conduct A/B (aka "split") testing on certain web pages.
There seem to be a few options for implementing this within Wagtail, with Wagtail Experiments being one.
The text was updated successfully, but these errors were encountered: