1895980 - Ads PPA: New KB content + in-product link request for privacy preserving attribution [Desktop Linux V128 Beta]

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Content, task)

Description

[cporter]

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

yes

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox for Desktop (Linux)

Select the type of request.

KB content update/ new content
In-product link request (via the Firefox Browser Settings)

Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

We're requesting the creation of a support page that describes the basic functionality, that 1) provides transparency and support for users, and 2) can be linked to from a (soon to be created) opt-out checkbox and "learn more" within the Firefox browser settings.

The Mozilla Ads team are developing a privacy-preserving attribution (PPA) technology that can enable the attribution insights advertisers need to understand their campaign performance while preserving the privacy of our users within the Firefox browser. End users won't "see" any change, but can still opt out from the Settings page.

With this feature active (default with Fx128), Firefox will aggregate and anonymize conversion data that can be used by Mozilla and advertisers to measure campaign effectiveness in a privacy preserving manner. No user data is shared, and individual users cannot be identified.
When a user opts out, we turn off the mechanism that sends the reports.

We will first roll out this feature as a beta on MDN only, desktop only, locales = all, with only 1-3 advertisers. From there we'll learn, iterate, and expand to other Mozilla surfaces (Pocket, New Tab) later in the year.

Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

Yes, in a sense. This is the first iteration, so the technology will adapt. Subsequent iterations will reach additional Mozilla products (i.e. Pocket, New Tab). That said, we are releasing a finalized production-quality feature at this time, just with a limited scale.

Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

On-train, target Fx128

What is the anticipated release date? [REQUIRED]

July 9 for Production release.

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

We will need to know the url for the support page before June 6 code freeze so that it can be included in the "Learn More" link within Settings. The content does not need to be live to end users until July 9.

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

This feature will be made available globally, and will need to be localized to all languages we support.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/AE-339
https://mozilla-hub.atlassian.net/browse/AE-359
https://docs.google.com/document/d/1_XsXUWx1V7nyxjKu6pJpnfFu2_NBJUsinw6sz5oyx5k/edit#heading=h.pg6qf4r8672x
https://docs.google.com/document/d/1tVnuVw2bN1suiWKM0I80P2xRRgbBsTkx-VVx_pvMqsE/edit#heading=h.25g3sck2mqzr

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

UX and Content Design for the Settings page are still in progress. Ticket: https://mozilla-hub.atlassian.net/browse/UXREQ-216

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

The only testing that you will be able to do and see as a user is to access Firefox Settings and opt out of the functionality, and link to the support page. Details of where that checkbox and message will live within the Settings are still being decided by the UX team. Details can be found in the UXREQ-216 ticket linked above.

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes. Dan Gonzalez ([e-mail]) should be the approver

Comment 1

[Lucas Siebert]

In-product link: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/privacy-preserving-attribution
Placeholder article: https://support.mozilla.org/en-US/kb/privacy-preserving-attribution
Guide to linking to SUMO articles: https://support.mozilla.org/en-US/kb/a-guide-to-linking-to-support-articles

Comment 2

[Alice Wyman]

KB article https://support.mozilla.org/en-US/kb/privacy-preserving-attribution has been updated and marked ready for localization. Bug 1895979 has been resolved fixed. Can this bug be closed as well?

Comment 3

[Lucas Siebert]

Appreciate you flagging it, Alice! Closing this bug now.