Analysis: App version updates timeliness and retention

[g-opzt]

Data Request Details

What is your specific ask / need from data analytics

• How well do our users do at updating to the most recent versions of the app?
• How do our notifications affect this?
• How does this connect with user retention?

Provide relevant details related to this request below

• VA Mobile App Utilization by App Version

---

Required questions for submittor

Who is the audience for this request (check all that apply)?

• [X] VA mobile app POs
• [X] VA mobile app team
• [ ] BAH
• [ ] Other VA stakeholders (specify them and their connection to this work)
• [ ] Other non-VA stakeholders (specify them and their connection to this work)

Whose perspective is this measurement meant to capture?

• [ ] Current users of the feature/function
• [X] All current app users
• [ ] All potential app users
• [ ] A different audience (specify)

What is the core motivation for the measurement? (You may receive follow up questions to confirm definitions of any key terms used.) We want to measure how many users update their app version and on what timeline in order to:

• [ ] Make a decision (specify the decision)
• [X] Monitor efficiency
• [X] Monitor efficacy
• [ ] Something else (specify the decision)

Optional questions that can speed up the request:

• What is your hypothesis? What do you expect to find in the data?

  • Hypothesis: users who don't update more likely to not be retained over the next X days.

• What target(s), if any, do we have for these measures? What is the basis of those targets?

  • NA

---

Data Analyst (DA) Section

Questions to be answered by DA upon review:

• What are the questions that this dashboard will be answering?

• Do we have all the tracking in place to capture necessary data to speak to the questions identified?

• If not, write up tickets for tracking events to be added. Also write up follow up tickets for each measure to be added and mark it as blocked until 30 days post-production implementation of tracking events.

  • Then, follow up with requestor and define and prioritize inclusion of alternative proxies while we wait for the tracking to be available.

[bischoffa]

Need Mobile analytics for this. They are still onboarding so will reassess timing when Adam is back from leave to see when Victor may be able to help and prioritize it against the rest of this work

[bischoffa]

After reviewing this is not a Qart specific ticket as Qart is not involved in retention or pushing to have users update the app (flagship strategies). Ticket talks about analytics around retention would be owned by the Flagship part of the program. I am adding Global given Ameet has talked about Retention in the past + talks about notifications.