Page MenuHomePhabricator

[EPIC] Community updates module: instrumentation & measurement (SDS 2.1.3)
Open, Needs TriagePublic

Description

User story:

As the Growth team, I want to be sure we consider instrumentation & measurement for every feature we release, because we only want to scale out features that improve new editor onboarding and retention.

Parent task: T360485: [EPIC] Newcomer homepage: Community updates module (FY23/24 WE1.3 / FY24/25 SDS2.1.3)

SDS 2.1.3: If the Growth team learns about the Metrics Platform by instrumenting a Homepage Module on the Metrics Platform, then we will be prepared to outline a measurement plan in Q1 and complete an A/B test on the new Metrics platform by the end of Q2.

Designs:

Community updates: Figma designs for Homepage module.

Community updates: Figma designs for the configuration form.

Key Question:

Does this module encourage more newcomers to participate in community events / campaigns / projects?

What we will measure as part of the A/B test:
  • Awareness: Total individual page views; how many account holders visited their Homepage while this feature was visible. (SDS 2.2.3: Clickthrough rate)
  • Consideration: Total Click Through Rate (SDS 2.2.3: Clickthrough rate)
  • Conversion: After click through, registration for event / program; Do more newcomers sign up for the WikiProject or Campaign when they are exposed to the Community Updates CTA on the Homepage? (SDS 2.2.2: conversion metric)
What we would like to measure, but may not be able to based on current limitations:

If possible, we should also measure the following metrics:

  • Constructive Activation: Are newly registered account holders who visited the Newcomer homepage and had access to this new feature more or less likely to activate?
  • Completion rate for Suggested Edits: Are newly registered account holders who visited the Newcomer homepage and had access to this new feature more or less likely to complete Suggested Edits?
  • Completion rate for asking a question to a Mentor: Are newly registered account holders who visited the Newcomer homepage and had access to this new feature more or less likely to connect with their Mentor?
  • Editor Retention: Are account holders who saw this new feature more or less likely to be retained?
NOTE: Page load performance & Page load error rates should be monitored separately, and not considered part of this task.
Measurement & Instrumentation details:

From the measurement specification.

Similar to other home page modules the following events will be captured:

  • Impressions
    • For these events we will capture the current update with a friendly name
  • Clicks on the call to action
    • For these events we will capture the current update with a friendly name
Acceptance Criteria:

TBD

Related Objects

StatusSubtypeAssignedTask
OpenKStoller-WMF
OpenNone
ResolvedSgs
ResolvedSgs
ResolvedSgs
ResolvedSgs
ResolvedCyndymediawiksim
ResolvedSgs
ResolvedEtonkovidova
DuplicateNone
Resolvednettrom_WMF
ResolvedCyndymediawiksim
ResolvedCyndymediawiksim
Duplicatenettrom_WMF
Resolvednettrom_WMF
Resolvednettrom_WMF
ResolvedSgs
StalledSgs
ResolvedCyndymediawiksim
OpenCyndymediawiksim

Event Timeline

KStoller-WMF moved this task from Up Next to Backlog on the Growth-Team board.
KStoller-WMF renamed this task from Community updates module: instrumentation & measurement to [EPIC] Community updates module: instrumentation & measurement (SDS 2.1.3).Jul 10 2024, 10:12 PM
KStoller-WMF updated the task description. (Show Details)

In early conversations with @DMburugu and @KStoller-WMF, we agreed that aside from the new Metrics Platform instruments, we would also add "legacy" instrumentation through the EventPlatform as the rest of homepage modules so we could compare results. Does this make sense to you @nettrom_WMF ? If so, we need to add a new module, community-updates in the module enumeration. Is there any other data that would be relevant to capture here as action data? eg: the title of the community update

In early conversations with @DMburugu and @KStoller-WMF, we agreed that aside from the new Metrics Platform instruments, we would also add "legacy" instrumentation through the EventPlatform as the rest of homepage modules so we could compare results. Does this make sense to you @nettrom_WMF ? If so, we need to add a new module, community-updates in the module enumeration. Is there any other data that would be relevant to capture here as action data? eg: the title of the community update

  1. Yes, it makes sense to me that we also instrument through HomepageModule. It's come up in discussions that having that data available for comparison purposes would be useful.
  1. Adding community-updates to the module enumeration also makes perfect sense.
  1. I'd love to have either the title or some symbolic name available so that it's easy to identify what specific Community Update was shown to the user. Here I defer to you as engineers as to what is readily available to use, if it's the title I'm fine with that! I'm also making a mental note of this as I'm sure we'll have to figure something out when we're looking at the Metrics Platform instrumentation for this, since custom data isn't available there.
  1. What values will action have for the events associated with this module? Maybe it would be impression and link-click, since the module is basically just a link to another page? I don't think we need a cu-* prefix (or something like that), but if you'd like to have that I'm fine with it.

Those were the thoughts I had so far.