Closed Bug 1186032 Opened 4 years ago Closed 4 years ago

Add telemetry probes to first app run

Categories

(Firefox for Android :: General, defect)

defect
Not set

Tracking

()

RESOLVED INVALID
Tracking Status
firefox42 --- affected

People

(Reporter: barbara, Unassigned)

References

(Blocks 1 open bug)

Details

Add telemetry probes (if not already there?) on how many people use the import function on first app run

We probably have to add two snippets of code
a) to track first app run carousel
b) to track once a user clicks the CTA button to import (or more general once a user uses the import functionality)
c) Can we measure the funnel, i.e. drop off rate after slide 1?

I've poked around Telemetry UI and found this event, could you please confirm if/what that does edit.1->settings->android.not_a_preference.import_android. Is this covering b)?
(In reply to Barbara Bermes [:bbermes] from comment #0)

> I've poked around Telemetry UI and found this event, could you please
> confirm if/what that does
> edit.1->settings->android.not_a_preference.import_android. Is this covering
> b)?

No. That probe is only tracking the Setting > Customize > Import action.

For the current CTAs, look at the UI Telemetry for Firstrun:
action.1->button->firstrun-browse
action.1->button->firstrun-sync

We also track cancelling out of the firstrun pane:
cancel.1->actionbar->firstrun-pane
cancel.1->back->firstrun-pane
cancel.1->dialog->firstrun-pane
I'll be sure to add these probes. I'm not sure what you mean by "track first app run carousel" - what action is the user taking that we want to track?

We can definitely measure clicks on the CTA button, and I can measure each screen the user has made it to. Since we know the user will make it to the first screen, it can be the baseline and we can calculate dropoff by comparing the numbers each first run screen has.
We've added probes into firstrun in various other bugs and versions, so closing this bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.