Skip to content
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

Open
ghwood opened this issue Apr 12, 2022 · 7 comments · May be fixed by #369
Open

add A/B testing capability #173

ghwood opened this issue Apr 12, 2022 · 7 comments · May be fixed by #369
Labels
contractor Ask contractor to do it enhancement New feature or request

Comments

@ghwood
Copy link
Collaborator

ghwood commented Apr 12, 2022

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.

@ghwood ghwood added enhancement New feature or request contractor Ask contractor to do it labels Apr 12, 2022
@holloway
Copy link
Contributor

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?

@ghwood
Copy link
Collaborator Author

ghwood commented Apr 20, 2022

Hi @holloway
A few initial conversion goals are being considered:

  • meeting registrations
  • endowment donations
  • email list subscriptions
    I expect these will be refined.

@holloway
Copy link
Contributor

@ghwood thanks, and so you'd want to A/B test UI differences (eg button colours) and how they affect completion of registrations, etc?

@ghwood
Copy link
Collaborator Author

ghwood commented Apr 21, 2022

Yes. CTAs, copy, colors, etc.

@ali-haghnia
Copy link

@AndrewCalderSpringload 's recommendation for AB testing is wagtail-ab-testing. With our initial investigations, seems it can address all our needs.

CC: @holloway

@mgax
Copy link
Contributor

mgax commented Dec 12, 2023

A few initial conversion goals are being considered:

  • meeting registrations
  • endowment donations
  • email list subscriptions
    I expect these will be refined.

Out of the box, wagtail-ab-testing can track page visits within the site as conversion goals. This might mean, for example, that a user visits the https://www.ietf.org/endowment/donate-ietf-endowment/ page, regardless of whether they actually make a donation.

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.

@ghwood
Copy link
Collaborator Author

ghwood commented Dec 14, 2023

Yes, this list is generally current for conversions that are clicking on links to another website:

  1. initiate meeting registration -> click on a link in a Wagtail page to visit https://registration.ietf.org
  2. make a donation - > successfully submit the form at https://www.ietf.org/endowment/donate-ietf-endowment/
  3. email list subscriptions -> click a link to visit a webpage at https://www.ietf.org/mailman/listinfo/* (where the exact webpage would depend on the list. Let me know if I can provide any further detail about any of these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contractor Ask contractor to do it enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants