Closed Bug 1553933 Opened 6 years ago Closed 5 years ago

Opt-out of Sponsored Content = Data Delete

Categories

(Firefox :: New Tab Page, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
Firefox 69
Iteration:
69.3 - Jun 10 - 23
Tracking Status
firefox69 --- verified

People

(Reporter: jdavis, Assigned: thecount)

References

Details

(Keywords: github-merged)

Attachments

(2 files)

Need ability for user to opt-out and request deletion of SPOC info associated with their ID.

Hey Wolasi! We'll need some UX design options around this before our next mtg with Legal on 6/6.

Assignee: nobody → wkonu
Iteration: --- → 69.2 - May 27 - Jun 9
Flags: needinfo?(wkonu)
Priority: -- → P1
Assignee: wkonu → sdowne
Depends on: 1557404
Summary: Adzerk Preference UI update → Opt-out of Sponsored Content = Data Delete
Flags: needinfo?(wkonu)
Iteration: 69.2 - May 27 - Jun 9 → 69.3 - Jun 10 - 23

Just had a quick review with Alicia (per Legal mtg notes last week) and want to verify that if someone unchecks "Recommended by Pocket" the "Sponsored Stories" will also uncheck (and thereby delete the associated data too).

Scott, can you confirm that this behavior can/will happen?

Making sure Tawanda & Wolasi see this too.

Thanks!

Data Deletion UX
Ad data should get deleted for these two actions

  1. unchecking Recommended by Pocket regardless of if Sponsored Stories is checked or unchecked
  2. when unchecking sponsored stories

Additional UX
When Recommended by Pocket the Sponsored Stories checkbox and label should be disabled. See Spec for reference
https://www.figma.com/file/V4p40RBBtp1939AxwqAFyWTe/New-Tab-Spec-for-Fx-v69?node-id=202%3A0

This adds up with my understanding too.

Alicia, can you confirm you're okay with this UX treatment?

(In reply to Wolasi :wolasi from comment #4)

Data Deletion UX
Ad data should get deleted for these two actions

  1. unchecking Recommended by Pocket regardless of if Sponsored Stories is checked or unchecked
  2. when unchecking sponsored stories

Additional UX
When Recommended by Pocket the Sponsored Stories checkbox and label should be disabled. See Spec for reference
https://www.figma.com/file/V4p40RBBtp1939AxwqAFyWTe/New-Tab-Spec-for-Fx-v69?node-id=202%3A0

Flags: needinfo?(agray)

(In reply to Jessilyn Davis from comment #6)

Alicia, can you confirm you're okay with this UX treatment?

(In reply to Wolasi :wolasi from comment #4)

Data Deletion UX
Ad data should get deleted for these two actions

  1. unchecking Recommended by Pocket regardless of if Sponsored Stories is checked or unchecked
  2. when unchecking sponsored stories

Additional UX
When Recommended by Pocket the Sponsored Stories checkbox and label should be disabled. See Spec for reference
https://www.figma.com/file/V4p40RBBtp1939AxwqAFyWTe/New-Tab-Spec-for-Fx-v69?node-id=202%3A0

Hi Jess,
Yes, I can confirm this meets the technical requirements for the deletion flag in the different scenarios and is approved.

I would suggest taking a look at the UX design for the very last scenario in the Figma image mockup. This greys out a marked "Sponsored Content" checkbox when the user unchecks the "Recommended by Pocket", but leaves the checkbox marked. I can see this leading to user confusion when they can't uncheck the "Sponsored Content" box. They will think that they get Sponsored Content and we aren't allowing them to opt-out/delete their data. While we can write around this in an FAQ, it's a lot of explanatory language with if this/then that. If there is a way to make this clearer in the design, that would be very helpful.

Flags: needinfo?(agray)

I agree with Alicia's suggestion here, if we can show the Sponsored Content box as unchecked that would remove the need for additional language and make it easier for users to see when their preferences have been updated.

That sounds reasonable to me. What should happen with the Sponsored Stories checkbox in the following scenario

  1. User unchecks Recommended by Pocket checkbox (Sponsored Stories automatically unchecked)
  2. Later user checks Recommended by Pocket checkbox

Should Sponsored Stories be checked automatically?

Flags: needinfo?(tkanhema)
Flags: needinfo?(agray)

Suggested Implementation:

User unchecks Recommended by Pocket checkbox (Sponsored Stories automatically unchecked)
Later user checks Recommended by Pocket checkbox (Sponsored Stories checked)

It's safe to assume that a user checking Recommended by Pocket for a second time understands that this comes with Sponsored Content and it's not too much work unchecking that box individually if they do not want to see Sponsored Stories.

Flags: needinfo?(tkanhema)

There is already familiarity in the user settings in firefox that when a checkbox is selected off, any dependant checkboxes are left checked on, but greyed out.

I think it is important to keep this constant across the whole browser.

I also suspect if we are to change this pattern, we would need to run it by the UX team, as they have likely done research around this already and come to the conclusion of greying it out but keeping it checked.

I'll include a screen shot of how this looks in the existing settings.

Attached image chekcs.png

So, I just noticed while doing one or other of these solutions, there is also another checkbox in the config that's de selecting. So this is already not constant across the whole browser, so we can probably do either or, so I'll work with de selecting it and disabling it.

(In reply to Tawanda Kanhema from comment #11)

Suggested Implementation:

User unchecks Recommended by Pocket checkbox (Sponsored Stories automatically unchecked)
Later user checks Recommended by Pocket checkbox (Sponsored Stories checked)

It's safe to assume that a user checking Recommended by Pocket for a second time understands that this comes with Sponsored Content and it's not too much work unchecking that box individually if they do not want to see Sponsored Stories.

Agreed; I think this is fine.

Flags: needinfo?(agray)

Thanks Alicia - It seems the UX team has done some research around the greyed out dependent check box and concluded that users understand it to mean that their preference has been updated. Understandably, both approaches (unchecked & greyed out and checked) are used across the browser, which is a little confusing. Are you okay with us proceeding with the current implementation as is in this development cycle?

Flags: needinfo?(agray)

Alicia is okay with our current implementation:

(In reply to Alicia Gray from comment #8)

Hi Jess,
Yes, I can confirm this meets the technical requirements for the deletion flag in the different scenarios and is approved.

I'm creating a new bug (Bug 1559143) to track the UX update to change the current "grayed out and checked" scenario. We're going to try to get this improvement in 69, but the most important part is landing the delete mechanism (that this bug does). Alicia, I'll keep you updated on this improvement in our legal mtgs.

Thanks all!

Flags: needinfo?(agray)
See Also: → 1559143
Blocks: 1559536
Type: defect → enhancement
Keywords: github-merged
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 69
Component: Activity Streams: Newtab → New Tab Page

Steps to test:

  1. Go to about:preferences#home
  2. Open the browser toolbox, and select the network tab.
  3. Opt out of spocs.
  4. You should see a DELETE request to "https://spocs.getpocket.com/user" with the params containing the pocket_id, the pocket_id should match your pref for "browser.newtabpage.activity-stream.impressionId"

Marius/Ciprian - did this get tested as part of the Adzerk QA in Nightly 69? If not, can you test it in Beta 69?

Flags: needinfo?(mcoman)
Flags: needinfo?(cmuresan)

We seem to have missed this when we verified the export.

I've verified that a DELETE request appears in the Browser Toolbox when the Recommended by Pocket or Sponsored Stories checkboxes are unchecked and that the IDs match the impressionId I see in about:config on Windows 10, macOS 10.14, and Arch Linux using the latest Nightly 70.0a1 (Build ID 20190711230342) and the latest Beta 69.0b3 (Build ID 20190708182549).

Sorry about this and thanks @Jess for flagging.

Status: RESOLVED → VERIFIED
Flags: needinfo?(mcoman)
Flags: needinfo?(cmuresan)

\o/ Thanks, Ciprian!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: