Discovery: Identify next set of metrics for visualization on analytics board

[vickyszuchin]

Issue description

Identify next set of metrics for visualization on analytics board per Product's needs.

Metrics for considerations (per discussion in product huddle):

• Domains missing DNS info ( statuses of DNS_needed, Unknown) (easy add, by Q: do we want an excel download of the list too? and do we really need to show this over time like the other tables or do we want to just show the current state as this will naturally fluctuate based on approved applications in a time frame)
• Expired domains (aka Delinquent domains ) (same questions as above) ~- Zone growth, covered in project growth (crossed out as the section at the bottom covers this~
• Submitted requests numerical total should show next to the current total of approved requests.
• Show graph of total requests submitted vs graph of approved
• Pie chart displaying domains by organization type( should show as percentage out of total). Refinement Q: include unknown domains?
• Project growth (project management and projection)
  • Non-fed domain count and percent of non-fed domains out of the total domains (Refinement Q: include anything that is not deleted? Even unknown)
  • Fed domain count and and percent of these fed domains out of the total domains
  • % growth (per year or quarter) -Refinement Q: should this just be for the quarter?
• Clickthru data. Can we tell how many users have clicked on the "Contact Us" link from, for example, get.gov vs manage.get.gov. (This type of metric helps us determine the impact of tying a certain feature to a user action) [from 5/1/24 new triage, and issue #2011]

Acceptance criteria

• [ ] Add/update key metrics spreadsheet per Product's needs
• [ ] Select the metrics that hold priority for visualization on the analytic board (mark as Priority 2)
• [ ] Create dev ticket(s) for implementation

Additional context

Key metrics spreadsheet Product huddle notes on 4/17/2024

Links to other issues

Related to: #1320 and #1789

[abroddrick]

@vickyszuchin I don't think this should be a discovery ticket really, I think we should just have a meeting to go over what is listed really quick ( or just use the refinement meeting) and then pick the next item to be done. The one ticket idea was just so the one ticket could be broken into multiple when we are in refinement and we can determine priority then.

[PaulKuykendall]

at today's New triage - discuss this in Refinement 4/29 and decide how we might prioritize this.