Skip to content

Think about ways to provide API access to DAP data to DAP users #12

@sanason

Description

@sanason

A DAP customer from FedRamp came up these ideas for how to use such an API:

  • Programmatically connect with other data sources such as contract award data (sams.gov); data is more useful for insights if you can link them together!
    • As a byproduct of this, ability to create custom dashboards specific to program needs and not just scoped to web analytics
      • E.g. "As a program director, I want an biannual report that overlays critical milestones and deadlines over web traffic to X website, so I can make strategic decisions when it comes time for my program's mid-year and end-of-year auditing/performance review."
    • While we can already export GA data, if programs want to move towards continuous monitoring and operationalizing their data, then API access is crucial. Proactive, early, and incremental change is a risk avoidance strategy. If data can signal to programs they are deviating from mission goals early on, then we can course correct to avoid hitting the iceberg and hence do cost avoidance.
  • Ability to use other LLM models other than what's built into GA to "talk" to the data for reporting and discovery by leadership
    • Maybe done through Retrieval-augmented generation or Model Context Protocol
  • For site reliability engineers, create an notification or alerting system when there is high traffic (or low traffic) towards a specific endpoint to signal a response
    • Like say if web traffic hits 50% below the baseline, we would kick off an automated workflow that sends an email blast to internal stakeholders so we can check for security vulnerabilities, threats, or service downtime and execute on a remediation plan
  • For user researchers or service designers, track custom events and user behavior through a web app, especially when trying to test against a hypothesis to ultimately improve user experience
    • This can tie into A/B testing platforms where one set of users have access to a feature an another doesn't; API access allows for more granular control of the data so we know how one set of users navigate through a web app vs. another

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions