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

ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics #4388

Open
6 tasks
JessicaLucindaCheng opened this issue Apr 3, 2023 · 2 comments
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Wins Page https://www.hackforla.org/wins/ role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 3, 2023

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

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]

@JessicaLucindaCheng JessicaLucindaCheng added the size: 0.25pt Can be done in 0.5 to 1.5 hours label Apr 3, 2023
@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Apr 3, 2023
@github-actions

This comment was marked as resolved.

@JessicaLucindaCheng JessicaLucindaCheng added role: back end/devOps Tasks for back-end developers ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.5pt Can be done in 3 hours or less Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: 0.25pt Can be done in 0.5 to 1.5 hours labels Apr 3, 2023
@JessicaLucindaCheng JessicaLucindaCheng changed the title ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics ER from TLDL: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics Apr 3, 2023
@JessicaLucindaCheng JessicaLucindaCheng added size: 2pt Can be done in 7-12 hours and removed size: 0.5pt Can be done in 3 hours or less labels Apr 3, 2023
@JessicaLucindaCheng JessicaLucindaCheng added Issue Making: Level 2 Make issue(s) from an ER or Epic ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 25, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 06. Data strategy milestone May 7, 2023
@ExperimentsInHonesty ExperimentsInHonesty added Issue Making: Level 2 Make issue(s) from an ER or Epic ready for issue making Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level and removed Issue Making: Level 2 Make issue(s) from an ER or Epic ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 10, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the ER Emergent Request label Oct 22, 2023
@JessicaLucindaCheng JessicaLucindaCheng changed the title ER from TLDL: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics Feb 8, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Draft Issue is still in the process of being created label Jun 4, 2024
@JessicaLucindaCheng JessicaLucindaCheng self-assigned this Jun 4, 2024

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty removed the Draft Issue is still in the process of being created label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Wins Page https://www.hackforla.org/wins/ role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours
Projects
Status: ERs and epics that are ready to be turned into issues
Development

No branches or pull requests

2 participants