Page MenuHomePhabricator

Define what user behavior we want to track for image suggestions
Closed, ResolvedPublic

Description

As per T292316, there are several analytics questions we want to answer to determine the success of the image suggestions notifications and to determine whether there are changes we need to make in the future.

The flow we want to track is:

  1. notification -> open notification -> visit page -> edit page -> view suggested images -> insert suggested image -> suggested image possibly reverted
  2. notification -> open notification -> view suggested images -> edit page -> insert suggested image -> suggested image possibly reverted

This ticket is to figure out what's technically possible

  • can we fire events on notification clicks? notification email opens?
  • can we connect a user who opens a notification to the user subsequently editing the page?
  • can we connect a later reversion of the image back into the chain of events?

When we have these questions answered (probably whoever's doing this will need to talk to
@cchen and/or @nettrom_WMF) then findings should be presented back to the team so that we can agree on what we'll track, and modify T292316 based on what's actually possible.

Acceptance Criteria:

  • Documentation to answer the technical questions
  • Update T292316 based on what's possible
  • Create a new ticket to add the instrumentation we need

Event Timeline

SWakiyama renamed this task from [SPIKE] Define what user behaviour we want to track for image suggestions to Define what user behavior we want to track for image suggestions.Sep 30 2021, 7:04 AM
SWakiyama updated the task description. (Show Details)
CBogen added a subscriber: cchen.

Seems to cover pretty much the same stuff, so I think so yeah

@cchen @Cparle Upon closer inspection there are a couple of things in T292316 that I'm not sure are covered by T299667:

  • How many images on average are added by a user per month? (To understand what the current behavior is today and how people engage with images; would help us know if engagement increases based on our work).
  • Number of notifications sent (To get a sense of the scope of our work and whether we should increase or decrease)
  • Number of opt-outs (To see whether users are annoyed by our notifications or not interested in them, etc)

Do we still need this ticket for defining how to track those things? Or are they covered elsewhere?

@CBogen

  • Number of notifications sent (To get a sense of the scope of our work and whether we should increase or decrease)
  • Number of opt-outs (To see whether users are annoyed by our notifications or not interested in them, etc)

we can define how to track those in here T292785

@CBogen

  • Number of notifications sent (To get a sense of the scope of our work and whether we should increase or decrease)
  • Number of opt-outs (To see whether users are annoyed by our notifications or not interested in them, etc)

we can define how to track those in here T292785

@cchen Great, thanks! What about

  • How many images on average are added by a user per month? (To understand what the current behavior is today and how people engage with images; would help us know if engagement increases based on our work).

@cchen Great, thanks! What about

  • How many images on average are added by a user per month? (To understand what the current behavior is today and how people engage with images; would help us know if engagement increases based on our work).

I see this one is to track the current behavior. And not like T291403, there are no previous projects related to this question. Maybe we can create a separate task for this question?

CBogen claimed this task.

I created T300065 for this, and also followed up to see whether it's even possible in Slack. Resolving this ticket :)

@cchen Great, thanks! What about

  • How many images on average are added by a user per month? (To understand what the current behavior is today and how people engage with images; would help us know if engagement increases based on our work).

I see this one is to track the current behavior. And not like T291403, there are no previous projects related to this question. Maybe we can create a separate task for this question?