Bug 1608461 Comment 35 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
What does Data prefer to store and analyze the information here, or is it the same for you?
  1. one scalar with keys like `${uniquename}-shown_count`, `${uniquename}-help_picked`, `${uniquename}-button_picked`
  2. one scalar for tips, one scalar for interventions with keys like `${name}-shown_count`, `${name}-help_picked`, `${name}-button_picked`
  3. one scalar for tips shown count, one scalar for interventions shown count, one scalar for interventions button picked, one scalar for interventions help picked (current approach)
Revision 1 by
on 
What format does Data prefer, to store and analyze the information (or is it the same for you)?
  1. one scalar with keys like `${uniquename}-shown_count`, `${uniquename}-help_picked`, `${uniquename}-button_picked`
  2. one scalar for tips, one scalar for interventions with keys like `${name}-shown_count`, `${name}-help_picked`, `${name}-button_picked`
  3. one scalar for tips shown count, one scalar for interventions shown count, one scalar for interventions button picked, one scalar for interventions help picked (current approach)
Revision 2 by
on 
What format does Data prefer, to store and analyze the information (or is it the same for you)?
  1. one scalar with keys like `${uniquename}-shown_count`, `${uniquename}-help_picked`, `${uniquename}-button_picked`
  2. one scalar for tips, one scalar for interventions with keys like `${name}-shown_count`, `${name}-help_picked`, `${name}-button_picked`
  3. one scalar for tips shown count, one scalar for interventions shown count, one scalar for interventions button picked, one scalar for interventions help picked (current approach, we won't count button picked on tips though)

Back to Bug 1608461 Comment 35