Closed Bug 1184338 Opened 9 years ago Closed 9 years ago

[userstory] Allow Heartbeat to target Private Browsing Mode users

Categories

(Toolkit :: Telemetry, defect)

Product:
Toolkit
Component:
Telemetry
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: javaun, Unassigned)

References

Details

(Whiteboard: [fxprivacy] [userstory])

User Story

As the Fx team, we need to gather user feedback without compromising user privacy, so we can understand if users find the new PBM with TP on by default to be an improvement over the existing PBM experience.

A.C.
* Survey team can deliver a survey to users in PBM, via Heartbeat
* CONSTRAINT: Only the existing UX options/configurations are available for survey options (aOptions)
* Heartbeat rating (stars) are hidden for users who receive survey prompt in PBM, since a user could click on the "stars" without realizing they would be sending feedback to Mozilla.
* PBM users see an opt-in survey. They have divulged no signal to anyone, including Mozilla, that they are in PBM unless they opt-in. 
* Survey prompt copy is specific to PBM, invites users to take a survey, and that doing so will consent to share information with Mozilla. "Would you like to share feedback with Mozilla? No information will be shared unless you take the survey." [Take Survey]
* Survey prompt offers a link. Clicking the link from PBM launches a survey tailored for PBM or recorded as actual PBM user.
* If a user has both normal and PBM windows open, the tailored survey prompt appears in PBM
Heartbeat must respect PBM and store nothing that would indicate what user did in PBM or that they even opened PBM.
* Heartbeat can store a general state on the local drive that a user has taken *a* survey, so long as this state is exactly the same whether a user took a survey in normal or PBM mode. Since all users in general population are eligible for HB surveys, it is plausible that any saved state for a HB survey resulted from normal mode.
* We may need to do work to make Heartbeat less visible. For example, we need to evaluate whether HB fires event callbacks on things like Survey prompt dismissal ("X")

Attachments

(1 file)

Graphic mockup of HB survey prompt restyled for PBM
86.07 KB, image/png
Details 
As part of the release of Tracking Protection in Private Browsing mode, we want to be able to collect attitudinal/behavioral data from users in a way that is clearly opt-in and preserves their privacy. We want to be able to serve Heartbeat surveys to PBM users to gauge their self-reported interest, frequency of usage, and other qualitative measures.
I reviewed this request with Javaun earlier. I'll still want to see the details for final data review, but I'm ok with this in principle.

I'd like to have somebody do a precise UX design for the way the survey is supposed to be presented to the user.

The potential challenges:
* Notifying heartbeat that the user has opened a private-browsing window. Probably should be done with a custom DOM event.
* Opening a heartbeat survey in the new private-browsing window. I assume this is where you want it. But I don't know whether the current API lets us target a survey at a particular window.

We must not send information back to Mozilla until the user has agreed to take the survey.
We must not track that the user has taken the PB survey through any sort of cookie.
Flags: needinfo?(jmoradi)
Flags: needinfo?(jmoradi) → firefox-backlog?
Whiteboard: [fxprivacy]
Flags: firefox-backlog?
Whiteboard: [fxprivacy] → [fxprivacy] [triage]
Whiteboard: [fxprivacy] [triage] → [fxprivacy] [userstory]
User Story: (updated)
Depends on: 1195971
Depends on: 1196102
Summary: Allow Heartbeat to target Private Browsing Mode users → [userstory] Allow Heartbeat to target Private Browsing Mode users
Depends on: 1196104
Depends on: 1196105
Depends on: 1197659
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: