search

18F / analytics-standards

WIP: Team standards for implementing website and API analytics.
Other
9 stars 12 forks source link

brainstorm analytics needs over a project's lifetime #14

Open gbinal opened 9 years ago

gbinal commented 9 years ago

E.g.

gbinal commented 9 years ago

To clarify - across the lifetime of a project, what are common questions/needs.

jackiekazil commented 9 years ago

Notes from MyRA customer meeting for lifecycle discussion: https://docs.google.com/document/d/1GSGx6KsnBPGaIdsuhH2AIP-XKWlug0cxuQXaoSeVxeE/edit#

jackiekazil commented 9 years ago

I ended up writing up off boarding options. Here is what I came up with based on the MyRA conversation. Not sure where is the best place to put it, so I am going to drop it in this ticket. Suggestions?

Off boarding analytics

When the IAA with 18f is complete, there are the options of what could happen after the official relationship between 18F and our agency partners is complete.

  1. The project can move off of 18F analytics and just have DAP. Because all the projects for an agency are together the project team from the agency can work directly with DAP to figure out how to distinguish their project.
    • (+) The project only worry about one set of analytics; less layers of complexity
    • (-) The project is not as isolated in the summary display, so analytics will require a little bit bit of digging to understand, but there are ways to filter.
  2. The project can move off of 18F analytics and start their own analytics account. This gives them complete control of their analytics without restriction. DAP would still need to be implemented.
    • (+) Project is not dependent on 18F -- project owners on the agency side manage access and implementation
    • (+) The project data is distinguished easily from other projects
    • (+) Complete control by the project allows for customizations such as Google tag manager.
    • (-) The project does not have 18F support unless contracted
    • (-) There is no way to transfer the analytics directly to another account. There will be a gap in a data when the switch happens, so it is recommended that you run both the 18F account and their own at the same time for a couple of months.
  3. The project can stay on 18F analytics without support as long as 18F analytics is able to provide them the space in their instance.
    • (+) This provides a separate instance from DAP that the project team will have control and responsibility over.
    • (+) There is no interruption in analytics on the account.
    • (+) Complete control by the project allows for customizations such as Google tag manager.
    • (-) 18F will provide the space for free as long as 18F is able. 18F will provide notice when it is unable.
    • (-) 18F will only provide support as it relates to the 18F account as a whole.