Analytics (update): Add tracking to account for filter functionality change

[signechambers1]

Overview

Tool: Gene Expression
Feature: Filters

Description: Users can now use the Dataset, Sex, Disease and Ethnicity filters prior to selecting a Tissue or Gene. We'd like to know:

1. Are more visitors filtering before getting to a heat map or after?
2. Is there a specific filter that is more useful to use before vs. after or after vs. before getting to a heat map?

Updates needed

• Requested change:
  ~ * includes all of the filters, DATASET, DISEASE, ETHNICITY, SEX
  FILTER_SELECT_* ~ to fire when a user selects a filter and there is no heat map loaded yet
  FILTER_SELECT_*_BEFORE_HEATMAP ~ to fire when a user gets to a loaded heat map and a filter is already selected
  FILTER_SELECT_*_AFTER_HEATMAP ~ to fire when a user gets to a loaded heat map and then selects a filter

Checklist

• Once event updates are deployed to Staging ping @ainfeld to check analytics
• Verify events are showing up in the Staging space in Plausible correctly
• Once event updates are deployed to Prod ping @ainfeld
• Confirm Plausible events are still showing up in the Prod space in Plausible correctly

People to cc

PM: @signechambers1
DS: @ainfeld

Privacy policy: https://cellxgene.cziscience.com/privacy

NOTES:

1. Draft PR for future reference: feat(wmg): Filter Analytics #5106

[ashin-czi]

@signechambers1

For FILTER_SELECT_*, we're already sending this event for when a user selects a filter, and we send the name of the filter selected

Did you want to send the names of the selected filters as well for FILTER_SELECT_*_BEFORE_HEATMAP and FILTER_SELECT_*_AFTER_HEATMAP? Or just the event with no data?

Should we rename FILTER_SELECT_* to FILTER_SELECT_*_NO_HEATMAP?

[signechambers1]

@ashin-czi I'd like to send the names of the filters too please!

Not sure I understand the renaming question, I think any filter selection will be either BEFORE_HEATMAP or AFTER_HEATMAP, so there is no need for a NO_HEATMAP option?

[tihuan]

@signechambers1 @dsadgat I might be able to work on this on Thursday if SEO work goes well this week. Will keep you posted!

[tihuan]

@signechambers1 not sure who added this, but in Updates needed section in the ticket there are three events!

1. FILTER_SELECT_* ~ to fire when a user selects a filter and there is no heat map loaded yet
2. FILTER_SELECT_*_BEFORE_HEATMAP ~ to fire when a user gets to a loaded heat map and a filter is already selected
3. FILTER_SELECT_*_AFTER_HEATMAP ~ to fire when a user gets to a loaded heat map and then selects a filter

It feels like the intention is to take share link into account in the #2 event, so the scenarios below can distinguish all three different filters?

1. User lands on GE
2. User selects filter A -> FILTER_SELECT_A fires
3. User selects a gene -> heatmap now renders -> FILTER_SELECT_A_BEFORE_HEATMAP fires (do we need this event? Feels a little redundant)
4. User selects filter B -> FILTER_SELECT_B_AFTER_HEATMAP fires
5. User shares link with UserB
6. UserB uses the share link and lands on GE with filter A and B selected already and heatmap loaded -> FILTER_SELECT_A_BEFORE_HEATMAP AND FILTER_SELECT_B_BEFORE_HEATMAP fire (Per @ainfeld , this is not ideal, since we don't want share link to skew the data. But since we don't have many share link entries, it's okay to not solve this right now)

Is that right?

[signechambers1]

@tihuan you are right FILTER_SELECT_* and FILTER_SELECT_*_BEFORE_HEATMAP feel redundant. @ainfeld i think we might just be able to use one of them, do you agree?

[tihuan]

@signechambers1 @ainfeld and I sync'd offline with the following notes:

1. FILTER_SELECT_* is to capture user's filter selection BEFORE a heatmap is loaded
2. FILTER_SELECT_*_BEFORE_HEATMAP is to capture filters selected AT THE TIME a heatmap is loaded
3. FILTER_SELECT_*_AFTER_HEATMAP is to capture additional filters selected AFTER a heatmap is loaded

We also decided that we can leave this in the back burner for now!

[signechambers1]

Discussed with @ainfeld and @tihuan, we are going to deprioritize this now and reprioritize later if we want to. Product questions would be better served by qualitative research right now.

[tihuan]

@signechambers1 I moved this back to "Disorder" and removed the "P1" label!

[tihuan]

For completeness: Signe and Amanda don’t see practical business value to track extra analytics for now, so we decided not to spend eng resource on this until we see stronger needs!