Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Telemetry] CFR message about Enhanced Tracking Protection panel #9625

Closed
AmyYLee opened this issue Apr 2, 2020 · 10 comments
Closed

[Telemetry] CFR message about Enhanced Tracking Protection panel #9625

AmyYLee opened this issue Apr 2, 2020 · 10 comments
Assignees
Labels
E2 Estimation Point: easy, half a day to 2 days eng:qa:verified QA Verified Feature:Telemetry Feature:TrackingProtection P1 Current sprint

Comments

@AmyYLee
Copy link
Collaborator

AmyYLee commented Apr 2, 2020

Description/User Story

As a UX feature owner, I’d like to measure the effectiveness of CFR messaging in relation to user engagement with the Enhanced Tracking Protection panel in Fenix

What questions will you answer with this data?

  • How many users tap on the shield icon to open the ETP panel right away after seeing the CFR message
  • How many users tap “x” to close the CFR message and not open the ETP panel
  • How many users tap on the shield icon to open the ETP panel without seeing the CFR message
  • How many users tap “x” to close the CFR message and open the panel after 24hrs or more
  • How many users tap on the shield icon to open the ETP panel without seeing the CFR message

What probes (suggested, if applicable)

    1. An event that’s fired when the CFR message is displayed
    1. An event for tapping “x” to close CFR message
    1. An event for when the shield icon is tapped - I think we already have this (tracking_protection.etp_shield).

Dependencies

Accurate data is dependent on this issue being fixed:
Contextual Feature Recommender disappears right away while scrolling #7387

Acceptance Criteria

  • Event pings can be queried via re:dash
  • We are sending telemetry events for the actions listed in the requirements
  • We have asked a data steward to review the telemetry
  • When the above questions are answered

┆Issue is synchronized with this Jira Task

@AmyYLee
Copy link
Collaborator Author

AmyYLee commented Apr 2, 2020

@vesta0 for visibility

@vesta0
Copy link
Collaborator

vesta0 commented Apr 5, 2020

For dev: please fill out the methodology section here.

@vesta0 vesta0 added needs:group-triage and removed needs:triage Issue needs triage labels Apr 5, 2020
@vesta0 vesta0 added this to Prioritized Feature Backlog in Fenix Sprint Kanban Apr 5, 2020
@boek boek moved this from Prioritized Feature Backlog to In Progress in Fenix Sprint Kanban Apr 7, 2020
@sblatz
Copy link
Contributor

sblatz commented Apr 7, 2020

I am working on making these CFR messages generic (ui components). Would be nice to include telemetry generically in those so we always get it for each message (with some ID to identify which CFR it actually is). Would that work for you @vesta0?

@vesta0
Copy link
Collaborator

vesta0 commented Apr 8, 2020

That would be amazing @sblatz 👍

@vesta0 vesta0 added this to Telemetry & User engagement in Fenix Q2 Feature Backlog Apr 9, 2020
@liuche liuche added the 🙅 waiting Issues that are blocked or has dependencies that are not ready label Apr 13, 2020
@vesta0 vesta0 removed this from Measure user engagement in Fenix Q2 Feature Backlog Apr 26, 2020
@vesta0 vesta0 added this to Waiting for DS in Feature engagement Apr 26, 2020
@vesta0
Copy link
Collaborator

vesta0 commented Apr 28, 2020

Next step is to create a JIRA request outlining the Dev proposal for DS review.

@sblatz sblatz added needs:data-science and removed 🙅 waiting Issues that are blocked or has dependencies that are not ready labels May 1, 2020
@vesta0 vesta0 removed this from In Progress in Fenix Sprint Kanban May 7, 2020
@vesta0 vesta0 added this to Q2: Fenix in Fenix Product Backlog May 12, 2020
@vesta0 vesta0 removed this from Q2: Fenix in Fenix Product Backlog May 12, 2020
@vesta0 vesta0 added the P1 Current sprint label May 29, 2020
@betsymi
Copy link

betsymi commented Jun 3, 2020

Would like to add 2 more request for telemetry:

  1. Measure when users tap on CFR bubble
  2. Measure when users tap outside the CFR message upon it appearing.

@sblatz
Copy link
Contributor

sblatz commented Jun 3, 2020

Jira ticket filed with high (P1) priority.

@sblatz sblatz added E2 Estimation Point: easy, half a day to 2 days 🙅 waiting Issues that are blocked or has dependencies that are not ready labels Jun 3, 2020
@sblatz sblatz added this to In Progress in Fenix Sprint Kanban Jun 3, 2020
@sblatz sblatz removed the 🙅 waiting Issues that are blocked or has dependencies that are not ready label Jun 15, 2020
@sblatz
Copy link
Contributor

sblatz commented Jun 15, 2020

Marissa approved 😄

@sblatz
Copy link
Contributor

sblatz commented Jun 15, 2020

Notes

onboarding.order#.xxx, where xxx matches the other preference telemetry name
Use “onboarding” as the top most naming convention
Onboarding.whats_new_clicked
order# refers to the order on the screen
Events for
Onboarding finished (search or enter address && start browsing)
Onboarding started
Useful to track position in the list

@sblatz sblatz moved this from Waiting for DS to Backlog in Feature engagement Jun 16, 2020
@sblatz sblatz moved this from Backlog to Eng Ready in Feature engagement Jun 16, 2020
@sblatz sblatz moved this from In Progress to In Dev Review in Fenix Sprint Kanban Jun 25, 2020
@sblatz sblatz added the eng:qa:needed QA Needed label Jun 25, 2020
@sblatz sblatz moved this from Eng Ready to In progress in Feature engagement Jun 25, 2020
@sblatz sblatz moved this from In Dev Review to Ready for QA in Fenix Sprint Kanban Jun 26, 2020
@liuche liuche mentioned this issue Jun 27, 2020
12 tasks
@AndiAJ
Copy link
Collaborator

AndiAJ commented Jun 30, 2020

Hi, verified as fixed on both Nightly Build 200629 from 6/30 and Fenix 79.0.1-beta.1 from 6/30 using a Google Pixel 3a (Android 10)

✔️ The enhanced tracking protection contextual hint was displayed
Nightly Ping d8cf4360-f336-4cf1-80ff-8e1e6449464b
Beta Ping c55839b6-edb9-4d3d-bad2-b1c1540ff65b

"category": "contextual_hint.tracking_protection",
         "name": "display"

✔️ The user tapped outside of the etp contextual hint -
Nightly Ping 1f6feec1-499a-4c94-ba94-ed1ad5a61809
Beta Ping 0182157a-8bb2-42e2-aac7-68913ccb57bc

"events": [
        {
          "category": "contextual_hint.tracking_protection",
          "name": "outside_tap"

✔️ The user tapped inside of the ETP contextual hint (which brings up the etp panel for this site) -
Nightly Ping 46c09f49-e181-4fcd-a8e4-aec037caf0e5
Beta Ping 37fe8035-4b5b-455a-918a-56773655a227

 "events": [
        {
          "category": "contextual_hint.tracking_protection",
          "name": "inside_tap"

✔️ The shield icon is tapped -
Nightly Ping 1fba4c85-9f43-4e0f-8095-3ee02759fd11
Beta Ping dd05044f-673e-449b-bfb6-5fd294468782

"events": [
        {
          "category": "tracking_protection",
          "name": "etp_shield"

✔️ The enhanced tracking protection contextual hint was dismissed by pressing the close button
Nightly Ping 54e1d23a-837b-4977-b68c-b56876926e16
Beta Ping fa9efbdf-92a5-400d-a539-14a603dccb46

events": [
        {
          "category": "contextual_hint.tracking_protection",
          "name": "dismiss"

► Nightly
Logcat
Glean dashboard

Logcat
Glean dashboard

► Beta
Logcat
Glean dashboard

Logcat
Glean dashboard

@AndiAJ AndiAJ closed this as completed Jun 30, 2020
Fenix Sprint Kanban automation moved this from Ready for QA to Sprint 20.11 Done Jun 30, 2020
@AndiAJ AndiAJ added eng:qa:verified QA Verified and removed eng:qa:needed QA Needed labels Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E2 Estimation Point: easy, half a day to 2 days eng:qa:verified QA Verified Feature:Telemetry Feature:TrackingProtection P1 Current sprint
Projects
Fenix Sprint Kanban
  
Sprint 20.11 Done
Feature engagement
  
In progress
Development

No branches or pull requests

7 participants