1145859 - user feedback for tracking protection

Status: RESOLVED WONTFIX

(support.mozilla.org :: General, defect)

Description

[[:mmc] Monica Chew (no longer reading bugmail)]

Hey folks,

We've been using a combination of bugzilla and a google doc (currently at http://trackingprotection.info) to keep track of breakages for tracking protection: https://support.mozilla.org/en-US/kb/tracking-protection-firefox?as=u&utm_source=inproduct

Is there a more formal way to do this? It would be great to have a link that's usable in-product where everyone who's interested can submit and read feedback on this particular feature.

Thanks,
Monica

Comment 1

[Matt Grimes [:Matt_G]]

Hey Monica. We can absolutely help out here. There are a lot of options for you. We can create custom surveys if you want really detailed information or to ask specific questions. If you'd prefer to let it be organic feedback we can create a new product in Input for you. You can either direct people to input with a custom URL or there's the input API that will let you handle the form on your end.

Happy to help. Let me know!

Comment 2

[[:mmc] Monica Chew (no longer reading bugmail)]

Yay, that sounds awesome! Would it makes sense to have 2 things?

1) Organic feedback link in Input (we don't have "report feedback" in the chrome anywhere but this might be coming soon)
2) In case the sentiment in 1) is negative, a survey that includes 2 questions:
- What site broke with tracking protection enabled?
- Did disabling protection (link to SUMO article) fix the problem?

Comment 3

[Matt Grimes [:Matt_G]]

Hey Monica. We are happy to do whatever works best for you. Want to set up something for next week so we can talk it through? Please include Cheng in the meeting as well. Thanks!

Comment 4

[François Marier [:francois]]

My notes from the meeting we had last week.

Telemetry:

- could tell us when tracking protection is turned off via the shield
- this could require zero user interaction or we could ask the user if they want to report the problem
- SSL error reporting has something similar, it took 1/2 to 3/4 year to get this shipped
- collecting URLs is not part of telemetry, domains can be

input.mozilla.org:

- idea: if you refresh 3 times in a row with TP on, ask user "is this not working for you, do you want to turn off TP?"
- involves front-end coding, some user interaction
- there's a json API we post to, input.m.o worries about storage for us 
- input visualizations are usually binary
- https://useradvocacy.mozilla.org/dashboards/hello-v1/ is an example of the kinds of dashboards that can be done

suveygizmo: we could have a 3-question survey

- cheap way, but marketing doesn't like us doing that in beta releases
- URLs are not great
- support team can help us design the survey questions
- goals: we want to know both what URLs break and how users feel about TP

heartbeat:

- changing the text for this is easy, as long as we're ok with 5-star rating
- idea: after 10 days of using TP, you have a 1/10 chance of being asked to take the survey
- we could also use the existing heartbeat in Nightly to see the effect of turning TP on by default in PB
- Note: nightly users are busier, they're less likely to report feedback

Comment 5

[François Marier [:francois]]

I think we should start with a survey while we work on the other mechanisms.

Matt: What do you need from us to design a small survey? Should a file a dependent bug with our goals for the survey?

Comment 6

[Matt Grimes [:Matt_G]]

You could send an email to Cheng and cc me on it. I think that would suffice. Please list all of your goals and we can go from there. Thanks!

Comment 7

[sjw]

Actually I can just report 'broken' sites. What about additional trackers that aren't blocked yet?

Comment 8

[François Marier [:francois]]

Disconnect is working on a solution for this on their end.