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 events analytics in the new form #3100

Closed
bacharakis opened this issue Nov 28, 2019 · 5 comments
Closed

Add events analytics in the new form #3100

bacharakis opened this issue Nov 28, 2019 · 5 comments

Comments

@bacharakis
Copy link
Collaborator

Adding events analytics in our new form will help us understand where our users drop off.

@karlcow
Copy link
Member

karlcow commented Nov 28, 2019

I'm not confortable with this for the project. I understand the rationale behind it.
Before trying to do more tracking, I would prefer we evaluate the success rate of the current project. That was the goal of the A/B testing. We still do not know if we want to adopt this new form.

@bacharakis
Copy link
Collaborator Author

Hey @karlcow , this is for evaluating the success rate of the new form. Currently, we identified some issues that we can't understand unless we get more information on where users drop off.

This is something that we have agreed with @miketaylr and @adamopenweb a few months ago. The only reason not implementing it before was because we assumed that we won't need to.
In any case, we need the metrics just to understand how the form is performing (currently is a blackbox) for properly evaluating it. We can later drop them.

@adamopenweb
Copy link
Collaborator

I agree that we should remove this level of tracking once the evaluation is complete.

@karlcow Currently we are seeing that the completion rate of the new form is much lower. This is somewhat expected, but it is also not producing an acceptable level of valid reports compared to the current form. The event data will help us understand where users are dropping off in the process so we can determine the next steps.

miketaylr pushed a commit that referenced this issue Dec 4, 2019
Fixes #3100 - Send GA events for issue-wizard clicks/input changes
@miketaylr
Copy link
Member

@bacharakis do we think we can remove this tracking now? Or are we still learning from it?

@bacharakis
Copy link
Collaborator Author

bacharakis commented May 12, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants