Closed Bug 1586882 Opened 6 years ago Closed 6 years ago

Add parameters to the Lockwise link in Protection Report

Categories

(Firefox :: Protections UI, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
Firefox 71
Tracking Status
firefox70 + verified
firefox71 --- verified

People

(Reporter: hoosteeno, Assigned: ewright)

Details

(Whiteboard: [protection-report][skyline])

Attachments

(1 file)

The protection report in Fx70 Beta includes a link to lockwise.firefox.com. We should add some utm parameters to that link so that we can measure the impact of this channel in driving Lockwise engagement.

We could follow the pattern set by the Monitor link on the same report:

https://lockwise.firefox.com/?utm_source=about-protections

We should do this before Fx70 release launch.

Summary: Add parameters to the lockbox link in Protection Report → Add parameters to the Lockwise link in Protection Report
Component: Preferences → Tracking Protection
Whiteboard: [protection-report][skyline]
Priority: -- → P1
Assignee: nobody → ewright
Status: NEW → ASSIGNED
Pushed by ewright@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6cdb3133f50f Add params to lockwise and proxy links from protection report. r=johannh

Can you request uplift (today) once this gets to m-c?
It has to land today to make it into beta 14 build tomorrow morning.

Flags: needinfo?(ewright)

ddurst is this also something you want to verify with marketing?

Flags: needinfo?(ddurst)

I'm going to assume that hoosteno is verifying this.

Flags: needinfo?(ddurst)

That said, if we should be doing something more robust here, like https://lockwise.firefox.com/ ?utm_source=firefox-desktop&utm_medium=referral&utm_campaign=about-protections&utm_content=about-protections (per hoosteno's spreadsheet), then we should. I can't tell who owns the final say of what links should be.

Comment on attachment 9099639 [details]
Bug 1586882 - Add params to lockwise and proxy links from protection report.

Beta/Release Uplift Approval Request

  • User impact if declined: We will not be able to measure impact of about:protections on the Lockwise product, and proxy (if we decide to enable it).
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): simple pref change which adds params to a url
  • String changes made/needed: none
Flags: needinfo?(ewright)
Attachment #9099639 - Flags: approval-mozilla-beta?
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71

hoosteeno, do you want to weigh in on comment 6? Or is this fine as it is? Can you verify it's as it should be in nightly?

Flags: needinfo?(hoosteeno)

Thanks, :lizzard.

My original request was intended to make this bug extremely expedient, because I thought it might be too late to be particular. But comment 6 is correct, and a better outcome here would include the following things:

a) standardized parameters that we try to use elsewhere, too
b) all 4 of the common utm parameters

So, with apologies for churn, I would prefer the URL on this link to be...

https://lockwise.firefox.com/
?utm_source=firefox-desktop&utm_medium=referral&utm_campaign=about-protections&utm_content=about-protections

Flags: needinfo?(hoosteeno)

Erica if you can fix up the patch I am happy to take it for tomorrow's build!

Flags: needinfo?(ewright)

Asking the sheriffs to back out the first patch from m-c

Backout by btara@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b109ea618eef Backed out changeset 6cdb3133f50f by lizzard's request

Thanks Liz, changed and up for review again.

Flags: needinfo?(ewright)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Pushed by jhofmann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bc6e2d9f6b74 Add params to lockwise and proxy links from protection report. r=johannh
Target Milestone: Firefox 71 → ---
Attachment #9099639 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71

I have verified this issue on the latest Nightly 71.0a1 (Build ID: 20191013213650), on Firefox Beta 70.0b14 (Build ID: 20191010142853), and on Firefox Release Candidate (Build ID: 20191014163058) on Windows 10 x64, Mac 10.14, and Ubuntu 16 x64.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: