You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Our current analytics on ddot.info are fairly minimal (mostly limited to number of users and which page they're visiting). Ideally, we'd like to be able to perform some more involved UX analytics to ensure people are finding what they want to find on ddot.info. For example, see some ideas in CityOfDetroit/detroitmi#1280.
Describe the solution you'd like
A couple options would be:
G4A - pretty minimal and would not allow us to perform the involved analysis we would want in CityOfDetroit/detroitmi#1280
New Relic agent - much more control and can support the requirements in CityOfDetroit/detroitmi#1280, but will take more effort for us to instrument in ddot.info and consume the data in DSA warehouse
For now, we'll update ddot.info to use G4A for some baseline metrics and exploration. In the next couple of months, we'll come back and add custom instrumentation using new relic.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Our current analytics on ddot.info are fairly minimal (mostly limited to number of users and which page they're visiting). Ideally, we'd like to be able to perform some more involved UX analytics to ensure people are finding what they want to find on ddot.info. For example, see some ideas in CityOfDetroit/detroitmi#1280.
Describe the solution you'd like
A couple options would be:
For now, we'll update ddot.info to use G4A for some baseline metrics and exploration. In the next couple of months, we'll come back and add custom instrumentation using new relic.
The text was updated successfully, but these errors were encountered: