Closed Bug 1547410 Opened 6 years ago Closed 6 years ago

Identification of Success Metrics and Data Analysis for Project Trailhead

Categories

(Data Science :: Experiment Collaboration, task)

x86_64
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: julie, Assigned: loines)

Details

Brief Description of the request (required): Need help in identifying, collecting, analyzing success metrics in support of Project Trailhead. In addition to a new onboarding flow for 99% of users to be deployed June 4th, we will launch an experiment that ‘holds back’ 1% and splits that population so that:

  • Variant 1 • Control: one third see the existing FxA CTA (control) version of about:welcome and onboarding tour with new messaging
  • Variant 2: one third see a “Join Firefox” CTA version of about:welcome and onboarding tour with new messaging
  • Variant 3: one third will bypass the about:welcome CTA and go directly to the onboarding tour with new messaging

Business purpose for this request (required):

This is in support of Marketing's Trailhead initiative.

Requested timelines for the request or how this fits into roadmaps or critical decisions (required):

now through June and most likely through the end of the year, as another version of "Trailhead" will launch in October.

Links to any assets (e.g Start of a PHD, BRD; any document that helps describe the project):

Trailhead user experience requirements: https://docs.google.com/document/d/17_lBxX5ooygyhPUTBgELlJXeqeluPwCAjS8edCWKqI0/edit
Trailhead PRD: https://docs.google.com/document/d/1I_gEnuuzNcDO_8XEWeD9H2yNPX6OrtbC4kz74LEidJQ/edit#
Note: These docs are still being updated (as of April 25th)

Name of Data Scientist (If Applicable):Leif Oines

Please note if it is found that not enough information has been given this will delay the triage of this request.

Assignee: nobody → loines
Status: NEW → ASSIGNED

helping out data analytics on this - doc here.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.