Event metrics

[maxkfranz]

Description

Q: What is the name of the feature?

A: Event metrics service

Q: What does this feature enable the user to do?

A: Provide implicit feedback

Q: What information must the user provide to use the feature?

A: Just use the interface

Q: What are the applicable constraints, e.g. compatibility or performance?

A: Must be a server-driven API

Q: How does this feature affect each class of user (persona)?

A:

• Biologist: Provide implicit feedback for which features are best
• Editor: "
• Computational biologist: "
• Curator: "

Specification

Mockup

• A user performs event X, which is something that is valuable for us to know w.r.t. design.
• Action X is logged.

Details

• Provide an endpoint, e.g. /api/event, that we POST to for relevant events.
• The payload should be enough for the server to send a request for this:
  • Docs: https://developers.google.com/analytics/devguides/collection/protocol/v1
  • Request: https://developers.google.com/analytics/devguides/collection/protocol/v1/devguide
  • Params: https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters
  • Note: May need some sort of anonymous user ID depending on what we want to measure

[jvwong]

Looking at what this might entail:

• Client
  • general data
    • client ID (UUID)
  • type: event
    • category (String, e.g. 'video')
    • action (String, e.g. 'play')
    • label (String, e.g. 'holiday')
    • value (Int, e.g. '300')
• Server
  • id (uuid) via cookie-session

[jvwong]

Universal Analytics will be going away

[jvwong]

• TODO
  • Bug in Chromium install for Docker
  • Get GTM code into production
  • *Consider events to track

• straightforward video on event tracking with Google Tag Manager

[jvwong]

Events to track (many are already tracked by GTM)

• Click CTA
• Search terms
• Access to the article