-
-
Notifications
You must be signed in to change notification settings - Fork 847
Open
Labels
Complexity: LargeComplexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelEREmergent RequestEmergent RequestIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Wins Pagehttps://www.hackforla.org/wins/https://www.hackforla.org/wins/role: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Milestone
Description
Note: This issue came from the Task List Dev Leads.
Emergent Requirement - Problem
Issue Description
Can Google Analytics' tags track the “Share your wins” button on the Wins page to see how many times "Share your wins" button is clicked? This way we can compare it to the number of wins submissions we get (aka how many times submit button is clicked).
Questions
- Is it possible to use Google Analytics' tags on the “Share your wins” button?
- If using Google Analytics' tags isn't feasible, is there another way to do it?
Note: From Wins form research conducted by UX Researcher Vivian.
Who was involved
- @JessicaLucindaCheng
@SAUMILDHANKAR
What happens if this is not addressed
We won't know how many people start a Wins submission but don't complete it.
Resources
Recommended Action Items
- Create an issue to add a Google Analytics tag to the submit wins button, so that we can tell the number of times it is clicked by date range.
- in the issue, indicate what resources beyond the normal team resources access a general member already has, that they will need to test and implement this issue.
- reference this ER in the resources of that issue
- add a ready for merge team label to the issue, so that it can get reviewed.
- add a link to that issue in this ER.
- when that issue is added to the prioritized backlog, close this ER.
Potential solutions [draft]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: LargeComplexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelEREmergent RequestEmergent RequestIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Wins Pagehttps://www.hackforla.org/wins/https://www.hackforla.org/wins/role: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Type
Projects
Status
ERs and epics that are ready to be turned into issues